Salesforce Platform Integration Architect (Plat-Arch-204) Practice Exam
Design secure, scalable integrations on the Salesforce Platform — patterns, APIs, authentication, and large-data-volume trade-offs — with objective-mapped questions, source-linked explanations in Learn mode, and a full timed simulation in Exam mode.
Start 24-hour free trial →Platform Integration Architect exam at a glance
- Vendor
- Salesforce
- Exam code
- Plat-Arch-204
- Credential
- Salesforce Certified Platform Integration Architect
- Level
- Architect (advanced)
- Blueprint
- Exam guide aligned to the Summer ’23 release; verify current edition before scheduling
- Format
- 60 multiple-choice / multiple-select questions, plus up to 5 unscored
- Duration
- 105 minutes
- Passing score
- 67%
- Delivery
- Onsite at a Pearson VUE test center or online proctored
- Prerequisites
- None required. Salesforce assumes 1–2 years of Salesforce integration experience plus broader admin/development background.
- Cost (USD)
- $400 registration; $200 retake (plus local taxes)
- Validity
- Does not expire; keep current via annual Trailhead maintenance modules
Source: Salesforce — Platform Integration Architect credential and its linked exam guide. Verify current details with Salesforce before scheduling.
About the Salesforce Platform Integration Architect certification
The Platform Integration Architect is an architect-level, Salesforce-native credential. It certifies that you can assess a system landscape and design end-to-end integrations between Salesforce and external systems that are secure, scalable, and maintainable — and that you can explain the trade-offs to both business and technical stakeholders. It is a design-and-decision exam, not a coding exam: expect scenarios where you choose the right pattern, API, and authentication approach given constraints like data volume, latency tolerance, and who initiates the call.
A common point of confusion is worth settling up front: this exam is distinct from the MuleSoft Platform Integration Architect (Mule-Arch-202). This one covers Salesforce’s own integration surface — REST, SOAP, Bulk, Streaming, Composite, Platform Events, Change Data Capture, Named Credentials, Connected Apps, Outbound Messaging — while the MuleSoft credential covers Anypoint Platform and Mule runtimes. Studying MuleSoft material for this exam is a mismatch. For the concepts behind every objective area, see the Salesforce integration patterns guide.
The credential is one of the architect building blocks that ladder up to the System Architect and, ultimately, the Certified Technical Architect (CTA). Because it does not expire, keeping it current is a matter of completing the short annual maintenance module on Trailhead rather than re-sitting the exam.
Platform Integration Architect objective areas and weights
The exam guide lists six objective areas. The percentage split below is the widely-cited third-party weighting used across major study guides — useful for planning study time, but read the vendor caveat under the table.
The heart of the exam: given requirements and constraints, select the right integration pattern (Request–Reply, Fire-and-Forget, Batch Data Sync, Remote Call-In, UI update on data change) and the Salesforce technology that implements it.
Turn the design into a concrete implementation approach: choose among REST, SOAP, Bulk, Streaming, Composite, Platform Events, and Change Data Capture, and design for scalability and large data volumes.
Convert business needs into functional and non-functional integration requirements, including authentication/authorization, data classification (confidential / secure / public), and growth and regulatory factors.
Identify existing standards, limits, boundaries, and protocols; analyze constraints and pain points; and assess the authentication and authorization the landscape already imposes.
Identify functional vs non-functional needs, the CRM-success factors that belong in the integration, and the business-growth or regulatory pressures that shape the choice of solution.
Monitor, troubleshoot, and sustain integrations in production — error handling, retries, and observability of the interfaces once they are live.
Note: Salesforce’s official exam guide publishes the six objective areas but does not publish a per-area percentage table. The weights above reflect consistent third-party study-guide estimates and should be treated as planning guidance, not vendor-published figures. Confirm the current objective list in the official Salesforce exam guide before you schedule.
Who the Platform Integration Architect exam is for
This is a specialist architect credential, not an entry point. Salesforce positions it for practitioners who already design integrations and now want to validate that expertise:
- Integration and solution architects who assess system landscapes and choose patterns, APIs, and middleware boundaries for Salesforce-to-external-system integrations.
- Senior Salesforce developers moving from building integrations to designing them — and who need to defend design trade-offs, not just implement a spec.
- Technical leads and enterprise architects responsible for data-heavy, regulated, or high-volume integrations where scalability and security decisions carry real risk.
- CTA candidates using this as one of the architect stepping-stones toward the System Architect and Technical Architect credentials.
If you are newer to the platform, the Platform Developer credential is a more appropriate starting point and builds the API fluency this exam assumes. For adjacent architect tracks, the Identity and Access Management Architect and Data Architect exams pair naturally with this one. For the roles this credential supports and where they lead, see our guide to Salesforce architect career paths.
What this Platform Integration Architect practice exam delivers
Learn mode
Get the correct answer, the reasoning, and a link to the exact Salesforce documentation each question derives from — immediately after each question. Best for the pattern-selection scenarios, where the “best” answer turns on one constraint in the stem.
Exam mode
60 questions on a 105-minute timer — the real Plat-Arch-204 format, including multiple-select items. Build the pacing and the discipline of reading each scenario for its governing constraint.
Source-linked explanations
Every answer cites the specific Salesforce developer or help doc (Bulk API 2.0, Change Data Capture, Named Credentials, and so on) so you can verify and go deeper rather than memorize.
Score by objective area
Results break down across the six exam objective areas, so practice tells you whether to spend your next session on pattern design, API selection, or authentication rather than “more questions.”
Sample Platform Integration Architect practice questions
Ten free questions across the exam’s objective areas, with full explanations and links to the Salesforce documentation each is derived from. The complete bank is available with the 24-hour trial.
Salesforce must send new orders to a fulfillment system. The business does not require the user to wait for a confirmation from fulfillment before continuing. Which pattern best fits?
- Request and Reply (synchronous)
- Fire-and-Forget (asynchronous)
- Remote Call-In
- UI Update Based on Data Changes
Show answer & explanation
Correct: B — Fire-and-Forget. Because the user does not need to wait for confirmation, the interaction is asynchronous. Fire-and-Forget lets Salesforce hand off the order and continue without blocking on a reply, which fits the stated latency tolerance.
Why not the others: Request and Reply (A) blocks the user until the remote system responds — the opposite of what’s needed. Remote Call-In (C) is when an external system initiates the call into Salesforce, not Salesforce pushing out. UI Update Based on Data Changes (D) refreshes a Salesforce UI when data changes, not an outbound order handoff.
Source: Salesforce Developers — Asynchronous integration patterns → Further reading: PowerKram — Salesforce Integration Patterns →An architect needs Apex callouts to an external REST service without storing the endpoint URL and credentials in code, and wants Salesforce to manage the authentication. What should they use?
- Hard-coded endpoint and credentials in the Apex class
- A Named Credential referencing the external endpoint
- A Remote Site Setting only
- A custom setting storing the password in plain text
Show answer & explanation
Correct: B — Named Credential. A Named Credential stores the endpoint URL and authentication settings outside the code and lets Salesforce handle the authentication for the callout, so secrets never live in Apex.
Why not the others: Hard-coding (A) exposes secrets and breaks on rotation. A Remote Site Setting alone (C) only allowlists the endpoint — it does not manage authentication. Storing a password in plain text in a custom setting (D) is an obvious security failure. This is the recommended, secret-free approach for outbound callouts.
Source: Salesforce Help — Named Credentials →A nightly job must load several million records into Salesforce from an external data warehouse with maximum throughput and minimal API-call overhead. Which API is the best fit?
- REST API with one call per record
- SOAP API single-record create calls
- Streaming API
- Bulk API 2.0
Show answer & explanation
Correct: D — Bulk API 2.0. Bulk API 2.0 is purpose-built for asynchronous loading of large data volumes; it batches records server-side and is optimized for throughput on millions of records, which is exactly the nightly-load scenario.
Why not the others: REST per-record (A) and SOAP single-record (B) would consume enormous numbers of calls and hit limits well before finishing. Streaming API (C) delivers event notifications to subscribers — it does not load records.
Source: Salesforce Developers — Bulk API 2.0 → Further reading: PowerKram — Large Data Volume Integration →A client application must create an account and its related contacts in a single request, and roll everything back if any part fails. Which REST capability supports this?
- A separate REST call per record with client-side coordination
- The Composite (or Composite Graph) REST resource with allOrNone enabled
- Outbound Messaging
- The Query resource
Show answer & explanation
Correct: B — Composite REST with allOrNone. The Composite resource executes a series of related subrequests in one call and can treat them as a single transaction, rolling all changes back if any subrequest fails — ideal for an account plus its contacts.
Why not the others: Separate calls (A) cannot guarantee atomic rollback across records. Outbound Messaging (C) is a SOAP-based outbound notification mechanism, not an inbound transactional write. The Query resource (D) reads data; it does not create records.
Source: Salesforce Developers — Composite REST resource →An external system must stay in near-real-time sync with changes to Salesforce records, receiving only the fields that changed, without polling. Which Salesforce feature fits best?
- Change Data Capture (CDC)
- A scheduled Bulk API export every hour
- Outbound Messaging on every object
- A nightly report subscription
Show answer & explanation
Correct: A — Change Data Capture. CDC publishes change events (create, update, delete, undelete) with the changed fields to subscribers in near real time over the event bus, so external systems stay in sync without polling.
Why not the others: Hourly Bulk export (B) and a nightly report (D) are batch and not near-real-time. Outbound Messaging (C) fires per workflow/flow action and sends a fixed message rather than a general change-event stream, and does not scale as cleanly for broad record-change sync.
Source: Salesforce Developers — Change Data Capture → Further reading: PowerKram — Event-Driven Integration on Salesforce →An architect wants a decoupled, publish-subscribe integration where Salesforce and external systems exchange custom business events with a defined schema. Which feature is designed for this?
- Field History Tracking
- Validation Rules
- Platform Events
- Big Objects
Show answer & explanation
Correct: C — Platform Events. Platform Events provide a defined event schema and a publish-subscribe model over the event bus, letting Salesforce and external systems communicate in a decoupled, event-driven way — publishers and subscribers do not need to know about each other.
Why not the others: Field History Tracking (A) logs field changes for audit, not integration. Validation Rules (B) enforce data quality on save. Big Objects (D) store very large data volumes for archival/analytics; they are not an eventing mechanism.
Source: Salesforce Developers — Platform Events →A middleware (ETL) tool must call into Salesforce to update records using the REST and Bulk APIs, authenticating via OAuth 2.0. Which Salesforce configuration is foundational to authorize it?
- A Connected App configured in Salesforce
- A Remote Site Setting in Salesforce
- A Named Credential in Salesforce
- A Platform Event definition
Show answer & explanation
Correct: A — Connected App. For an external system to access Salesforce APIs via OAuth 2.0, a Connected App is the foundational framework: it defines the OAuth settings and scopes that authorize the middleware to call in (this is a Remote Call-In scenario).
Why not the others: Remote Site Settings (B) and Named Credentials (C) govern outbound callouts from Salesforce, not inbound access. A Platform Event definition (D) is for eventing, not authorization.
Source: Salesforce Help — Connected Apps → Further reading: PowerKram — Authenticating Salesforce Callouts →A Salesforce UI must update in near real time when specific records change, so users see fresh data without refreshing. Which mechanism supports this on the client?
- A scheduled Apex job every five minutes
- Streaming API (PushTopic / event subscription)
- SOAP API polling from the browser
- Outbound Messaging
Show answer & explanation
Correct: B — Streaming API. The Streaming API pushes notifications to subscribed clients when matching records change, so a UI can update in near real time without polling — the “UI update based on data changes” pattern.
Why not the others: Scheduled Apex (A) is batch, not push. Browser SOAP polling (C) is exactly the polling this pattern avoids and scales poorly. Outbound Messaging (D) sends a message to an external endpoint on a workflow action; it does not update a Salesforce UI.
Source: Salesforce Developers — Streaming API →An architect needs Salesforce to notify an external system whenever an Opportunity reaches Closed Won, using a declarative, contract-first message that the external system can consume. Which option fits with the least custom code?
- Outbound Messaging triggered by a record-triggered flow
- A synchronous Apex REST callout on every save
- Bulk API 2.0 job
- A nightly CSV export
Show answer & explanation
Correct: A — Outbound Messaging. Outbound Messaging sends a SOAP message with a defined WSDL (contract-first) to an external endpoint when triggered by a flow, with built-in retry — a declarative, low-code fit for “notify on Closed Won.”
Why not the others: A synchronous Apex callout (B) is code-heavy and risks blocking the transaction. Bulk API 2.0 (C) is for large loads, not single-event notifications. A nightly CSV export (D) is batch and not event-driven.
Source: Salesforce Developers — Outbound Messaging →An external client needs a lightweight, stateless HTTP integration returning JSON for individual record operations from a mobile app. Which Salesforce API is the most appropriate choice?
- SOAP API
- Bulk API 2.0
- REST API
- Metadata API
Show answer & explanation
Correct: C — REST API. The REST API is lightweight, stateless, and returns JSON (or XML), which suits mobile and web clients doing individual record operations — the standard fit for this profile.
Why not the others: SOAP API (A) is heavier and XML/WSDL-based, better where strong contracts or legacy tooling demand it. Bulk API 2.0 (B) targets large asynchronous data loads, not single-record mobile calls. Metadata API (D) manages org configuration and metadata, not record data.
Source: Salesforce Developers — REST API → Further reading: PowerKram — Choosing a Salesforce API →Keep going: Learning & Career resources
Integration architecture rewards depth in two directions — the patterns and APIs themselves, and the architect career track this credential feeds. Both PowerKram hubs back this exam.
Deep dive: exam format, scoring, study path, and how this differs from MuleSoft
Exam format and scoring
Plat-Arch-204 delivers 60 scored multiple-choice / multiple-select questions (plus up to five unscored) in 105 minutes, with a 67% passing bar — roughly 40 correct. Multiple-select items ask you to pick more than one right answer, and partial credit is not given, so read the count the item asks for. The questions are scenario-driven: most give you a short business situation with one or two governing constraints (latency tolerance, data volume, who initiates the call, security posture) and ask for the best design. Read the integration-patterns deep dive →
How this differs from the MuleSoft Integration Architect exam
The single most common preparation mistake is studying the wrong exam. The Salesforce Platform Integration Architect (Plat-Arch-204) tests Salesforce’s native integration surface: REST, SOAP, Bulk, Streaming, Composite, Platform Events, Change Data Capture, Named Credentials, Connected Apps, and Outbound Messaging, plus the classic integration patterns. The MuleSoft Platform Integration Architect (Mule-Arch-202) tests Anypoint Platform, Mule runtimes, and API-led connectivity. They are separate credentials with separate exams. If your goal is the MuleSoft one, use the MuleSoft practice exam instead of this one.
Realistic study path
Salesforce’s Architect Journey Trailmix for this credential runs roughly 40–43 hours of content; most candidates layer several weeks of hands-on integration practice on top. A workable plan: study the integration patterns until you can name the pattern from the constraint in a stem, then map each pattern to its Salesforce implementation (which API or feature realizes it), then drill authentication (inbound Connected App / OAuth vs outbound Named Credential). Finish with timed Exam-mode simulations to build pacing on the multiple-select items. PowerKram’s per-objective scoring surfaces whether your gap is pattern design, API selection, or security. Read the “which Salesforce API” guide →
Authentication: the direction trap
A recurring exam theme is the direction of the call. Outbound from Salesforce (Apex callouts, flows calling external services) uses Remote Site Settings and, preferably, Named Credentials so Salesforce manages the auth and secrets stay out of code. Inbound to Salesforce (an ETL tool or external app calling the REST/Bulk APIs) uses a Connected App with OAuth 2.0 scopes. Many wrong answers are correct features pointed the wrong way — a Named Credential offered for an inbound scenario, or a Connected App offered for an outbound callout. Read the authentication guide →
Large data volumes and governor limits
Scalability questions almost always hinge on volume. Single-record REST or SOAP calls are fine for interactive, low-volume cases but collapse against millions of records and API limits; Bulk API 2.0 is the answer for high-throughput asynchronous loads. Big Objects, selective queries, and skinny/indexed access patterns show up when the scenario stresses very large data footprints. Recognizing the volume signal in the stem is often the whole question. Read the large-data-volume guide →
Maintenance and career outlook
Unlike time-boxed credentials, this certification does not expire; you keep it current with a short annual Trailhead maintenance module tied to each release. It sits on the architect ladder alongside the Application Architect and the other domain architect exams, feeding the System Architect designation and ultimately the Certified Technical Architect. It carries the most weight when paired with hands-on integration delivery and adjacent architect credentials. For roles and progression, see the Career Hub. Career Hub — Salesforce architect roles →
Frequently asked questions
Is the Salesforce Integration Architect exam the same as the MuleSoft one?
What are the Platform Integration Architect exam format and passing score?
Are there prerequisites for Plat-Arch-204?
How much does it cost, and what is the retake policy?
Does the certification expire?
Start your free 24-hour Platform Integration Architect practice trial
Full access to the question bank, both study modes, source-linked explanations, and score-by-objective. No credit card required.
Start free trial →