New Year Sale 2026! 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 Certified MuleSoft Developer II (Mule-Dev-301) Exam - Topic 3 Question 26 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Developer II (Mule-Dev-301) exam
Question #: 26
Topic #: 3
[All Salesforce Certified MuleSoft Developer II (Mule-Dev-301) 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 Certified MuleSoft Developer II (Mule-Dev-301) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Paris
2 months ago
C is interesting, but can it really handle all those compensating actions effectively?
upvoted 0 times
...
Delisa
2 months ago
A sounds complicated, not sure if it's worth it.
upvoted 0 times
...
Josue
3 months ago
I think option C is the best choice for this scenario.
upvoted 0 times
...
Paulina
3 months ago
Wait, I thought D was the go-to for reliability patterns?
upvoted 0 times
...
Antonio
3 months ago
I disagree, B seems more straightforward for handling retries.
upvoted 0 times
...
Kristin
3 months ago
I was leaning towards option C as well, but I wonder if the VM queues could also work for reliability and rollback. It's a tough call!
upvoted 0 times
...
Deeanna
3 months ago
I feel like the Until Successful router could be useful, but I can't recall if it specifically handles rolling back requests.
upvoted 0 times
...
Onita
4 months ago
I'm not entirely sure, but I remember practicing a question about using a Try scope for error handling. Maybe the Parallel for Each scope is the way to go?
upvoted 0 times
...
Markus
4 months ago
I think the Scatter-Gather pattern might be the right choice since it allows for parallel processing and can handle compensating actions for failures.
upvoted 0 times
...
Antonio
4 months ago
The Scatter-Gather pattern with a Saga orchestrator sounds like the most comprehensive solution to me. It should allow for the parallel API calls and provide a way to handle the rollbacks if any requests fail. I think I'd go with that one.
upvoted 0 times
...
Roosevelt
4 months ago
I'm a bit confused by the VM queues and error handlers option. That doesn't seem like it would address the need for parallel processing and rollbacks. I'm leaning more towards the Scatter-Gather or Parallel for Each approaches.
upvoted 0 times
...
Lisha
4 months ago
I'm pretty confident the database transactional outbox and Until Successful router is the way to go here. That pattern seems well-suited for handling the parallel API calls and retrying failed requests.
upvoted 0 times
...
Alease
5 months ago
Hmm, the Parallel for Each scope with Try scopes seems like a simpler solution that could also work. I'd want to double-check the details, but that might be a good option to consider.
upvoted 0 times
...
Stefany
5 months ago
This looks like a tricky one. I'm not sure I fully understand the different patterns mentioned, but I think the Scatter-Gather approach with a Saga orchestrator sounds like it could work for handling the parallel API calls and rollbacks.
upvoted 0 times
...
Luisa
11 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
10 months ago
A database as a transactional outbox? That sounds like a solid strategy for handling failed requests.
upvoted 0 times
...
Kiley
10 months ago
C) Scatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes
upvoted 0 times
...
Asuncion
10 months ago
A) A database as a transactional outbox and an Until Successful router to retry any requests
upvoted 0 times
...
...
Brunilda
11 months ago
I'm leaning towards option B, it seems like a practical approach.
upvoted 0 times
...
Lashandra
11 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
11 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
11 months ago
User 2: Maybe option A would be a simpler choice for handling multiple HTTP APIs in parallel.
upvoted 0 times
...
Louvenia
11 months ago
User 1: I agree, option D does seem overly complex for just a few API calls.
upvoted 0 times
...
...
Nettie
11 months ago
I would go with option D, it seems like a safe bet.
upvoted 0 times
...
Tracey
11 months ago
I disagree, I believe option A is more reliable.
upvoted 0 times
...
Louvenia
11 months ago
Hmm, B sounds good too. Parallel processing with error handling could work well, especially for simpler use cases.
upvoted 0 times
...
Arlette
11 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
11 months ago
I prefer option B, using a Parallel for Each scope with Try scopes for each HTTP request.
upvoted 0 times
...
Mee
11 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
11 months ago
I agree, option C seems like the best choice for invoking multiple HTTP APIs in parallel.
upvoted 0 times
...
...
Pauline
12 months ago
I think option C is the best choice.
upvoted 0 times
...

Save Cancel