Salesforce Exam MuleSoft-Integration-Architect-I Topic 8 Question 11 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Integration Architect I exam

Question #: 11
Topic #: 8

[All Salesforce Certified MuleSoft Integration Architect I Questions]

A retail company is implementing a MuleSoft API to get inventory details from two vendors by Invoking each vendor's online applications. Due to network issues, the invocations to the vendor applications are timing out intermittently, but the requests are successful after re-invoking each

What is the most performant way of implementing the API to invoke each vendor application and to retry invocations that generate timeout errors?

AUse a For-Each scope to invoke the two vendor applications in series, one after the other.
Place the For-Each scope inside an Until-Successful scope to retry requests that raise timeout errors.

BUse a Choice scope to Invoke each vendor application on a separate route.
Place the Choice scope inside an Until-Successful scope to retry requests that raise
timeout errors.

CUse a Scatter-Gather scope to invoke each vendor application on a separate route.
Use an Until-Successful scope in each route to retry requests that raise timeout errors.

DUse a Round-Robin scope to invoke each vendor application on a separate route.
Use a Try-Catch scope in each route to retry requests that raise timeout errors.

Show Suggested Answer

Suggested Answer: A

by Leana at Jul 15, 2024, 06:37 AM

Limited Time Offer

25%

Off

Get Premium MuleSoft-Integration-Architect-I Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Apolonia

21 days ago

I'd go with Option B as well. It's a simple and straightforward solution that addresses the specific problem at hand. No need to overcomplicate things.

upvoted 0 times

...

Alpha

23 days ago

Haha, I bet the vendor apps are running on a hamster-powered server. That's why the timeouts are happening! Option B is definitely the way to go here.

upvoted 0 times

Nana

2 days ago

It's a good idea to have the retry mechanism in place within the Choice scope.

upvoted 0 times

...

Anthony

6 days ago

Yeah, using a Choice scope to invoke each vendor application separately makes sense.

upvoted 0 times

...

Lisandra

11 days ago

I agree, Option B seems like the best choice for this situation.

upvoted 0 times

...

Pete

26 days ago

Hmm, I'm not sure. Option C with the Scatter-Gather scope also looks like it could work well. But I guess the Until-Successful scope in each route might be overkill if we're just dealing with timeouts.

upvoted 0 times

Arminda

1 days ago

I agree, Option A sounds like the best approach. It keeps it simple and should help with retrying the requests that timeout.

upvoted 0 times

...

Kallie

2 days ago

Option A seems like the most efficient way to handle the timeouts. Using a For-Each scope and an Until-Successful scope should do the trick.

upvoted 0 times

...

Maryann

1 months ago

I agree, Option B seems like the right choice here. Separating the vendor invocations and retrying the failed requests is a smart way to ensure the API is robust and performant.

upvoted 0 times

In

7 days ago

I agree, Option B is the way to go. Separating the invocations and handling timeouts efficiently is key for a reliable API.

upvoted 0 times

...

Murray

11 days ago

Option C could be a good approach as well. Using Scatter-Gather to invoke vendors in parallel and retrying failed requests could improve performance.

upvoted 0 times

...

Latricia

17 days ago

I think Option A could work too. Invoking the vendors in series and retrying failed requests might be more straightforward.

upvoted 0 times

...

Dorothy

23 days ago

Option B seems like the right choice. Separating the vendor invocations and retrying the failed requests is a smart way to ensure the API is robust and performant.

upvoted 0 times

...

Dino

2 months ago

Option B looks like the most efficient way to handle the intermittent timeouts. Using a Choice scope to invoke the vendors separately and an Until-Successful scope to retry the requests seems like the best approach.

upvoted 0 times