New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Plat-Arch-204 Exam - Topic 2 Question 2 Discussion

Actual exam question for Salesforce's Plat-Arch-204 exam
Question #: 2
Topic #: 2
[All Plat-Arch-204 Questions]

Northern Trail Outfitters uses Salesforce to track leads and opportunities, and to capture order details. However, Salesforce isn't the system that holds or processes orders. After the order details are captured in Salesforce, an order must be created in the Remote system, which manages the order's lifecycle. The integration architect for the project is recommending a remote system that will subscribe to the platform event defined in Salesforce. Which integration pattern should be used for this business use case?

Show Suggested Answer Hide Answer
Suggested Answer: B

In this scenario, Salesforce acts as the trigger for a business process that completes in an external system. The architect's recommendation for the remote system to subscribe to a platform event is the classic implementation of the Remote Process Invocation---Fire and Forget pattern.1

In a Fire and Forget pattern, Salesforce initiates a process by publishing a message (the event) to the event bus and then immediately continues its own2 processing without waiting for a functional response from the target system. The 'Fire' part occurs when the order details are captured and the event is published; the 'Forget' part refers to Salesforce handing off the responsibility of order creation to the remote system. This pattern is ideal for improving user experience and system performance, as it avoids blocking the user interface while waiting for potentially slow back-office systems to respond.

Option A (Request and Reply) is incorrect because that would require Salesforce to make a synchronous call and wait for the remote system to confirm the order was created before allowing the user to proceed. Option C (Remote Call-In) is the inverse of what is described; it would involve the remote system actively reaching into Salesforce to 'pull' the data, whereas here Salesforce is 'pushing' the notification via an event stream. By using Platform Events to facilitate this hand-off, Northern Trail Outfitters ensures a decoupled, scalable architecture where the remote system can process orders at its own pace while Salesforce remains responsive to sales users.


Contribute your Thoughts:

0/2000 characters
Karrie
7 days ago
I think the Fire and Forget pattern might be the right choice since the remote system just needs to subscribe to the event without waiting for a response.
upvoted 0 times
...
Martha
12 days ago
B) Fire and Forget. Anything else would be like trying to herd cats. Keep it simple, keep it efficient.
upvoted 0 times
...
Kaycee
17 days ago
B) Fire and Forget. Why overcomplicate things? This is the integration pattern that best fits the business use case.
upvoted 0 times
...
Loren
22 days ago
B) Fire and Forget, for sure. I'm not trying to play ping-pong with the remote system. Just send the event and let it do its thing.
upvoted 0 times
...
Chanel
28 days ago
B) Fire and Forget is the way to go. I don't want to be stuck waiting for the remote system to respond. Let's just get the order details out there and move on to the next task.
upvoted 0 times
...
Dallas
1 month ago
I'm going with B) Fire and Forget. Less back-and-forth, more getting the job done. Efficiency is key in the world of Salesforce integrations.
upvoted 0 times
...
Sherita
1 month ago
B) Fire and Forget seems like the way to go. Who wants to deal with the hassle of a request and reply pattern when you can just fire off the event and let the remote system handle it?
upvoted 0 times
...
Cyril
1 month ago
I think the correct answer is B) Fire and Forget. It makes sense to have the remote system subscribe to the platform event and handle the order creation asynchronously.
upvoted 0 times
...
Luisa
2 months ago
Okay, I think I've got this. The Remote system needs to be notified whenever a new order is created in Salesforce, so it can take over the order lifecycle. The Fire and Forget pattern sounds like the right approach to decouple these two systems and handle that event-driven integration.
upvoted 0 times
...
Shayne
2 months ago
The key here is that the order details are captured in Salesforce, but the actual order processing happens in the Remote system. So we need an integration pattern that can push that data from Salesforce to the Remote system asynchronously. I'd go with option B, Fire and Forget.
upvoted 0 times
...
Tasia
2 months ago
Hmm, this seems like a classic event-driven integration scenario. Since the Remote system needs to subscribe to a Salesforce platform event, I'm thinking the Fire and Forget pattern might be the way to go.
upvoted 0 times
...
Cora
2 months ago
I think B) Fire and Forget is the best option. It's simple and efficient.
upvoted 0 times
...
Malcolm
2 months ago
I'm a bit confused by the different systems involved here. Sounds like we need to integrate Salesforce with this Remote system, but I'm not sure which integration pattern would work best.
upvoted 0 times
...
Brandon
2 months ago
Sounds like a Fire and Forget situation to me!
upvoted 0 times
...

Save Cancel