INTEGRATION-ARCHITECTURE-DESIGNER practice question 9 of 25

Northern Trail Outfitters (NTO) has recently implemented middleware for orchestration of services across platforms. The ERP system being used…

Full set: 106 questions

Domain Design an Integration Solution

Northern Trail Outfitters (NTO) has recently implemented middleware for orchestration of services across platforms. The ERP system being used requires transactions be captured near real time at a REST endpoint initiated in Salesforce when creating an order object. Additionally, the Salesforce team has limited development resources and requires a low code solution. Which two options will fulfill the use case requirements? Choose 2 answers
Answer options
A: Use Remote Process Invocation fire and forget pattern on insert on the order object using Flow Builder. Correct answer
B: Implement a Workflow Rule with Outbound Messaging to send SOAP messages to the designated endpoint.
C: Implement Change Data Capture on the order object and leverage the replay Id in the middleware solution. Correct answer
D: Use a process builder to create a Platform Event, selecting the record type as the Platform Event Name on insert of record.
Correct Answer:
A. Use Remote Process Invocation fire and forget pattern on insert on the order object using Flow Builder.; C. Implement Change Data Capture on the order object and leverage the replay Id in the middleware solution.
Explanation

This scenario requires a near real-time, low-code solution to notify an external ERP system with a REST endpoint when an Order is created.
Option A, Remote Process Invocation (Fire and Forget) using Flow Builder, directly meets the requirements. Flow Builder is a low-code tool that can be configured to make an immediate, asynchronous callout to a REST endpoint upon record creation. This pattern sends the data without waiting for a response, which is suitable for near real-time transaction capture.
Option C, Change Data Capture (CDC), is a highly scalable, event-driven, low-code solution. Enabling CDC on the Order object declaratively publishes change events in near real-time. The existing middleware can subscribe to this event stream, receive the new order data, and perform the required orchestration by calling the ERP's REST endpoint. This decouples the systems effectively.

Why Incorrect

B. Implement a Workflow Rule with Outbound Messaging to send SOAP messages to the designated endpoint. This is incorrect because Outbound Messaging uses the SOAP protocol, while the requirement explicitly states the ERP system has a REST endpoint.
D. Use a process builder to create a Platform Event, selecting the record type as the Platform Event Name on insert of record. While technically possible, Change Data Capture (Option C) is the purpose-built and more efficient feature for broadcasting Salesforce record changes to external systems for synchronization purposes.

References

1. Change Data Capture: The Salesforce Change Data Capture Developer Guide states

"Change Data Capture is a streaming product on the Lightning Platform that enables you to efficiently integrate your Salesforce data with external systems... Change Data Capture publishes change events

which represent changes to Salesforce records." This aligns with option C as a low-code

near real-time solution for notifying the middleware.

Source: Salesforce Change Data Capture Developer Guide

"Change Data Capture Basics" section.

2. Flow for REST Callouts (Remote Process Invocation): The Salesforce Flow Documentation details how to use HTTP Callout actions within a record-triggered flow. "Make a callout from a record-triggered flow that’s configured to run in the background. The callout is made after the original transaction is completed

which helps you avoid failures and keep your automations fast." This supports option A as a low-code method for invoking a REST endpoint.

Source: Salesforce Help

"Make HTTP Callouts from Flow" article.

3. Integration Patterns: The Salesforce Architect's Handbook: A-to-Z Guide to Salesforce Integration (a well-regarded academic-style text on the subject) discusses both patterns. It describes Remote Process Invocation (Fire-and-Forget) for simple

direct calls and event-based patterns using Change Data Capture for decoupled

scalable integrations

validating both A and C as appropriate solutions.

Source: Salesforce Architect's Handbook

Chapter 4: "Salesforce Integration Patterns and Best Practices".

4. Outbound Messaging Protocol: The Salesforce SOAP API Developer Guide confirms the protocol used by Outbound Messaging. "Outbound messaging sends a SOAP message to a designated endpoint..." This explicitly invalidates option B.

Source: Salesforce SOAP API Developer Guide

"Setting Up Outbound Messaging" section.

Scroll to Top