Integration-Architect Exam Study Guide: The Ultimate 2026 Practice Test

Managing a " big surge " of requests requires an architecture that is decoupled and scalable. The Remote Process Invocation—Fire and Forget pattern is specifically designed to handle high-concurrency spikes where the user does not need an immediate functional response from the target system. 67

In this scenario, if NTO used Request and Reply (Option C), each user thread in Salesforce would remain open and " waiting " for the scheduling system to process room capacity. During a surge, this would quickly exhaust Salesforce ' s concurrent request limits , leading 8 to 503 " Service Unavailable " errors for all community users. 9

By using Fire and Forget , the following happens: 10

Capture Intent: The co 11 mmunity user clicks " Register. " Salesforce captures the registration and immediately publishes a message (e.g., via a Platform Event or Outbound Message).

Acknowledgment: Salesforce receives a simple technical acknowledgment that the message was received by the bus or middleware and then releases the user thread.

Asynchronous Processing: The middleware or event bus " buffers " the requests and delivers them to the scheduling system at a rate it can handle.

This pattern protects both Salesforce and the scheduling system from being overwhelmed. Batch Data Synchronization (Option B) would be too slow for users who expect a " Registered " status within a reasonable timeframe (near-real-time). Fire and Forget ensures the community remains performant and responsive during the critical launch window while maintaining the integrity of the registration data.

To minimize downtime when an external endpoint changes, an Integration Architect must ensure that the URL is not " hardcoded " within Apex code or configuration. The standard Salesforce mechanism for abstracting and managing external endpoints is Named Credentials .

Named Credentials specify the URL of a callout endpoint and its required authentication parameters in one definition. If the URL changes, an administrator simply updates the " URL " field in the Named Credential setup. This change takes effect immediately across all Apex callouts, Flows, and External Services that reference it, without requiring a code deployment or a sandbox-to-production migration.

Along with Named Credentials, Remote Site Settings (or the more modern External Website Configurations ) are required. Salesforce blocks all outbound calls to URLs that are not explicitly whitelisted.

By having both in place, the remediation process is:

Update the URL in the Named Credential .

Update (or add) the new URL in the Remote Site Settings .

This approach follows the " Separation of Concerns " principle. Option B (ESB) could technically handle this, but it adds an extra layer of failure and complexity for a simple URL change. Option C (Content Security Policies) is used to control which resources (like scripts or images) a browser is allowed to load in the UI; it does not govern server-side Apex callouts. Therefore, the combination of Named Credentials and Remote Site whitelisting is the most efficient and standard way to provide architectural agility and minimize downtime.

To provide " instant access " and a seamless experience for Community (Experience Cloud) users, the architect must choose an authentication and provisioning strategy that handles user creation on-the-fly. While both SAML and OpenID Connect (OIDC) are viable for SSO, OpenID Connect is the modern standard for consumer-facing " Social " or external identity integrations because it is built on OAuth 2.0.

The critical component for " self-service " is the Registration Handler . When an OpenID Connect Authentication Provider is configured in Salesforce, you must associate it with an Apex class that implements the Auth.RegistrationHandler interface. This handler is executed during the SSO flow if the user does not already exist. It provides the architect with full programmatic control to:

Match the incoming identity to an existing Contact or Account.

Create a new Contact record if one doesn ' t exist.

Provision a new User record with the correct Profile, Permission Sets, and Locale settings.

Link the User to the correct Account hierarchy, which is vital for Community security models.

Option A suggests Just-in-Time (JIT) provisioning , which is a declarative way to create users. However, JIT is often too rigid for Experience Cloud requirements, as it has limited ability to perform complex data lookups or handle the specific linking of Contacts to Accounts required for external users. Option C is technically mismatched in common Salesforce terminology; while SAML uses JIT, the Registration Handler is the native, specific mechanism designed to work with Authentication Providers (like OIDC). By using B, the company ensures that a subscriber logging in for the first time via the IAM system is instantly and accurately provisioned in Salesforce, eliminating the need for multiple accounts.