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 10 Question 1 Discussion

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

Merri
6 months ago
Haha, I bet the vendors are using the same internet provider as my grandma. Her Wi-Fi cuts out every time she tries to stream her cat videos!
upvoted 0 times
...
Sylvie
6 months ago
Hmm, I'm not convinced. Option D with the Round-Robin scope and Try-Catch scope in each route might be a good alternative. It could help balance the load between the two vendor applications and still handle the timeout errors.
upvoted 0 times
Cheryl
5 months ago
I agree, using a Scatter-Gather scope with an Until-Successful scope in each route could help with handling timeout errors.
upvoted 0 times
...
Dottie
5 months ago
I think using a For-Each scope inside an Until-Successful scope might be more reliable.
upvoted 0 times
...
Heike
5 months ago
Using a Scatter-Gather scope with an Until-Successful scope in each route might be a good approach.
upvoted 0 times
...
Domingo
5 months ago
Option D with the Round-Robin scope and Try-Catch scope could be a good choice.
upvoted 0 times
...
Soledad
6 months ago
I think using a For-Each scope inside an Until-Successful scope could also work well.
upvoted 0 times
...
Aleta
6 months ago
Option D with Round-Robin scope and Try-Catch scope sounds like a good choice.
upvoted 0 times
...
...
Paris
6 months ago
I'm not sure about that. Option C with the Scatter-Gather scope might be a better choice. That way, we can invoke both vendor applications in parallel and use an Until-Successful scope on each route to handle the timeout errors.
upvoted 0 times
Mose
5 months ago
I agree, that way we can ensure that the requests are retried if they encounter any issues.
upvoted 0 times
...
Selma
6 months ago
Yes, and using an Until-Successful scope on each route will help us handle any timeout errors that may occur.
upvoted 0 times
...
Keena
6 months ago
Option C with the Scatter-Gather scope sounds like a good idea. It allows us to invoke both vendor applications in parallel.
upvoted 0 times
...
...
Samira
7 months ago
I agree with Carmen. Option B seems like the most efficient way to handle this situation. The Choice scope will allow us to invoke each vendor application simultaneously, and the Until-Successful scope will ensure that we retry any requests that time out.
upvoted 0 times
Dawne
5 months ago
I agree, using a Choice scope for separate routes and an Until-Successful scope for retries seems like the best approach.
upvoted 0 times
...
Teddy
5 months ago
I think Option B is the way to go. It allows us to invoke each vendor application separately and retry any timeouts.
upvoted 0 times
...
Misty
6 months ago
I agree, using a Choice scope for simultaneous invocations and an Until-Successful scope for retries seems like the way to go.
upvoted 0 times
...
Shonda
6 months ago
I think Option B is the best choice. It allows us to invoke both vendors separately and retry any timeouts.
upvoted 0 times
...
...
Carmen
7 months ago
I think option B is the most performant. Using a Choice scope to invoke each vendor application on a separate route, and then placing the Choice scope inside an Until-Successful scope to retry requests that raise timeout errors, seems like the best approach to handle the intermittent network issues.
upvoted 0 times
Sarah
6 months ago
I think option B is the way to go as well. It provides a good balance between invoking the vendors and handling timeout errors.
upvoted 0 times
...
Ira
6 months ago
I agree, option B seems like the most efficient way to handle the network timeouts.
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