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?

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 Yaeko at May 23, 2024, 11:17 PM

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

Merri

11 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

11 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

11 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

11 months ago

I think using a For-Each scope inside an Until-Successful scope might be more reliable.

upvoted 0 times

...

Heike

11 months ago

Using a Scatter-Gather scope with an Until-Successful scope in each route might be a good approach.

upvoted 0 times

...

Domingo

11 months ago

Option D with the Round-Robin scope and Try-Catch scope could be a good choice.

upvoted 0 times

...

Soledad

11 months ago

I think using a For-Each scope inside an Until-Successful scope could also work well.

upvoted 0 times

...

Aleta

11 months ago

Option D with Round-Robin scope and Try-Catch scope sounds like a good choice.

upvoted 0 times

...

Paris

12 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

11 months ago

I agree, that way we can ensure that the requests are retried if they encounter any issues.

upvoted 0 times

...

Selma

11 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

11 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

12 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

10 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

11 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

11 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

11 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

12 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

11 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

11 months ago

I agree, option B seems like the most efficient way to handle the network timeouts.

upvoted 0 times

...