Salesforce Integration Arch Exam Practice Test
Salesforce integration architecture connects org data and business events with external applications through APIs, callouts, and event-driven patterns. The practice bank touches on locating records by external identifiers, discovering object metadata at runtime, handling OAuth token expiry, and configuring outbound connections without embedding credentials in Apex.
Exam overview
About the Salesforce Integration Arch Exam
Integration design requires choosing how systems exchange data and how each side responds to failures. REST resources can support conditional requests with HTTP mechanisms such as ETags, while external identifiers provide a way to match records without depending on Salesforce IDs. Runtime metadata discovery helps clients adapt to object fields and relationships without a fixed schema. For outbound communication, architects weigh centrally managed endpoint and authentication settings against code-level configuration. Resilient designs account for transient service failures, retries, and duplicate delivery: retry policies should preserve pending work, and idempotent processing should prevent a repeated request from applying the same business action twice. Event-based integration can decouple producers from multiple consumers, but consumers must tolerate duplicate notifications and process them safely.
Sample Practice Questions
Review a selection from this exam's published US Practice Tests practice bank.
A Salesforce record contains a field that stores an identifier assigned by an external system. The integration needs to use that identifier to locate the record without relying on Salesforce record IDs. Which field configuration is most useful?
Show answer
Correct answer: AAn External ID field can store an external system’s identifier and supports matching records by that identifier in integration operations. It can also be configured as unique when the identifier must not be duplicated.
An external integration needs to determine which fields and relationships are available on a Salesforce object at runtime rather than relying on a hard-coded schema. Which API capability is intended for this purpose?
Show answer
Correct answer: AAn sObject describe request returns metadata about an object, including its fields and relationship information. This allows a client to inspect schema details dynamically before constructing data operations.
An integration client uses OAuth access tokens to call Salesforce APIs. What should the client generally do when an API request returns an authentication error because the access token has expired?
Show answer
Correct answer: AOAuth access tokens have lifetimes. The client should obtain a valid token through the configured OAuth process, such as a refresh-token flow where applicable, and then retry safely. Credentials should not be sent with every API request.
An integration exchanges data with a service that may return temporary failures. The design must avoid losing work and should prevent a retry from repeating an already completed business action. Which combination is most appropriate?
Show answer
Correct answer: ADurable retry handling preserves work across transient failures, while a stable idempotency key lets the receiving side recognize repeated attempts as the same logical operation. Backoff and retry limits are also commonly used.
A client needs to detect whether a Salesforce record has changed since it last retrieved that record, without fetching every field again. Which HTTP mechanism is commonly used with Salesforce REST resources for conditional requests?
Show answer
Correct answer: ASalesforce REST resources can support conditional requests using timestamps such as If-Modified-Since, allowing a client to check whether a resource changed since a specified time. The other headers serve different purposes, such as describing payload format or authentication.
A team wants to manage an integration’s endpoint and authentication configuration without placing secrets directly in Apex code. Which Salesforce feature is designed to store endpoint connection details and support authentication configuration?
Show answer
Correct answer: ANamed Credentials provide a managed way to define an endpoint and associated authentication settings for callouts, reducing the need to hard-code connection details and credentials in Apex. The other choices are not intended for managing authenticated endpoint connections.
An external application needs to make an outbound HTTP request from Salesforce to a service whose hostname is allowlisted in Salesforce configuration. What must Apex generally use to identify the endpoint?
Show answer
Correct answer: AA Named Credential provides a configured endpoint and can also centralize authentication settings. Apex callouts can reference it rather than hard-coding the host and related connection details.
How to use this practice test
Access is free. Each session draws up to 20 random questions from the 50-question practice bank and displays results when the session ends. Use the scenarios to test integration choices, then review missed items by tracing the relevant API behavior, configuration option, or failure-handling principle.
Preparation tips
- Compare Salesforce record IDs with external ID fields, and identify when an upsert or external-key lookup avoids dependence on Salesforce-generated IDs.
- Practice using object describe or metadata capabilities to determine available fields and relationships at runtime rather than assuming a fixed schema.
- Trace OAuth expiry and transient service-failure scenarios; distinguish refreshing credentials from retrying a business operation, and consider idempotency before replaying requests.
- Review how Named Credentials centralize endpoint and authentication settings, and how Apex callouts reference configured endpoints.
- For event-driven designs, map producer and consumer responsibilities, including independent processing schedules and deduplication of repeated notifications.