MENU
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?
Suggested Answer: A
Get Premium Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
40 comments · newest first
LU
Lucina
11 months ago
Round-Robin? Sounds like a risky choice with timeouts!
LE
Lennie
11 months ago
B could work too, but C is more efficient.
CO
Coleen
12 months ago
Surprised that no one mentioned load balancing!
HE
Herminia
12 months ago
I disagree, A might be simpler to implement.
JA
Jaime
1 year ago
C seems like the best option for performance.
MI
Micaela
1 year ago
I vaguely remember that using a Try-Catch scope might not be the most efficient for this scenario, but I can't quite remember why. It feels like there might be a better way to handle timeouts.
FR
Freida
1 year ago
I’m leaning towards option C because it seems to allow for better handling of multiple invocations, but I’m not confident about the specifics of how retries would work in that setup.
ME
Melissa
1 year ago
I think the Until-Successful scope is crucial for retries, but I can't recall if it works well with the For-Each scope. I feel like I've seen a similar question before.
LE
Lettie
1 year ago
I remember that using a Scatter-Gather scope can help with performance since it allows parallel processing, but I'm not entirely sure if it's the best choice for handling timeouts.
CR
Crista
1 year ago
The Round-Robin scope with a Try-Catch scope in each route also sounds like a good approach. That way, we can distribute the load across the vendor applications and handle the timeout errors without impacting the overall performance.
EZ
Ezekiel
1 year ago
I'm leaning towards the Scatter-Gather scope option. That way, we can invoke the vendor applications in parallel and use an Until-Successful scope in each route to handle the timeout errors. This should provide the best performance, as long as we configure the retry settings correctly.
MA
Mabelle
1 year ago
The key here is to minimize the impact of the intermittent network issues. Using an Until-Successful scope to retry the requests seems like a solid strategy, but I'm not sure if a For-Each or a Choice scope would be better for invoking the vendor applications.
IZ
Izetta
1 year ago
Hmm, I'm a bit confused on the difference between a Choice scope and a Scatter-Gather scope. I'll need to review those concepts before deciding which one would be the most performant approach.
TH
Theodora
1 year ago
I think the most performant way would be to use a Choice scope to invoke each vendor application on a separate route, and then place the Choice scope inside an Until-Successful scope to retry requests that raise timeout errors.
NO
Noah
1 year ago
Hmm, I'm not sure an external catalog is the best solution here. We might need to consider other options that don't require as much integration with the vendor's systems. I'll have to think this through a bit more.
SE
Selma
1 year ago
I'm not entirely sure, but I feel like a defect is more about the recognition of failure. That might tie to II-d?
MY
My
1 year ago
Option A with a Shared VPC Host Project sounds interesting, but I'm not sure if that's the most efficient approach here. I'll need to research that a bit more to understand if it's the best fit.
EL
Elouise
1 year ago
I'm a bit confused on this one. I know there are a bunch of IEEE 802 standards, but I'm not sure which one covers wireless access specifically. I'll have to think it through carefully.
JE
Jennie
1 year ago
Hmm, I'm not too familiar with the history of vi, but EMACS seems like a reasonable guess. I'll have to think about this one.
YV
Yvonne
1 year ago
This question covers a lot of different hedging strategies, so I'll need to carefully read through the details to make sure I understand the concepts before attempting to answer.
ME
Merri
2 years 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!
SY
Sylvie
2 years 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.
CH
Cheryl
2 years ago
I agree, using a Scatter-Gather scope with an Until-Successful scope in each route could help with handling timeout errors.
DO
Dottie
2 years ago
I think using a For-Each scope inside an Until-Successful scope might be more reliable.
HE
Heike
2 years ago
Using a Scatter-Gather scope with an Until-Successful scope in each route might be a good approach.
DO
Domingo
2 years ago
Option D with the Round-Robin scope and Try-Catch scope could be a good choice.
SO
Soledad
2 years ago
I think using a For-Each scope inside an Until-Successful scope could also work well.
AL
Aleta
2 years ago
Option D with Round-Robin scope and Try-Catch scope sounds like a good choice.
PA
Paris
2 years 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.
MO
Mose
2 years ago
I agree, that way we can ensure that the requests are retried if they encounter any issues.
SE
Selma
2 years ago
Yes, and using an Until-Successful scope on each route will help us handle any timeout errors that may occur.
KE
Keena
2 years ago
Option C with the Scatter-Gather scope sounds like a good idea. It allows us to invoke both vendor applications in parallel.
SA
Samira
2 years 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.
DA
Dawne
2 years ago
I agree, using a Choice scope for separate routes and an Until-Successful scope for retries seems like the best approach.
TE
Teddy
2 years ago
I think Option B is the way to go. It allows us to invoke each vendor application separately and retry any timeouts.
MI
Misty
2 years ago
I agree, using a Choice scope for simultaneous invocations and an Until-Successful scope for retries seems like the way to go.
SH
Shonda
2 years ago
I think Option B is the best choice. It allows us to invoke both vendors separately and retry any timeouts.
CA
Carmen
2 years 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.
SA
Sarah
2 years 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.
IR
Ira
2 years ago
I agree, option B seems like the most efficient way to handle the network timeouts.