Platform Integration Architect checks that you can design how Salesforce connects to other systems, from start to finish. It is one of the four exams you need for System Architect. See the System Architect guide for the full path.
Free practice • No sign-up required
Independent study resource
Exam objectives and policies can change. Confirm current details with the certification issuer.
Check current objectives
Use the official exam guide as the source for current objectives and section weights.
Practice for learning
Use sample questions to review concepts and identify topics for further study.
Works on Any Device
Full practice experience on phone, tablet, or desktop
Free, No Sign-Up
Start practicing immediately, no account or email required
Salesforce Certified Platform Integration Architect – Complete 2026 Guide
This exam tests how you design connections between Salesforce and other systems using the REST, SOAP, Bulk and streaming APIs. You pick the right pattern, decide whether middleware is needed, and plan what happens when something fails. The exam is 60 scored questions in 105 minutes, with a 67% pass mark, weighted towards Design Integration Solutions (28%) and Build Solution (23%).
Recommended Prerequisites
We recommend completing this certification first to prepare you better.
| Official exam name and code | Salesforce Certified Platform Integration Architect (Integration Architect) |
|---|---|
| Questions | 60 |
| Time allotted | 105 min |
| Passing score | 67% |
| Exam fee | $400 |
| Retake fee | $200 |
| Prerequisite certifications | Recommended preparation: Salesforce Certified System Architect |
| Study guide release | Summer '26 |
Salesforce Certified Platform Integration Architect Exam Weightage by Section
1. Evaluate the Current System Landscape (8%)
8%2. Evaluate Business Needs (11%)
11%3. Translate Needs to Integration Requirements (22%)
22%4. Design Integration Solutions (28%)
28%5. Build Solution (23%)
23%6. Maintain Integration (8%)
8%Exam Topics
Last updated:
Who is the Integration Architect exam for?
- Senior developers: You already build callouts and APIs, and you want proof that you can design the whole integration, not just code one part of it.
- Aspiring architects: Platform Integration Architect is one of the four exams you need for System Architect, which in turn leads toward Technical Architect (CTA).
- Integration consultants: You connect Salesforce to ERPs, billing tools and data platforms for clients, and you want a credential that shows it.
Exam Fees & Registration
Exam Fee
$400
One-time registration fee
Retake Fee
$200
If you need to retake the exam
Comparing certs? View all Salesforce exam fees in one place →
Certification Validity
Maintenance and renewal requirements vary. Check the issuer’s current credential page for requirements that apply to you.
How to Register
Check current Salesforce Certified Platform Integration Architect credential and registration details with the issuer.
View official credential detailsOfficial references: Use the issuer’s current materials to confirm exam objectives, format, and fees before booking.
Official sources: Exam guide·Salesforce exam pricing·Independent exam-prep resource; details may change.
Exam Tips
- 1Integration Architecture and Patterns are 55%. Know when to use REST, SOAP, and event-driven patterns.
- 2Understand identity and access management for integrations (OAuth, SAML, certificates).
- 3Know integration patterns: point-to-point, hub-and-spoke, publish-subscribe.
- 4Be ready for "how would you integrate X with Y?" scenario questions.
Prerequisites
- •Application Architect
- •System Architect
- •Strong integration experience
Focus Areas
- •Integration Architecture
- •Integration Patterns
- •Identity and Access
- •Development Lifecycle
Study Strategy
Study integration patterns and when to use each.
Practice designing end-to-end integration solutions.
Review CTA prep materials for complex scenarios.
Exam Format and First-Attempt Readiness
The Salesforce Certified Platform Integration Architect exam has 60 questions in 105 min, passing score 67%. Most Salesforce exams test scenario-based decisions. Focus on when to use each feature, not just terms.
- Study Design Integration Solutions and Build Solution first, together they carry 51% of the exam.
- Do timed question sets. Build pacing and confidence.
- Review why wrong answers are wrong. It improves scenario reasoning.
- Book the exam once your mock scores are steady at 80%+.
Is the Integration Architect Exam Hard?
Is the Integration Architect Exam Hard?
Yes. Most people rate it as one of the harder architect exams. You need to know the Salesforce APIs well, and you also need to know when not to use them and reach for middleware instead.
- 60 multiple-choice questions in 105 minutes.
- 67% to pass. That is about 41 correct answers out of 60. Most questions are scenarios, so you can't pass on memory alone.
- Many patterns tested. Expect REST, SOAP, Bulk API, Platform Events, Change Data Capture, outbound messages and MuleSoft.
- Limits matter. Callout limits (100 per transaction, 120 seconds total) and async Apex come up often.
Pass Rate Guidance
People with a few years of real integration work tend to do best. Before you book. Aim for 80% or more on practice tests, and make sure you can sketch an integration on a whiteboard and explain why you chose each piece.
Integration Architect Exam Format Explained
Integration Architect Exam Format Explained
You can take the exam online with a proctor or at a test centre. Here is what to expect:
Total Questions
60 scored questions
Time Limit
105 min
Passing Score
67%
Question Type
Multiple-choice & multiple-select
How Many Questions Are Scenario-Based?
About two thirds of the questions are short business scenarios. A typical one describes data that needs to move between Salesforce and another system, then asks which approach fits best: real time, near real time or batch, and push or pull.
Best Way to Pass on Your First Attempt
- Learn the patterns first: For each scenario, ask three things. Does the user wait for an answer? How much data is there? Which system starts the exchange? Those answers point to the pattern.
- Know the callout limits: 100 callouts per transaction and 120 seconds in total. Know when to move work into @future or Queueable Apex to stay under them.
- Don't skip Connected Apps: Know the main OAuth flows, what scopes do, and how Canvas apps load an outside app inside Salesforce.
- Know when to add middleware: A single, simple connection can go direct. Many systems, heavy data changes or reuse across teams usually means MuleSoft or another middleware tool.
Integration Architect: Key Concepts
Integration Patterns: When to Use Each
Salesforce publishes a short list of integration patterns, and most exam questions map to one of them. Request and Reply: Salesforce calls another system and waits for the answer, for example checking an address while a user saves a record. Fire and Forget: Salesforce sends a message and moves on without waiting. Platform Events and outbound messages work this way. Batch Data Synchronization: large amounts of data move on a schedule, usually with Bulk API or an ETL tool such as MuleSoft or Informatica. Data Virtualization: Salesforce shows outside data without storing it, using External Objects and Salesforce Connect. UI Update Based on Data Changes: Change Data Capture or the streaming API pushes changes to a screen as they happen. To pick the right one, look at three things in the question: how fast the answer is needed, how much data there is, and what should happen if the call fails.
Salesforce APIs: REST, SOAP, Bulk, Streaming, and Connect
Each API fits a different job. REST API uses JSON and is the default for small, real-time reads and writes, both into Salesforce and out through Apex callouts. SOAP API uses XML and a WSDL, and you mostly see it with older enterprise systems that want a strict contract. Bulk API 2.0 handles millions of records in the background and is the usual choice for data migration and large nightly loads. Change Data Capture sends an event every time a record changes; with only the fields that changed. Composite API groups several REST calls into one request, which saves round trips. Connect API gives ready-made endpoints for things like Chatter and Experience Cloud. The exam asks which API fits a given amount of data, speed and direction, and which limits apply. Remember 100 callouts per transaction, a 6 MB heap limit for synchronous Apex and the daily API call allowance for your org.
Error Handling, Idempotency, and Recovery
Integrations fail, and the exam wants to see that you planned for it. Retry with backoff: wait a little longer before each retry (1s, 2s, 4s, 8s) so you don't flood a system that is already struggling. Idempotency: sending the same message twice should not create two records. The usual fix is an external ID or a unique request ID that the receiving system checks. Dead-letter queue: messages that still fail after every retry go to a holding area where someone can look at them. Circuit breaker: after several failures in a row, stop calling the other system for a while and queue the work instead. Two Salesforce details come up often. Outbound messages are retried for up to 24 hours. Platform Event subscribers can use the replay ID to pick up where they left off, and events are kept for 72 hours.
Platform Events, CDC, and Event-Driven Architecture
Platform Events let one system announce that something happened while other systems listen. Apex, Flow or an outside system can publish an event. Apex triggers, Flow or outside subscribers can react to it. The publisher doesn't need to know who is listening, which is why this is called loose coupling. Events are kept for 72 hours, and each one has a replay ID so a subscriber that went offline can catch up. Change Data Capture (CDC) is a special kind of event that Salesforce sends for you whenever a record is created, updated, deleted or undeleted. Each CDC event tells you what changed, the type of change and who made it. Outside systems can subscribe with CometD or with the newer Pub/Sub API, which uses gRPC and is the better choice for new work. On the exam, use Platform Events when you control the message, CDC when you just need to mirror record changes, and outbound messages for simple, no-code notifications.
Middleware, MuleSoft, and API Governance
Once more than two or three systems are involved, connecting each one directly to the others turns into a mess. Middleware sits in the middle and handles the routing and data mapping. MuleSoft splits APIs into three layers. System APIs talk to the back-end systems. Process APIs combine data and apply business rules. Experience APIs shape the data for a specific app or channel. Anypoint Exchange is where teams publish APIs so others can reuse them, and an API gateway enforces rate limits and security. On the Salesforce side, Named Credentials hold the endpoint URL and the login details, so your Apex code never contains a password or token. When a question shows hard-coded auth headers, the answer is almost always Named Credentials. External Services let an admin import an OpenAPI spec and call that API from Flow with no code. Expect questions on when middleware is worth the cost and how to retire an old API version without breaking the systems that use it.
Integration Architect scenarios reduce to matching the requirement’s latency and fan-out needs to the correct pattern.
How to Pass the Salesforce Integration Architect Exam
Almost every question is a design choice. Read the scenario, find the details about timing, volume and failure, and let those pick the answer for you.
Integration Pattern Selection
If the user is waiting on screen, think Request and Reply. If nobody is waiting, think Fire and Forget or batch. If the data shouldn't be copied into Salesforce at all, think Data Virtualization.
REST vs. SOAP vs. Bulk API
REST API for small, quick reads and writes. SOAP API when the other system needs a WSDL. Bulk API once you are into tens of thousands of records or more. Streaming and CDC when the other side needs to hear about changes as they happen.
Platform Events & Change Data Capture
Platform Events when you design the message yourself and want publisher and subscriber kept apart. CDC when you just need to copy record changes somewhere else. In both cases. Know how the replay ID lets a subscriber catch up after it was offline.
Middleware & MuleSoft
One simple connection can go direct. Several systems, a lot of data mapping, or APIs that other teams will reuse point to middleware. Know the three MuleSoft layers: System, Process and Experience.
Security in Integrations
Use Named Credentials for every outbound call. Pick the OAuth flow that fits: JWT bearer for server-to-server, web server flow when a person logs in. Add IP restrictions or mutual TLS when the data is sensitive.
Is the Salesforce Certified Platform Integration Architect Exam Hard?
DifficultyChallenging; plan about 8-16 weeks of focused prep.
Book When ReadyScore 80%+ on three timed mocks before scheduling.
Use Practice, Not DumpsOriginal practice questions build skill without risking your credential.
Exam format: 60 questions, 105 min, 67% passing score.
Salesforce Certified Platform Integration Architect Practice Questions (With Explanations)
Test your knowledge with these 15 sample questions.
Question 1: When a sales rep saves an Account, the address must be checked by an outside address service. The rep should see an error straight away if the address is wrong. Which pattern fits best?
Key takeaway: The rep is waiting and needs the result before the save finishes.
Show correct answer and explanation
Correct answer: C. Request and Reply using a synchronous callout
The rep is waiting and needs the result before the save finishes. That is Request and Reply: Salesforce calls the service and waits for the answer.
- A Platform Event doesn't wait for a reply, so the rep wouldn't see the error while saving.
- A nightly batch runs hours later. The rep would already have moved on.
- External Objects show outside data inside Salesforce. They don't check data the user is typing in.
Question 2: A company needs to load 8 million order records from an old ERP into Salesforce during a one-time migration. Which API should the architect recommend?
Key takeaway: Bulk API 2.
Show correct answer and explanation
Correct answer: A. Bulk API 2.0
Bulk API 2.0 is built for very large loads. It processes records in the background in large chunks and uses far fewer API calls.
- One REST call per record would use 8 million API calls and blow through the org's daily limit.
- Composite API groups a few requests together, but it is meant for small related changes, not millions of rows.
- Synchronous SOAP calls have the same volume problem as REST and would be very slow.
Question 3: A developer has written an Apex callout with the API username and password typed into the code as an Authorization header. What should the architect recommend instead?
Key takeaway: A Named Credential keeps the URL and login details out of the code.
Show correct answer and explanation
Correct answer: B. Use a Named Credential to hold the endpoint and authentication
A Named Credential keeps the URL and login details out of the code. Salesforce adds the authentication for you, and admins can change it without a deployment.
- A Custom Setting is still readable by admins and code, and you still have to build the auth header by hand.
- Custom Labels are not meant for secrets, and anyone with setup access can read them.
- Removing authentication makes the other system less secure. IP checks can be added on top of login, not used instead of it.
Question 4: Every time an Opportunity is updated, a data warehouse needs a copy of only the fields that changed. The team does not want to write custom code to send these changes. What is the best fit?
Key takeaway: Change Data Capture sends an event for each change automatically, and the event holds only the changed fields.
Show correct answer and explanation
Correct answer: D. Change Data Capture on the Opportunity object
Change Data Capture sends an event for each change automatically, and the event holds only the changed fields. The warehouse just subscribes.
- A trigger with callouts is custom code, and it can hit callout limits during bulk updates.
- A scheduled report is not a real integration and doesn't capture each individual change.
- A custom Platform Event works, but you would have to build and publish it yourself. CDC does this for you.
Question 5: An external billing system sometimes sends the same invoice message twice after a network timeout. Duplicate invoices are being created in Salesforce. What should the architect do?
Key takeaway: An upsert on an external ID updates the record if it already exists, so a repeated message doesn't create a second invoice.
Show correct answer and explanation
Correct answer: B. Upsert using an external ID taken from the invoice number
An upsert on an external ID updates the record if it already exists, so a repeated message doesn't create a second invoice. This makes the integration idempotent.
- Turning off retries means real failures are never recovered.
- A cleanup job leaves duplicates in place for hours and fixes the symptom, not the cause.
- A longer timeout might reduce retries, but it won't stop them. Duplicates can still happen.
Question 6: An external subscriber to Salesforce Platform Events was offline for 6 hours during maintenance. How can it get the events it missed?
Key takeaway: Platform Events are kept for 72 hours.
Show correct answer and explanation
Correct answer: D. Reconnect using the replay ID of the last event it processed
Platform Events are kept for 72 hours. A subscriber can pass the last replay ID it handled and receive everything published after that point.
- Events are not lost straight away. They are kept for 72 hours so subscribers can catch up.
- Support doesn't resend events. The replay ID is the built-in way to do this.
- A full export is slow and unnecessary when the events are still available to replay.
Question 7: A company is connecting Salesforce to an ERP, a warehouse system, a billing tool and a customer portal. Several teams will reuse the same customer and order data. What should the architect recommend?
Key takeaway: With many systems and shared data, middleware keeps the connections in one place.
Show correct answer and explanation
Correct answer: A. Middleware with reusable APIs
With many systems and shared data, middleware keeps the connections in one place. Reusable System and Process APIs stop each team rebuilding the same thing.
- Point-to-point links grow quickly with each new system and become hard to change.
- Nightly files are slow, error-prone and don't give teams reusable services.
- Separate callouts per team mean duplicated logic and no central place to manage security or changes.
Question 8: A partner's server needs to call the Salesforce REST API every 15 minutes with no person logging in. Which OAuth flow fits best?
Key takeaway: The JWT bearer flow is meant for server-to-server access.
Show correct answer and explanation
Correct answer: C. JWT bearer flow
The JWT bearer flow is meant for server-to-server access. The partner signs a token with a certificate and gets access without anyone typing a password.
- The web server flow needs a person to log in and approve access in a browser.
- The user-agent flow is for apps running in a browser or on a device, with a user present.
- The username and password flow stores a real password on the server and is not recommended.
Question 9: A trigger starts one Queueable job that makes a callout for every record in the transaction. During a data load, a single transaction can include 500 records. What is the main risk?
Key takeaway: Apex allows 100 callouts per transaction, and the Queueable job runs as one transaction.
Show correct answer and explanation
Correct answer: B. The transaction will hit the limit of 100 callouts
Apex allows 100 callouts per transaction, and the Queueable job runs as one transaction. 500 callouts would fail. Group the records into fewer calls or split the work across several jobs or batch Apex.
- Triggers can re-run in some cases, but that is not the main risk in this scenario.
- Callouts from a Queueable job started by a trigger are allowed. That is the usual way to call out after a record change.
- Records get IDs when they are inserted. Callouts don't affect that.
Question 10: Service agents need to see a customer's recent shipments, which live in a logistics system. The data changes constantly and must not be copied into Salesforce. Which approach fits?
Key takeaway: Salesforce Connect reads the data from the logistics system when the agent opens the page.
Show correct answer and explanation
Correct answer: D. Salesforce Connect with External Objects
Salesforce Connect reads the data from the logistics system when the agent opens the page. Nothing is stored in Salesforce, and the data is always current.
- An hourly copy stores the data in Salesforce, which the scenario rules out, and it can be an hour out of date.
- Outbound messages send data out of Salesforce. They don't bring outside data in.
- A nightly Bulk load copies the data and is up to a day old.
Question 11: An admin wants to call an outside currency rate API from a Flow without writing any Apex. The API has an OpenAPI spec. What should they use?
Key takeaway: External Services reads the OpenAPI spec and creates actions that Flow can call directly.
Show correct answer and explanation
Correct answer: A. External Services
External Services reads the OpenAPI spec and creates actions that Flow can call directly. No code is needed.
- Outbound messages send a fixed SOAP message out of Salesforce. They can't read a response back into a Flow.
- A Canvas app shows an outside web app inside Salesforce. It doesn't give Flow a callable action.
- CDC publishes changes to Salesforce records. It doesn't call outside APIs.
Question 12: When a Case is closed, a ticket must be closed in an outside help desk tool. The user doesn't need to wait for this, and the team wants a declarative option with built-in retries. What fits?
Key takeaway: Outbound messages are no-code, don't make the user wait, and Salesforce retries them for up to 24 hours if the other system is down.
Show correct answer and explanation
Correct answer: C. An outbound message from a record-triggered Flow
Outbound messages are no-code, don't make the user wait, and Salesforce retries them for up to 24 hours if the other system is down.
- Triggers can't make synchronous callouts, and this would make the user wait anyway.
- A nightly job delays the update by up to a day for no reason.
- A browser call only runs when someone has the page open, and it puts the integration logic on the user's screen.
Question 13: An outside order system is having an outage, and every call to it times out after 10 seconds. Salesforce keeps calling it and users are stuck waiting. Which design helps most?
Key takeaway: A circuit breaker notices repeated failures and stops calling the broken system for a set time.
Show correct answer and explanation
Correct answer: D. A circuit breaker that pauses calls and queues work
A circuit breaker notices repeated failures and stops calling the broken system for a set time. Work is queued and sent once the system is back.
- A longer timeout makes users wait even longer and doesn't fix the outage.
- Instant retries add load to a system that is already down and use up callout limits.
- Removing error handling means failed work is lost with no record of it.
Question 14: Version 1 of a company's customer API is being replaced by version 2, which changes some field names. Five other systems use version 1. What is the safest plan?
Key takeaway: Running both versions for a while gives each consumer time to update and test.
Show correct answer and explanation
Correct answer: B. Run both versions side by side, announce a retirement date
Running both versions for a while gives each consumer time to update and test. A clear retirement date keeps the move on track.
- A same-day switch means any consumer that isn't ready will break.
- Changing version 1 in place breaks every system that relies on the old field names.
- Never moving on leaves the team stuck maintaining old code and blocks improvements.
Question 15: An external app needs to create an Account, a Contact and an Opportunity together. If any one fails, none should be saved. The team wants as few API calls as possible. What should they use?
Key takeaway: The Composite API sends all three requests in one call.
Show correct answer and explanation
Correct answer: C. Composite API with allOrNone true
The Composite API sends all three requests in one call. With allOrNone set to true, everything is rolled back if one part fails.
- Three separate calls use more API calls, and if the third fails the first two are already saved.
- Bulk API is for large volumes and runs in the background. It is far too heavy for three related records.
- Outbound messages send data out of Salesforce. They can't be used by an outside app to create records.
Get the Full Question Bank
Most candidates book the exam after scoring 80%+ on full mocks.
If you’re planning to test this quarter, aim to complete full mocks at least 10–14 days before your exam date.
Contact us for more information on our full 60-question mock exams and a personalized study plan. Use the contact form.
Request Mock Exams & Study PlanSalesforce Certified Platform Integration Architect Exam FAQs
- What is covered on the Salesforce Certified Platform Integration Architect exam?
- The Salesforce Certified Platform Integration Architect exam (formerly Salesforce Certified Integration Architect) covers section-wise weightage as shown above. Use the exam topics and practice questions on this page to align your study with the official outline.
- What is Integration Architect?
- Integration Architect designs integration solutions, understands integration patterns, and ensures secure, scalable integrations between Salesforce and external systems.
- Do I need Application Architect before Integration Architect?
- Yes, Application Architect is typically required. Integration Architect is part of the Technical Architect path and requires deep integration expertise.
- Are there free practice questions for the Salesforce Certified Platform Integration Architect exam?
- Yes. This page includes free sample practice questions with explanations. Use them alongside the current official documentation.
- How do I prepare for the Salesforce Certified Platform Integration Architect certification?
- Use the exam tips, prerequisites, and study strategy on this Salesforce Certified Platform Integration Architect study guide (formerly Salesforce Certified Integration Architect). Focus first on the highest-weighted sections, then take the sample practice questions. Schedule the exam when you consistently score well on practice tests.
Next Architect Certifications
After Integration Architect, most people work toward System Architect and then CTA:
Honest Cert Breakdown
Difficulty: Hard
4/5Broad scope: APIs, middleware, event-driven architecture, security, governance. Real enterprise integration project experience is the best preparation.
Salary Range
$120,000–$168,000 / year
US average for certified professionals • Updated Summer '26 • Source: Salesforce Talent Ecosystem
Is it worth it?
Strong salary premium. Integration skills are perpetually in short supply. One of the better architect-tier investments outside the CTA path.
Weightings by Section
What Each Domain Covers
Translating Business Requirements
Converting integration requirements into architectural decisions. Identify integration patterns (point-to-point, hub-and-spoke, ESB, API-led) appropriate for each business scenario. Evaluate trade-offs between real-time and batch integration. Assess non-functional requirements: latency, throughput, availability, error tolerance.
Architecting Integration Solutions
Designing REST and SOAP APIs on Salesforce, Apex callouts, Platform Events, Change Data Capture (CDC), and Streaming API. Understanding the Salesforce Integration Patterns: remote process invocation (sync/async), data replication, UI update, batch data sync. Middleware and API gateway design.
Understanding Integration Protocols & Patterns
REST vs SOAP trade-offs, OAuth 2.0 flows, named credentials, remote site settings, certificate management. Salesforce Platform Events and event-driven architecture. Bulk API vs REST API vs SOAP API for data volume decisions. Salesforce Connect and external objects.
Performance, Scalability & Error Handling
Governor limits impact on integration design (callout limits, heap size, CPU timeout). Async Apex patterns for callout scalability: Queueable vs Future vs Batch. Idempotency, retry logic, dead-letter queues. Monitoring integrations with Platform Event replay IDs.
Governance & Monitoring
API versioning strategy, deprecation planning, integration documentation standards. API Management tools: Salesforce API Manager, MuleSoft Anypoint, Apigee. Monitoring callout failures, Platform Event delivery guarantees, and alerting strategy.
10-Week Study Plan
Working Through Scenario Questions
- 1.Know the 5 integration patterns cold: Remote Process Invocation (sync), Remote Process Invocation (async), Batch Data Sync, Remote Call-In, and UI Update. Each question’s scenario will map to one, identify it before selecting an answer.
- 2.Async beats sync for large volumes: If a scenario involves high volume, long-running external calls, or fire-and-forget notification, the answer is almost always an async pattern (Queueable, Batch, Platform Events) over a synchronous callout.
- 3.Platform Events for event-driven: When a scenario requires near-real-time notification to multiple subscribers (decoupled architecture), Platform Events is the correct answer over direct callouts or polling.
- 4.Named credentials for callout security: Any question about securing external HTTP callouts should point to named credentials, they abstract authentication and avoid storing credentials in Apex code.
Practice-Test Benchmark
Aim for 80%+ on practice exams before scheduling. Integration Architect tests architecture judgement, not just feature knowledge. If you can explain why you chose a pattern (not just what the pattern is), you are ready. The 67% passing score is higher than most professional certs.
10 Concepts Worth Reviewing
- The 5 Salesforce integration patterns and when to apply each
- REST vs SOAP trade-offs: when to use each for Salesforce integrations
- Platform Events: publish-subscribe, replay IDs, delivery guarantees
- Change Data Capture: what triggers events, high-volume events, supported objects
- Apex callout limits: 100 callouts/transaction, 120s timeout, heap impact
- Queueable vs Future vs Batch Apex for async integration scenarios
- OAuth 2.0 flows: Web Server, JWT Bearer, Username-Password, when each applies
- Named credentials: types (Legacy, Per-User, Named Principal), protocol support
- Idempotency and retry design: why it matters and how to implement it
- Bulk API 2.0 vs REST API for large-volume inbound data loads
Questions Candidates Ask
- What is the Salesforce Integration Architect certification?
- The Salesforce Integration Architect certification validates ability to design and architect enterprise integration solutions on the Salesforce platform. The exam covers integration patterns (REST, SOAP, streaming, event-driven), error handling, scalability, and governance. It has 60 questions, a 105-minute time limit, a 67% passing score and a $400 fee. It is one of the four exams you need for System Architect.
- What are the prerequisites for Integration Architect?
- No formal prerequisites are listed, but Salesforce strongly recommends holding ADM-201 and Platform Developer I before attempting Integration Architect. Candidates typically have 3–5 years of Salesforce integration experience. The exam assumes deep knowledge of Salesforce APIs, Apex callouts, Platform Events, and external authentication patterns.
- What integration patterns are tested on the exam?
- The exam tests all major Salesforce integration patterns: Remote Process Invocation (sync and async), Data Replication (inbound and outbound), UI Update via Salesforce, and Batch Data Synchronisation. For each pattern, you must know when to apply it, what Salesforce features implement it (Platform Events, CDC, Bulk API, Apex callouts), and the trade-offs involved.
- How hard is the Integration Architect exam?
- Integration Architect is considered one of the more challenging Salesforce exams. It tests deep technical knowledge and scenario-based architecture decisions, not just feature recall. Candidates must understand governor limits, async patterns, API design trade-offs, and error handling strategies. Most candidates have 3–5 years of integration experience and still spend 10–12 weeks preparing.
- What is the difference between Platform Events and CDC?
- Platform Events are custom event messages you define and publish to the Salesforce event bus, used for near-real-time notifications between systems. Change Data Capture (CDC) automatically publishes change events whenever Salesforce records are created, updated, deleted, or undeleted, used for data replication to external systems. Both use the CometD streaming protocol and replay IDs for guaranteed delivery.
Plan Your Next Certification
After this certification, consider: Application Architect, System Architect, or Technical Architect (CTA).
Topic Difficulty Heatmap
Which topics are a gimme vs which ones trap confident candidates. Use this to prioritise your final-week revision. These are our own topic groupings for study planning, not the official exam sections, those and their weightings are in the credential's exam guide.
| Topic | Difficulty | Study Tip |
|---|---|---|
| Integration Architecture | Hard | Pattern selection (sync vs async, real-time vs batch), scenario-heavy. |
| Integration Patterns | Trap ⚠ | When to use Platform Events vs Change Data Capture vs API, commonly tested. |
| Identity and Access | Moderate | Named Credentials and auth for integrations. Know the options. |
| Development Lifecycle | Easy | Integration deployment and testing, standard patterns. |
Difficulty based on analysis of common candidate errors across each exam section.
Try It Yourself
Test yourself with free Integration Architect practice questions covering all 5 exam sections.
Start Free Practice QuestionsFast Facts: Integration Architect Focus Areas
- Integration pattern selection: When to use REST vs. SOAP vs. Bulk API vs. Streaming API vs. Platform Events, and the trade-offs of each for specific integration scenarios.
- Middleware architecture: When to recommend point-to-point integration vs. middleware (MuleSoft, Dell Boomi) vs. a custom ESB, and the governance implications of each choice.
- Security for integrations: OAuth flows (User-Agent, Username-Password, JWT Bearer, Web Server), Named Credentials, and certificate management for secure system-to-system communication.
Section Weightings to Prioritise
Integration Architecture + Platform Architecture = 50%. Integration pattern selection is your single most important study topic.
Scenario Strategy: How to Approach Integration Questions
Every Integration Architect question describes an integration requirement and asks which pattern or technology fits. Answer by identifying three constraints: volume, latency requirement, and system ownership.
- High volume + batch = Bulk API. Real-time + low latency = REST API. Event-driven = Platform Events. Message queue = MuleSoft or custom middleware. Learn this decision matrix cold.
- For middleware questions: point-to-point is fast but creates spaghetti as systems multiply. Recommend middleware whenever the scenario involves 3+ integrated systems or complex transformation requirements.
- For security questions: know all four OAuth flows and when to use each. JWT Bearer = server-to-server without user interaction. Web Server = user-initiated. Username-Password = legacy/not recommended. User-Agent = deprecated.
- For Change Data Capture questions: CDC is for near-real-time sync of Salesforce changes to external systems. Platform Events is for publishing custom events. Know the difference and when each applies.
How to Know You’re Ready
80%+ on 3 timed full mocks before booking
Integration Architect has a lower first-attempt pass rate than most architect component exams. The questions require genuine integration project experience, candidates who have only studied theory consistently fail middleware and OAuth flow questions.
3 Concepts That Fail Most Integration Architect Candidates
These are not the hardest topics; they are the ones where candidates are most confidently wrong. Learn the distinction early.
1. Real-Time vs Near-Real-Time vs Batch: Choosing the Right Integration Pattern
Real-time integration executes synchronously during a transaction (callout mid-save), adds latency and risk of timeout. Near-real-time uses Platform Events or Change Data Capture to trigger async processing within seconds. Batch syncs data on a schedule (hourly, nightly). Candidates recommend real-time callouts for data that needs to be "current", the exam expects near-real-time (Platform Events) for that pattern and real-time only for blocking decisions (credit checks, inventory holds).
2. Idempotency: Why Retry Logic Requires Idempotent Operations
An idempotent operation produces the same result whether executed once or multiple times. Integration retries can cause duplicate records or double-charges if operations are not idempotent. Exam scenarios about retry handling expect idempotency design: use upsert (not insert) on retry, include a correlation ID, check if a record already exists before creating. Candidates design retry without idempotency safeguards.
3. Salesforce Connect vs Heroku Connect vs MuleSoft: Three Different Integration Approaches
Salesforce Connect exposes external data as External Objects in real time without importing it (best for small record sets queried infrequently). Heroku Connect maintains a Postgres replica of Salesforce data for high-performance querying. MuleSoft API-led connectivity builds reusable integration APIs across systems. Candidates recommend MuleSoft for all integration scenarios, the exam tests which tool fits the specific requirement.
FAQs From Candidates
- What is the Salesforce Integration Architect exam format?
- The Salesforce Integration Architect exam has 60 multiple-choice questions, a 120-minute time limit, a 67% passing score, and a $200 fee. It is a component exam for the System Architect role-based credential and tests integration strategy, API patterns, and middleware architecture.
- What are the highest-weight Integration Architect exam sections?
- Integration Architecture (27%) and Salesforce Platform Architecture (23%) together account for 50% of the exam. API design patterns, middleware selection (MuleSoft vs. point-to-point vs. custom), and Platform Events are the most heavily tested topics.
- What prerequisites do I need for the Integration Architect exam?
- There are no hard prerequisites, but Salesforce recommends Platform Developer I (PD1) and experience with REST/SOAP APIs before attempting Integration Architect. Real integration project experience, connecting Salesforce to ERP, marketing, or billing systems, is essential for the scenario-based questions.
- What is the difference between Integration Architect and Platform Developer II for integrations?
- Platform Developer II tests how to write integration code (REST callouts, SOAP, Named Credentials, HttpCalloutMock). Integration Architect tests when and how to choose the right integration pattern at an architectural level: REST vs. SOAP vs. bulk API vs. streaming, middleware vs. point-to-point vs. ESB, and security architecture for integrations.
- What concepts do most Integration Architect candidates get wrong?
- The most commonly misunderstood topics for the Integration Architect exam are: (1) Real-Time vs Near-Real-Time vs Batch: Choosing the Right Integration Pattern; (2) Idempotency: Why Retry Logic Requires Idempotent Operations; (3) Salesforce Connect vs Heroku Connect vs MuleSoft: Three Different Integration Approaches. Candidates are most confidently wrong on these. Learn the distinctions early to avoid losing marks on questions you expect to get right.
- Why do most Integration Architect candidates fail questions about Real-Time vs Near-Real-Time vs Batch?
- Real-time integration executes synchronously during a transaction (callout mid-save), adds latency and risk of timeout. Near-real-time uses Platform Events or Change Data Capture to trigger async processing within seconds. Batch syncs data on a schedule (hourly, nightly). Candidates recommend real-time callouts for data that needs to be "current", the exam expects near-real-time (Platform Eve...
- Why do most Integration Architect candidates fail questions about Idempotency?
- An idempotent operation produces the same result whether executed once or multiple times. Integration retries can cause duplicate records or double-charges if operations are not idempotent. Exam scenarios about retry handling expect idempotency design: use upsert (not insert) on retry, include a correlation ID, check if a record already exists before creating. Candidates design retry without id...
- Why do most Integration Architect candidates fail questions about Salesforce Connect vs Heroku Connect vs MuleSoft?
- Salesforce Connect exposes external data as External Objects in real time without importing it (best for small record sets queried infrequently). Heroku Connect maintains a Postgres replica of Salesforce data for high-performance querying. MuleSoft API-led connectivity builds reusable integration APIs across systems. Candidates recommend MuleSoft for all integration scenarios, the exam tests w...
Start Integration Architect Prep
After this exam, consider Application Architect or System Architect next.
Share or cite this study guide
Free to link from a forum post, study repo or article. Copy the Markdown and paste it anywhere.