Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam MuleSoft Integration Architect I Topic 8 Question 11 Discussion

Actual exam question for Salesforce's MuleSoft Integration Architect I exam
Question #: 11
Topic #: 8
[All 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?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Apolonia
4 months 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
4 months 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
Gene
3 months ago
Definitely, Option B will help in handling the timeout errors efficiently.
upvoted 0 times
...
Nana
3 months ago
It's a good idea to have the retry mechanism in place within the Choice scope.
upvoted 0 times
...
Anthony
3 months ago
Yeah, using a Choice scope to invoke each vendor application separately makes sense.
upvoted 0 times
...
Lisandra
3 months ago
I agree, Option B seems like the best choice for this situation.
upvoted 0 times
...
...
Pete
4 months 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
3 months 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
3 months 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
4 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
3 months 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
3 months 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
4 months 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
4 months 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
5 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
Corinne
4 months ago
Yes, that way the API can handle the timeouts gracefully and ensure the requests are successful in the end.
upvoted 0 times
...
Irma
4 months ago
I agree, 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
...
Jeff
4 months ago
Option B looks like the most efficient way to handle the intermittent timeouts.
upvoted 0 times
...
...
Casie
5 months ago
I see your point, Deangelo. But I think option D with Round-Robin and Try-Catch is the way to go for better load balancing.
upvoted 0 times
...
Deangelo
5 months ago
I disagree, I believe option C is more performant as it uses Scatter-Gather to invoke vendors in parallel.
upvoted 0 times
...
Elinore
5 months ago
I think option A is the best choice because it invokes the vendors in series and retries timeout errors.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77