Integration Architecture Designer tests whether you can connect Salesforce to the rest of a business reliably. Scenarios describe systems, data volumes and timing needs, and you choose the pattern, the API and the way failures are handled.
Start with the patterns
Salesforce documents common integration patterns, and they give you a vocabulary for every scenario:
- Request and reply: Salesforce calls another system and waits for the answer.
- Fire and forget: Salesforce sends a message and carries on.
- Batch data synchronisation: large volumes moved on a schedule.
- Remote call-in: another system creates or updates Salesforce data.
- UI update based on data changes: the screen reflects changes as they happen.
- Data virtualisation: data stays in its own system and is shown in Salesforce without copying it.
What to learn
Salesforce integration options
The REST, SOAP and Bulk APIs; Platform Events, Change Data Capture and the Pub/Sub API for events; Salesforce Connect and external objects for data that stays outside; and middleware such as MuleSoft for orchestration.
Enterprise patterns
Choosing synchronous or asynchronous designs, handling high volumes within API limits, and when middleware beats point-to-point connections.
Governance
Authentication with OAuth and Named Credentials, error handling and retries, monitoring, and making sure one failing system does not take others down.
How to study it
- Read each scenario for three facts: how much data, how fast it must arrive, and which system starts the exchange. They usually decide the answer.
- Plan for failure. For every design, ask what happens when the other system is down.
- Try the APIs. A few calls with the Salesforce CLI or a REST client make the options concrete.
Check the official guide
Salesforce sets the exam format, passing score and price, and updates the topics over time. Read the current exam guide on Trailhead before you book.
How Arkton helps
The Integration Architecture Designer course has 16 lessons with hands-on labs and exam preparation, about 14 hours of material. Developers often come to it from Platform Developer II.