Salesforce Exam MuleSoft Integration Architect I Topic 2 Question 9 Discussion

Actual exam question for Salesforce's MuleSoft Integration Architect I exam

Question #: 9
Topic #: 2

[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 Graciela at Jul 02, 2024, 06:26 AM

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

Cyril

4 months ago

Option A seems a bit too sequential for my liking. I prefer the parallel invocations in the other options.

upvoted 0 times

Ming

3 months ago

Let's go with option C for the most efficient implementation.

upvoted 0 times

...

Devorah

4 months ago

I also prefer parallel invocations, option C seems like the way to go.

upvoted 0 times

...

Stephaine

4 months ago

I think option C with Scatter-Gather scope is the best choice for parallel invocations.

upvoted 0 times

...

Annamaria

4 months ago

I agree, parallel invocations would be more efficient.

upvoted 0 times

...

Sabine

5 months ago

Haha, this question is testing our knowledge of Mule scopes and error handling. I love it!

upvoted 0 times

Zack

3 months ago

C) Definitely! It's important to handle timeout errors properly to ensure the API functions smoothly.

upvoted 0 times

...

Dottie

3 months ago

B) That sounds like a good approach. It ensures that both vendor applications are invoked and retries are handled efficiently.

upvoted 0 times

...

Carole

3 months ago

D) Use 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.

upvoted 0 times

...

Amber

3 months ago

A) Use 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.

upvoted 0 times

...

Paris

4 months ago

C) Use 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.

upvoted 0 times

...

Ettie

4 months ago

A) Use 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.

upvoted 0 times

...

Regenia

5 months ago

I think option B could also work well, as it separates the vendors into different routes for better control.

upvoted 0 times

...

Lou

5 months ago

But with option C, there might be more network congestion. Option A seems more reliable.

upvoted 0 times

...

Long

5 months ago

I'm not sure about Option D. Using a Round-Robin scope and Try-Catch might work, but I'm not convinced it's the most performant solution compared to the other options.

upvoted 0 times

Ramonita

4 months ago

D: I see your point, but Option A does seem more straightforward. It's better to play it safe with the For-Each and Until-Successful approach.

upvoted 0 times

...

Gracie

4 months ago

C: Option A does seem like a reliable solution. It's always good to have a backup plan for those timeouts.

upvoted 0 times

...

Jennie

4 months ago

B: I agree, Option A sounds like a solid plan. It's important to handle those timeout errors properly.

upvoted 0 times

...

Stefan

5 months ago

A: Option A seems like the best choice. For-Each and Until-Successful should handle the timeouts efficiently.

upvoted 0 times

...

Precious

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

...

Marti

6 months ago

Option C looks good too. The Scatter-Gather scope will allow parallel invocations of the vendor applications, and the Until-Successful scope in each route will handle the retries.

upvoted 0 times

...

Lou

6 months ago

I think option A is the best choice because it invokes the vendors in series and retries timeouts.

upvoted 0 times

...

Willodean

6 months ago

I think Option B is the most performant way. Using a Choice scope with Until-Successful will ensure that each vendor application is invoked on a separate route and that requests with timeout errors are retried.

upvoted 0 times

Maryann

5 months ago

User 2

upvoted 0 times

...

Kate

5 months ago

User 1

upvoted 0 times

...