SALESFORCE CERTIFICATION
Certified Platform Integration Architect Practice Exam
Exam Number: 3708 | Last updated 14-Apr-26 | 2965+ questions across 6 vendor-aligned objectives
The Integration Architect credential validates your ability to design and evaluate integration solutions that connect Salesforce with external systems. It covers middleware patterns, API strategies, event-driven architecture, and data synchronization across complex enterprise landscapes involving ERP, marketing automation, and custom applications.
The Integration Architecture domain weighs in at 25%, covering patterns, middleware, API strategy, and solution design. With 25% of the exam, Salesforce Integration APIs demands serious preparation, covering REST, SOAP, Bulk, Streaming, Pub/Sub, and Composite APIs. Questions on data integration make up 20% of the test, covering real-time vs. batch, data synchronization, and conflict resolution. Candidates who master these top-weighted areas position themselves well for the majority of exam questions.
The remaining sections balance the blueprint. Expect about 15% of exam content to cover Security and Authentication, which spans OAuth for integrations, certificates, and named credentials. Error Handling and Monitoring commands 15% of the blueprint, which spans retry logic, dead letter queues, logging, and alerting. Although individually lighter, these topics frequently appear in scenario-based questions that blend multiple skill areas.
Every answer links to the source. Each explanation below includes a hyperlink to the exact Salesforce documentation page the question was derived from. PowerKram is the only practice platform with source-verified explanations. Learn about our methodology →
312
practice exam users
92.6%
satisfied users
92.9%
passed the exam
4.3/5
quality rating
Test your Certified Integration Architect knowledge
10 of 2965+ questions
Question #1 - Connect and synchronize real-time vs. batch, data synchronization, and conflict resolution to keep data flowing reliably between Salesforce and external systems with minimal latency
A retail company needs to synchronize customer data between Salesforce and their on-premise ERP. Changes in either system should be reflected within 5 minutes, handling up to 50,000 record changes per day.
Which integration pattern should the architect recommend?
A) Salesforce Connect with an OData adapter to the ERP
B) A synchronous REST API call on every record save in both systems
C) A near-real-time bidirectional sync using Change Data Capture events and middleware
D) Batch integration with a nightly file exchange
Show solution
Correct answers: C – Explanation:
Change Data Capture provides near-real-time notification of Salesforce data changes for middleware to consume and push to the ERP. Nightly batch is too infrequent. Synchronous calls create tight coupling. Salesforce Connect provides read-only virtual access. Source: Trailhead: Change Data Capture
Question #2 - Wire up and maintain patterns, middleware, and API strategy to keep data flowing reliably between Salesforce and external systems with minimal latency
An architect is designing a solution where Salesforce calls an external credit check API during opportunity approval. The API sometimes takes up to 30 seconds to respond.
How should the architect handle the long-running callout?
A) Make a synchronous callout from an Apex action
B) Use a Continuation in a Lightning component for an asynchronous callout that updates the UI when done
C) Store the request in a custom object and have a scheduled job poll the API
D) Use a @future method and email the result
Show solution
Correct answers: B – Explanation:
Continuation allows Lightning components to make asynchronous callouts without blocking the UI. Synchronous callouts risk timeout errors. Scheduled polling introduces delay. @future methods cannot return results to the UI. Source: Salesforce Docs: Lightning Aura Guide
Question #3 - Enforce and audit OAuth for integrations, certificates, and named credentials to safeguard sensitive data and enforce least-privilege access across the organization
A logistics company integrates Salesforce with five external systems, each using different authentication mechanisms.
Which Salesforce feature should manage these diverse authentication requirements?
A) Named Credentials configured for each external system
B) Store all credentials in a custom metadata type
C) Custom settings with encrypted fields for passwords
D) A single Connected App for all five integrations
Show solution
Correct answers: A – Explanation:
Named Credentials abstract authentication complexity by securely storing endpoint URLs and credentials for each system. Custom metadata and custom settings expose credentials in code. A Connected App manages inbound authentication, not outbound. Source: Salesforce Help: Named Credentials About
Question #4 - Wire up and maintain patterns, middleware, and API strategy to keep data flowing reliably between Salesforce and external systems with minimal latency
An e-commerce platform pushes 100,000 orders per day to Salesforce. Data must be available within 2 hours of order creation.
Which API should the integration architect recommend?
A) Bulk API 2.0 with periodic batch submissions
B) Streaming API to push orders in real time
C) REST API with individual record inserts
D) Metadata API to create Order records
Show solution
Correct answers: A – Explanation:
Bulk API 2.0 is optimized for large volumes with parallel processing. REST API is inefficient at this scale. Streaming API is for Salesforce outbound, not inbound loading. Metadata API handles metadata, not data records. Source: Salesforce Docs: Bulk API Guide
Question #5 - Wire up and maintain patterns, middleware, and API strategy to keep data flowing reliably between Salesforce and external systems with minimal latency
A healthcare org needs to orchestrate a multi-step integration: patient creation must sequentially trigger billing, insurance verification, and appointment scheduling, each dependent on the previous step.
What integration approach should the architect recommend?
A) Three sequential @future callouts from the trigger
B) An event-driven architecture using Platform Events with middleware orchestrating sequential steps
C) A single composite API call to all three systems
D) A Batch Apex class that processes new patients and calls all three systems
Show solution
Correct answers: B – Explanation:
Middleware orchestration with Platform Events decouples Salesforce from sequential logic, handling errors and retries at each step. Sequential @future calls cannot guarantee order. Composite API is for Salesforce API calls, not external systems. Batch Apex introduces latency. Source: Trailhead: Platform Events
Question #6 - Integrate and monitor REST, SOAP, and Bulk to keep data flowing reliably between Salesforce and external systems with minimal latency
An external system makes 15,000 API calls per hour to a Salesforce org with a 100,000 daily limit. The limit will be exhausted within 7 hours.
What should the architect do to reduce API consumption?
A) Migrate from REST API to SOAP API
B) Replace polling with Salesforce-initiated push notifications using Change Data Capture or Platform Events
C) Request Salesforce to increase the API limit
D) Reduce the polling frequency to every 10 minutes
Show solution
Correct answers: B – Explanation:
Push-based notifications via CDC or Platform Events eliminate redundant polling calls. Increasing limits is a temporary fix. Reducing frequency sacrifices freshness. SOAP and REST have similar API limit impacts. Source: Trailhead: Change Data Capture
Question #7 - Wire up and maintain patterns, middleware, and API strategy to keep data flowing reliably between Salesforce and external systems with minimal latency
A company needs to create an Account, Contact, and Opportunity in Salesforce through a single API request, with all records succeeding or failing together.
Which API approach should the integration architect use?
A) A custom Apex REST endpoint that accepts all records
B) Three separate REST API calls wrapped in a try-catch externally
C) The Bulk API with a single batch containing all three types
D) The Composite API with allOrNone set to true
Show solution
Correct answers: D – Explanation:
The Composite API allows multiple operations in a single request with allOrNone for transactional integrity. It supports referencing outputs of prior subrequests. Separate calls risk partial failures. Bulk API is for single-object operations. Custom Apex adds development effort for a built-in capability. Source: Salesforce Docs: REST API Guide
Question #8 - Wire up and maintain patterns, middleware, and API strategy to keep data flowing reliably between Salesforce and external systems with minimal latency
An external system needs real-time push notifications when specific fields on Salesforce Contact records change, such as Email or Phone.
Which Salesforce feature should the architect configure?
A) A Visualforce page monitored by the external system
B) Change Data Capture events subscribed via Pub/Sub API
C) Outbound Messages in a workflow rule
D) A scheduled Apex job that checks for changes
Show solution
Correct answers: B – Explanation:
Change Data Capture publishes events on record changes. The external system subscribes via Pub/Sub API for real-time notifications. Outbound Messages use legacy workflow rules. Scheduled jobs introduce delays. Visualforce pages cannot be monitored externally. Source: Trailhead: Change Data Capture
Question #9 - Connect and synchronize real-time vs. batch, data synchronization, and conflict resolution to keep data flowing reliably between Salesforce and external systems with minimal latency
A global company with Salesforce orgs in three regions needs a unified view of customer data at headquarters without replicating data.
Which integration strategy should the architect implement?
A) Deploy Salesforce Connect with cross-org adapters in the headquarters org
B) Build custom REST APIs in each regional org for nightly queries
C) Use Salesforce-to-Salesforce connections with published objects
D) Consolidate all three orgs into one
Show solution
Correct answers: A – Explanation:
Salesforce Connect with cross-org adapters provides real-time virtual access without replication. Consolidation disrupts regional operations. Salesforce-to-Salesforce is limited. Nightly queries introduce staleness. Source: Trailhead: Salesforce Connect
Question #10 - Wire up and maintain patterns, middleware, and API strategy to keep data flowing reliably between Salesforce and external systems with minimal latency
An integration architect needs to implement error handling for a Salesforce-to-SAP integration. Some errors are transient (network timeouts) and others are permanent (invalid data).
What error-handling pattern should the architect implement?
A) Use a global try-catch that suppresses all errors
B) Disable error handling to let transactions fail naturally
C) Implement exponential backoff retry for transient errors and route permanent errors to a dead letter queue with alerts
D) Log all errors to a custom object for manual retry
Show solution
Correct answers: C – Explanation:
Exponential backoff handles transient errors automatically. Permanent errors go to a dead letter queue for investigation. Logging all errors with manual retry creates backlogs. Disabling error handling risks data loss. Suppressing errors hides problems. Source: Salesforce Docs: Integration Patterns Guide
Get 2965+ more questions with source-linked explanations
Every answer traces to the exact Salesforce documentation page — so you learn from the source, not just memorize answers.
Exam mode & learn mode · Score by objective · Updated 14-Apr-26
Learn more...
What the Certified Integration Architect exam measures
- Wire up and maintain patterns, middleware, and API strategy to keep data flowing reliably between Salesforce and external systems with minimal latency
- Integrate and monitor REST, SOAP, and Bulk to keep data flowing reliably between Salesforce and external systems with minimal latency
- Connect and synchronize real-time vs. batch, data synchronization, and conflict resolution to keep data flowing reliably between Salesforce and external systems with minimal latency
- Enforce and audit OAuth for integrations, certificates, and named credentials to safeguard sensitive data and enforce least-privilege access across the organization
- Deliver and support retry logic, dead letter queues, and logging to deliver reliable platform solutions that meet real-world business demands
How to prepare for this exam
- Review the official exam guide to confirm full topic coverage
- Complete the Integration Architecture trail on Trailhead — pay special attention to API-led connectivity and event-driven patterns
- Build an integration between a Salesforce Developer Org and an external system using REST API and named credentials
- Get involved in an integration project at your workplace — even documenting existing integrations teaches you to evaluate architectural decisions
- Start with the two highest-weighted objectives — Integration Architecture and Salesforce Integration APIs
- Use PowerKram’s learn mode to master integration patterns through scenario-based practice
- Validate your readiness in PowerKram’s exam mode with timed, full-length tests
Career paths and salary outlook
Integration architects are critical for enterprises connecting Salesforce with their broader tech stack:
- Salesforce Integration Architect — $150,000–$200,000 per year, designing cross-platform integration solutions (Glassdoor salary data)
- Enterprise Integration Architect — $155,000–$210,000 per year, leading integration strategy across cloud and on-premise systems (Indeed salary data)
- MuleSoft Architect — $145,000–$195,000 per year, specializing in API-led connectivity and MuleSoft Anypoint Platform (Glassdoor salary data)
Official resources
Follow the Integration Architect Learning Path on Trailhead. The official exam guide provides the complete objective breakdown.