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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Exam Salesforce MuleSoft Developer II Topic 3 Question 26 Discussion

Actual exam question for Salesforce's Salesforce MuleSoft Developer II exam
Question #: 26
Topic #: 3
[All Salesforce MuleSoft Developer II Questions]

Which pattern should be used to invoke multiple HTTP APIs in parallel and roll back failed requests in sequence?

Show Suggested Answer Hide Answer
Suggested Answer: C

To invoke multiple HTTP APIs in parallel and roll back failed requests in sequence, the developer should use a Scatter-Gather router as a central Saga orchestrator for all API requests with compensating actions for failing routes. A Scatter-Gather router executes multiple routes concurrently and aggregates the results. A Saga orchestrator coordinates a series of actions across different services and handles failures by executing compensating actions. Therefore, using a Scatter-Gather router as a Saga orchestrator allows invoking multiple HTTP APIs in parallel and rolling back any failed requests in sequence. Reference: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept https://docs.mulesoft.com/mule-runtime/4.3/saga


by Jeffrey at Mar 06, 2025, 09:54 PM

Limited Time Offer

25%

Off

Get Premium Salesforce MuleSoft Developer II Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Luisa
3 months ago
A database as a transactional outbox? Now that's an interesting approach. I'd have to read up more on that, but it could be a clever way to handle the rollbacks.
upvoted 0 times
Kimberlie
1 months ago
A database as a transactional outbox? That sounds like a solid strategy for handling failed requests.
upvoted 0 times
...
Kiley
1 months ago
C) Scatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes
upvoted 0 times
...
Asuncion
2 months ago
A) A database as a transactional outbox and an Until Successful router to retry any requests
upvoted 0 times
...
...
Brunilda
3 months ago
I'm leaning towards option B, it seems like a practical approach.
upvoted 0 times
...
Lashandra
3 months ago
Haha, option D with VM queues and error handlers? Sounds like a whole lot of complexity just for a few API calls. I'll pass on that one.
upvoted 0 times
Miriam
2 months ago
User 3: Yeah, using a database as a transactional outbox and retrying failed requests with an Until Successful router sounds more straightforward.
upvoted 0 times
...
Carlene
2 months ago
User 2: Maybe option A would be a simpler choice for handling multiple HTTP APIs in parallel.
upvoted 0 times
...
Louvenia
2 months ago
User 1: I agree, option D does seem overly complex for just a few API calls.
upvoted 0 times
...
...
Nettie
3 months ago
I would go with option D, it seems like a safe bet.
upvoted 0 times
...
Tracey
3 months ago
I disagree, I believe option A is more reliable.
upvoted 0 times
...
Louvenia
3 months ago
Hmm, B sounds good too. Parallel processing with error handling could work well, especially for simpler use cases.
upvoted 0 times
...
Arlette
3 months ago
I think option C is the way to go. Scatter-Gather with a Saga orchestrator sounds like the most robust and scalable solution to me.
upvoted 0 times
Hermila
2 months ago
I prefer option B, using a Parallel for Each scope with Try scopes for each HTTP request.
upvoted 0 times
...
Mee
3 months ago
I think option A could also work well, using a database as a transactional outbox for retrying failed requests.
upvoted 0 times
...
Reiko
3 months ago
I agree, option C seems like the best choice for invoking multiple HTTP APIs in parallel.
upvoted 0 times
...
...
Pauline
3 months ago
I think option C is the best choice.
upvoted 0 times
...

Save Cancel