Deal of The Day! 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 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?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Apolonia
7 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
9 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
...
Pete
12 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
...
Maryann
25 days 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
Latricia
3 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
9 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
1 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 days ago
Yes, that way the API can handle the timeouts gracefully and ensure the requests are successful in the end.
upvoted 0 times
...
Irma
13 days 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
20 days ago
Option B looks like the most efficient way to handle the intermittent timeouts.
upvoted 0 times
...
...
Casie
1 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
2 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
2 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