Salesforce Exam ARC-101 Topic 9 Question 13 Discussion

Actual exam question for Salesforce's ARC-101 exam

Question #: 13
Topic #: 9

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?

AOutbound Message for Salesforce to Legacy System direction and SOAP API using Enterprise WSDL for the communication back from legacy system to salesforce.

BPlatform Events for Salesforce to Legacy System direction and SOAP API using Partner WSDL for the communication back from legacy system to salesforce.

CPlatform Events for Salesforce to Legacy System direction and SOAP API using Enterprise WSDL for the communication back from legacy system to salesforce.

DOutbound Message for Salesforce to Legacy System direction and SOAP API using Partner WSDL for the communication back from legacy system to salesforce.

Show Suggested Answer

Suggested Answer: A, C, D

by Trinidad at Jan 06, 2023, 08:58 PM

Limited Time Offer

25%

Off

Get Premium ARC-101 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Markus

2 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

25 days 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

1 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

1 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

2 months ago

Ah, the joys of SOAP API integrations - where the 'S' stands for 'Seriously, who uses this anymore?'

upvoted 0 times

Ira

2 days 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

7 days 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

20 days 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

25 days 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

1 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

1 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

2 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

2 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

2 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

2 months ago

I think C is the correct option because of the 'Fire and Forget' pattern.

upvoted 0 times

...

Margurite

2 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

2 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

23 days 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

1 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

2 months ago

I agree, Platform Events are designed for asynchronous communication which aligns with the Fire and Forget pattern.

upvoted 0 times

...

Cora

2 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

2 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

2 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

2 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

3 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

...