Salesforce Integration Architect Exam Guide
Design robust, secure integrations between Salesforce and the rest of your enterprise landscape. This guide explains the format, domains, patterns, and preparation tips for the Salesforce Certified Integration Architect exam, with scenario-style examples.
Who is the Salesforce Integration Architect for?
This credential is for architects and senior practitioners who own the integration strategy for Salesforce. You’re a great fit if you:
- Design or review APIs, middleware flows, events and data sync involving Salesforce.
- Work with integration platforms (e.g., MuleSoft) and enterprise architects on end-to-end designs.
- Have to balance real-time vs batch, sync vs async, API limits, resiliency and cost.
- Are already experienced with platform limits, security and data model design on Salesforce.
This exam also contributes towards composite System Architect and is a key step in the overall Salesforce Architect Journey.
Exam Overview
📊 Exam at a Glance
| Exam Name | Salesforce Certified Integration Architect |
| Format | Proctored, multiple-choice / multiple-select, scenario-heavy |
| Duration | ~105–120 minutes (check current exam guide) |
| Number of Questions | ~60 scored questions (+ a few unscored items) |
| Passing Score | Typically mid-60% range (verify latest value before booking) |
| Registration Fee | $400 USD (Retake: $200 USD) |
| Prerequisites | No mandatory certification prerequisite, but strong experience with APIs, integration tools, and Salesforce data & security is strongly recommended. |
🧭 What this Exam Focuses On
Expect questions that test your ability to:
- Pick the right integration pattern (request/response, batch, event-driven, pub/sub).
- Design API strategies with REST, SOAP, Bulk, GraphQL and limits in mind.
- Use events, queues and middleware for scalable asynchronous designs.
- Implement error handling, retry, idempotency and monitoring for resilience.
- Respect security, governance and data residency constraints across systems.
Integration Architect Exam Domains
Salesforce occasionally renames domains or tweaks weightage, but the core concepts stay stable. Use the breakdown below as a practical study map and always cross-check the latest official exam guide.
🔍 View High-Level Domains & Weightage
- Integration Fundamentals & Requirements – Understanding system landscape, constraints, SLAs and non-functional requirements.
- Integration Patterns & Design – Request/reply, fire-and-forget, batch data sync, event-driven and pub/sub designs.
- API Strategy & Implementation – REST, SOAP, Bulk APIs, limits, versioning, and platform events / change data capture.
- Security, Identity & Governance – Auth, encryption, data classification, governance and compliance for integrations.
- Error Handling, Resiliency & Monitoring – Retry, back-off, idempotency, observability, and operational ownership.
Exact domain names and percentages may change by release; always rely on the official exam guide for the latest breakdown.
- More questions using event-driven architectures and real-time integrations.
- Scenarios that combine Salesforce with MuleSoft, Data Cloud and external data platforms.
- Increased emphasis on governance, reuse and API-led connectivity for large programs.
- Attention to rate limiting, concurrency and back-pressure across high-volume interfaces.
Key Integration Architecture Decisions
🔄 Choosing the Right Integration Pattern
- Identify when the business truly needs real-time vs near-real-time or batch.
- Use request/response for synchronous UX-driven use cases with immediate feedback.
- Use fire-and-forget, queues or events for decoupled, resilient processes.
- Design bulk data sync and initial loads for large datasets and migrations.
🌐 API Strategy & Limits
- Choose between REST, SOAP, Bulk, GraphQL depending on consumer and use case.
- Respect API limits, concurrency and back-off strategies.
- Define versioning and lifecycle for APIs (especially with MuleSoft / API gateway).
- Plan for governance: who can publish, change and consume each API.
📡 Events, Streaming & Middleware
- Use Platform Events and Change Data Capture to publish Salesforce changes.
- Leverage middleware (e.g. MuleSoft) for orchestration, transformation and policy enforcement.
- Design for idempotency so retries don’t create duplicates.
- Consider event ordering, replay and durability for critical processes.
🛡️ Security & Compliance for Integrations
- Protect integrations with appropriate auth flows (OAuth, JWT, certificates).
- Understand how field-level security, sharing and data classification apply to APIs.
- Handle PII, compliance and residency requirements across regions.
- Define monitoring, logging and alerting so issues are caught quickly.
4-Week Study Plan (Adjust as Needed)
This plan assumes ~1–2 hours per weekday and deeper hands-on practice on weekends. Extend it if you’re newer to Salesforce or enterprise integration.
Week 1 – Fundamentals & Landscape
- Read the official Integration Architect exam guide end-to-end.
- Map your current system landscape: systems, data flows, message volumes.
- Review Salesforce docs on API limits, REST/SOAP/Bulk, Platform Events & CDC.
Week 2 – Patterns & API Design
- Study the official integration pattern docs (request/reply, batch, fire-and-forget, etc.).
- Implement sample integrations using REST and SOAP APIs in a dev sandbox.
- Design a simple API-led connectivity diagram: System, Process, Experience APIs.
Week 3 – Events, Middleware & Error Handling
- Configure and test Platform Events or Change Data Capture in a sandbox.
- Explore middleware (e.g., MuleSoft or your company’s chosen tool) patterns.
- Practice designing retry, back-off, idempotency and monitoring strategies.
Week 4 – Scenario Practice & Mock Exams
- Do as many scenario-based questions as possible; focus on trade-off reasoning.
- Time yourself on 60-question mixed sets to simulate the real exam pacing.
- Re-review weak domains and create a one-page “go-to patterns” cheat sheet.
Sample Scenario-Style Questions
Question 1
A call center app needs to display real-time customer data from Salesforce whenever an agent opens a customer record in a non-Salesforce system. The UI must not proceed until Salesforce data is loaded. What pattern is most appropriate?
Question 2
A financial services company needs to replicate opportunity data from Salesforce into a data warehouse every 15 minutes for analytics. The volume is high but strict real-time is not required. Which approach is most appropriate?
Question 3
An integration between Salesforce and an order management system is experiencing intermittent timeouts. Orders are sometimes created twice in Salesforce when the OMS retries. What should the architect recommend?