Integration

This domain covers designing enterprise integration landscapes, selecting integration technologies, and justifying integration patterns. Integration is consistently the highest-failure domain on the CTA exam — mastering it requires understanding not just what the patterns are, but why and when to apply each one.

Study Content

Patterns & Architecture

• Integration Patterns — All 6 official Salesforce integration patterns with sequence diagrams, selection criteria, and timing guidance
• Middleware Architecture — MuleSoft API-led connectivity, ESB vs iPaaS, when middleware is justified vs point-to-point
• Event-Driven Architecture — Platform Events vs CDC vs Streaming vs Pub/Sub, event bus architecture, replay mechanisms

Technology & Implementation

• Salesforce API Landscape — Every Salesforce API with decision matrix, volume thresholds, rate limits, and authentication flows
• Error Handling Patterns — Retry strategies, exponential backoff, circuit breaker, dead letter queues, idempotency, monitoring
• Marketing Cloud Integration Architecture — MC Connect, Journey Builder, data model, MC Engagement vs Account Engagement, Data Cloud integration

Decision & Strategy

• Integration Decision Guides — 9 decision trees as Mermaid flowcharts covering sync vs async, middleware vs P2P, which API to use, and more
• Best Practices — Design, implementation, testing, and operations best practices with anti-patterns section
• Integration Trade-offs — Common trade-offs for CTA scenarios with structured analysis framework

Objectives

• Recommend enterprise integration landscape; describe risks, trade-offs, and business/technical considerations
• Describe capabilities of appropriate technology and justify use in overall integration architecture
• Recommend and justify appropriate integration strategy and common integration patterns
• Recommend platform-specific integration technology for external systems

Related Domains

Integration sits at the crossroads of nearly every domain. These connections are critical:

• System Architecture — System boundaries and platform capabilities define the integration surface area
• Data Architecture — ETL patterns, data migration, and volume considerations bridge the data and integration domains
• Solution Architecture — External application capabilities and constraints directly shape integration design choices
• Development Lifecycle — API versioning strategies, deployment pipelines, and integration testing are lifecycle concerns