Integration

Key Takeaways

Integration is consistently the highest-failure domain on the CTA exam. You must know all 6 official Salesforce integration patterns, when middleware (MuleSoft) is justified vs point-to-point, event-driven architecture options, error handling strategies, and how to defend pattern choices with clear trade-off analysis. Always show the middleware layer in diagrams.

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

Practice

• Domain Grilling: D5 Integration Q&A

Related Topics

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

Frequently Asked Questions

What integration topics does the CTA exam focus on most heavily?

The CTA exam tests all 6 official Salesforce integration patterns (Request-Reply, Fire-and-Forget, Batch, Remote Call-In, UI Update, Data Virtualization), middleware architecture (MuleSoft API-led connectivity, ESB vs iPaaS), event-driven architecture (Platform Events, CDC, Pub/Sub API), error handling strategies, and the Salesforce API landscape with rate limits and authentication flows.

How is Integration scored in the CTA review board?

Judges evaluate whether you selected the correct integration pattern for each system interaction, whether you justified middleware vs point-to-point decisions, whether your error handling strategy is comprehensive (retry, circuit breaker, dead letter queue, idempotency), and whether your integration diagram clearly shows all system boundaries, protocols, and data flow direction. Always include the middleware/ESB layer in diagrams.

What are the most common mistakes in Integration during the CTA exam?

Candidates commonly fail by using synchronous patterns where asynchronous is more appropriate, not showing middleware in the integration architecture diagram, ignoring error handling and retry strategies, selecting the wrong API type for the data volume (REST API for bulk operations instead of Bulk API 2.0), and not addressing rate limiting and API call budget consumption across all integrations.

When should I recommend MuleSoft middleware vs point-to-point integration?

Recommend MuleSoft middleware when the scenario has 3+ external systems, requires API reuse across multiple consumers, needs protocol transformation (SOAP to REST, XML to JSON), requires centralized error handling and monitoring, or involves complex orchestration logic. Point-to-point is acceptable for simple, single-system integrations with low volume and straightforward data mapping.

How should I handle event-driven architecture questions at the review board?

Distinguish clearly between Platform Events (custom publish/subscribe), Change Data Capture (automatic change notifications), and Pub/Sub API (high-volume external subscription). Address replay mechanisms for message recovery, event bus delivery guarantees, subscriber capacity, and when to use each. Platform Events suit custom business events; CDC suits data synchronization; Pub/Sub API suits external high-throughput consumers.

What error handling patterns should I include in my CTA solution?

Every integration should address retry strategy (exponential backoff with jitter), idempotency (using unique transaction IDs), circuit breaker pattern for failing endpoints, dead letter queues for unrecoverable messages, monitoring and alerting, and reconciliation processes for data consistency verification. Judges specifically look for comprehensive error handling — omitting it is a common failure point.