Northern Trail Outfitters has a registration system that is used for workshops offered at its conferences. Attendees use Salesforce Community to…

The scenario describes a need to handle a "big surge of requests" without overwhelming the backend scheduling system. The "Remote Process Invocation—Fire and Forget" pattern is an asynchronous integration style ideal for this situation. Salesforce accepts the registration request and immediately sends it to the backend system without waiting for a response. This decouples the systems, allows the user interface to remain responsive, and enables the backend system to process the queued requests at its own pace, ensuring high availability and a good user experience during peak load.

A. This synchronous pattern would force the user to wait for the backend system to process the request, likely causing timeouts and failures during a high-volume surge.

C. Batch Data Synchronization is for processing large data volumes on a schedule (e.g., nightly) and is not suitable for handling real-time, user-initiated transactions.

1. Salesforce, Integration Patterns and Practices, Page 14, "Remote Process Invocation—Fire and Forget". The document states this pattern is appropriate when "The remote system is unable to process requests in a timely fashion" and "A response is not required, or can be received at a later time." This perfectly matches the surge scenario.

2. Salesforce Architects, The Salesforce Architect's Handbook, "Chapter 10: Integration Architecture and Patterns", Section on Asynchronous Patterns. This section explains how fire-and-forget patterns using Platform Events or Outbound Messages prevent system overloads during traffic spikes.