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

Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Exam - Topic 4 Question 37 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Developer II (Mule-Dev-301) exam
Question #: 37
Topic #: 4
[All Salesforce Certified MuleSoft Developer II (Mule-Dev-301) Questions]

A Mule application need to invoice an API hosted by an external system to initiate a process. The external API takes anywhere between one minute and 24 hours to compute its process.

Which implementation should be used to get response data from the external API after it completes processing?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Miriam
3 days ago
B is like checking the fridge every minute to see if the food is ready. Seems a bit overkill.
upvoted 0 times
...
Carlene
8 days ago
Option D is the way to go. Who wants to wait 24 hours for a response? Not me!
upvoted 0 times
...
Dean
13 days ago
I'd go with C. Async scope should be able to handle the long processing time.
upvoted 0 times
...
Tesha
18 days ago
B is a bit of a hack, but it might work if the external system is reliable.
upvoted 0 times
...
Ronald
24 days ago
D seems like the best option to me. Handling the callback from the external system is the way to go.
upvoted 0 times
...
Bev
29 days ago
Option C looks good, but I'm not sure if it can handle the 24-hour processing time.
upvoted 0 times
...
Delsie
1 month ago
I feel like option C could work, but using Async might complicate things if we need to handle the response properly.
upvoted 0 times
...
Lashaunda
1 month ago
I'm a bit confused about option B; checking every minute seems inefficient, but maybe it's a valid approach?
upvoted 0 times
...
Davida
1 month ago
I remember practicing a question similar to this, and I think option D makes sense because it allows the external system to notify us when it's done.
upvoted 0 times
...
Buddy
2 months ago
I think option A might be too risky since the response time can be so long, but I'm not entirely sure.
upvoted 0 times
...
Glendora
2 months ago
I'm leaning towards option B - a scheduled check for the response every minute. That seems like a straightforward way to handle the uncertainty around the processing time.
upvoted 0 times
...
Anna
2 months ago
Option D seems interesting, but I'm not sure how that would work in practice. I'd need to understand more about how to expose and register that HTTP callback API.
upvoted 0 times
...
Val
2 months ago
Wait, can the external API really take up to 24 hours? That’s wild!
upvoted 0 times
...
Dudley
2 months ago
A would just time out, right? Not a good choice.
upvoted 0 times
...
Ben
3 months ago
I agree, D is definitely the way to go!
upvoted 0 times
...
Odelia
3 months ago
D seems like the best option for handling long wait times.
upvoted 0 times
...
Cyril
3 months ago
I think option C might be the way to go here. Using an async scope to invoke the API and wait for the response seems like it could handle the variable processing time well.
upvoted 0 times
...
France
3 months ago
Hmm, I'm a bit confused by the time range for the external API processing. That's going to be an important factor in deciding the best approach.
upvoted 0 times
...
Brynn
3 months ago
This looks like a tricky one. I'll need to think carefully about the different options and their implications.
upvoted 0 times
...

Save Cancel