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 ARC-101 Exam - Topic 9 Question 13 Discussion

Actual exam question for Salesforce's ARC-101 exam
Question #: 13
Topic #: 9
[All ARC-101 Questions]

A company needs to integrate a legacy on premise application that can only support SOAP API. After the Integration Architect has evaluated the requirements and volume, they determined that the Fire and Forget integration pattern will be most appropriate for sending data from Salesforce to the external application and getting response back in a strongly typed format.

Which integration capabilities should be used to integrate the two systems?

Show Suggested Answer Hide Answer
Suggested Answer: A, C, D

Contribute your Thoughts:

0/2000 characters
Cordelia
4 months ago
I disagree, B seems more flexible with Platform Events.
upvoted 0 times
...
Dean
4 months ago
Wait, can SOAP really handle that volume?
upvoted 0 times
...
Pedro
4 months ago
Definitely A! Strongly typed response is key here.
upvoted 0 times
...
Kathryn
4 months ago
I think Partner WSDL is the way to go for this.
upvoted 0 times
...
Loreta
4 months ago
Outbound Message is great for Fire and Forget!
upvoted 0 times
...
Vincent
5 months ago
I'm a bit confused about the Fire and Forget pattern. I thought it meant we could use either Outbound Messages or Platform Events, but now I'm not sure which one is better for this integration.
upvoted 0 times
...
Nicolette
5 months ago
I practiced a similar question where we had to choose between Enterprise and Partner WSDL, and I think Enterprise is usually more suitable for strongly typed responses.
upvoted 0 times
...
Francesco
5 months ago
I think Outbound Messages might be the right choice since they are designed for sending data to external systems, but I need to double-check the WSDL options.
upvoted 0 times
...
Latricia
5 months ago
I remember studying the differences between Outbound Messages and Platform Events, but I'm not entirely sure which one fits best for this scenario.
upvoted 0 times
...
Caitlin
5 months ago
Round Robin could be a good option too, as it evenly distributes the traffic across all the nodes without considering their current load.
upvoted 0 times
...
Shanice
5 months ago
I'm a bit confused by the options here. I'll need to review my notes on product classification to make sure I understand the distinctions between them.
upvoted 0 times
...
Markus
10 months ago
Hey, at least it's not a REST API integration, right? That would be way too modern for this legacy system!
upvoted 0 times
Armando
9 months ago
C) Platform Events for Salesforce to Legacy System direction and SOAP API using Enterprise WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...
Samira
9 months ago
B) Platform Events for Salesforce to Legacy System direction and SOAP API using Partner WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...
Erinn
10 months ago
A) Outbound Message for Salesforce to Legacy System direction and SOAP API using Enterprise WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...
...
Hannah
10 months ago
Ah, the joys of SOAP API integrations - where the 'S' stands for 'Seriously, who uses this anymore?'
upvoted 0 times
Joaquin
8 months ago
D) Outbound Message for Salesforce to Legacy System direction and SOAP API using Partner WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...
Ira
8 months ago
C) Platform Events for Salesforce to Legacy System direction and SOAP API using Enterprise WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...
Peggie
8 months ago
B) Platform Events for Salesforce to Legacy System direction and SOAP API using Partner WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...
Edda
9 months ago
A) Outbound Message for Salesforce to Legacy System direction and SOAP API using Enterprise WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...
Mary
9 months ago
D) Outbound Message for Salesforce to Legacy System direction and SOAP API using Partner WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...
Vincenza
9 months ago
C) Platform Events for Salesforce to Legacy System direction and SOAP API using Enterprise WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...
Gregoria
9 months ago
B) Platform Events for Salesforce to Legacy System direction and SOAP API using Partner WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...
Vallie
10 months ago
A) Outbound Message for Salesforce to Legacy System direction and SOAP API using Enterprise WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...
...
Marguerita
10 months ago
Option A looks good at first glance, but the question mentions 'Fire and Forget' pattern, so that rules out Outbound Messages. Gotta go with C.
upvoted 0 times
Flo
10 months ago
Yeah, I agree. Platform Events for Salesforce to Legacy System direction and SOAP API using Enterprise WSDL makes sense.
upvoted 0 times
...
France
10 months ago
I think C is the correct option because of the 'Fire and Forget' pattern.
upvoted 0 times
...
...
Margurite
11 months ago
Hmm, this one's a little tricky. Gotta love those SOAP API integration questions - they really keep you on your toes!
upvoted 0 times
...
Gladys
11 months ago
I was about to pick option B, but then I realized the question specifically mentions 'Fire and Forget' pattern, which is more aligned with Platform Events than Outbound Messages.
upvoted 0 times
Evelynn
9 months ago
Yes, that combination will ensure the data is sent from Salesforce to the external application and the response is received in a strongly typed format.
upvoted 0 times
...
Trina
10 months ago
So, we should use Platform Events for Salesforce to Legacy System direction and SOAP API using Enterprise WSDL for the communication back.
upvoted 0 times
...
Mitsue
10 months ago
I agree, Platform Events are designed for asynchronous communication which aligns with the Fire and Forget pattern.
upvoted 0 times
...
Cora
10 months ago
I think option C is the correct choice because Platform Events are more suitable for Fire and Forget pattern.
upvoted 0 times
...
...
Willetta
11 months ago
I see your point, but I still think A is the best choice because it provides a more direct and efficient integration pattern.
upvoted 0 times
...
Brendan
11 months ago
Option C seems like the obvious choice here. Platform Events for the outbound direction and Enterprise WSDL for the strongly typed response back - that's exactly what the question is asking for.
upvoted 0 times
...
Ernest
11 months ago
I disagree, I believe the correct answer is B) Platform Events for Salesforce to Legacy System direction and SOAP API using Partner WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...
Willetta
11 months ago
I think the answer is A) Outbound Message for Salesforce to Legacy System direction and SOAP API using Enterprise WSDL for the communication back from legacy system to salesforce.
upvoted 0 times
...

Save Cancel