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 4 Question 21 Discussion

Actual exam question for Salesforce's Salesforce MuleSoft Developer II exam
Question #: 21
Topic #: 4
[All Salesforce MuleSoft Developer II 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
Suggested Answer: D

To get response data from the external API after it completes processing, the developer should expose an HTTP callback API in Mule and register it with the external system. This way, the external API can invoke the callback API with the response data when it is ready, instead of making the Mule application wait for a long time or poll for a response repeatedly. Reference: https://docs.mulesoft.com/mule-runtime/4.3/http-listener-ref#callback


by Goldie at Nov 17, 2024, 04:50 AM

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
Myong
1 months ago
Haha, imagine setting up a Scheduler to check the external API every minute for 24 hours. That's going to be one busy Mule app!
upvoted 0 times
Elouise
25 days ago
C) Use an HTTP Connector inside Async scope to invoice the API and wait for a response
upvoted 0 times
...
Sabina
26 days ago
A) Use an HTTP Connector to invoke the API and wait for a response
upvoted 0 times
...
...
Lynelle
1 months ago
I'm a little worried about Option A. Waiting for a response from an API that could take 24 hours seems like it could cause issues. Better to use an asynchronous approach.
upvoted 0 times
Jamie
19 days ago
User 4: Yeah, I think using an HTTP Connector inside Async scope would be the safest bet for handling the response from the external API.
upvoted 0 times
...
Tracey
21 days ago
User 3: Option C sounds like the way to go. It's important to handle long processing times in a more efficient manner.
upvoted 0 times
...
Telma
26 days ago
User 2: I agree, an asynchronous approach would be more efficient in this case. Option A could potentially cause issues if we have to wait for 24 hours.
upvoted 0 times
...
Shakira
1 months ago
User 1: I think Option C would be the best choice. Using an Async scope would allow us to wait for the response without blocking the application.
upvoted 0 times
...
...
Earlean
2 months ago
I'm not sure, but option D seems interesting as it involves setting up an HTTP callback API in Mule.
upvoted 1 times
...
Selma
2 months ago
I disagree, I believe option C is better as it allows us to invoke the API asynchronously and wait for the response.
upvoted 0 times
...
Julio
2 months ago
Option D is interesting, but it would require coordinating with the external system to set up the callback. Might be more work than just using an Async scope.
upvoted 0 times
...
An
2 months ago
I'm not sure about using a Scheduler to check for a response every minute. That seems like it could get messy and inefficient. Exposing a callback API might be a cleaner solution.
upvoted 0 times
...
Ressie
2 months ago
Option C looks promising, using an Async scope to handle the long-running external API call. That way, Mule won't be blocked while waiting for the response.
upvoted 0 times
Art
1 months ago
User 4: Async scope definitely seems like the way to go for this scenario.
upvoted 0 times
...
Peter
2 months ago
User 3: I agree. It's important to handle long-running processes asynchronously in Mule applications.
upvoted 0 times
...
Terina
2 months ago
It's definitely a good approach to ensure the Mule application remains responsive during the external API call.
upvoted 0 times
...
Daren
2 months ago
User 2: That's a good point. It will prevent Mule from being blocked while waiting for the response.
upvoted 0 times
...
Adolph
2 months ago
Using an HTTP Connector inside Async scope is a good way to handle this situation.
upvoted 0 times
...
Ruthann
2 months ago
User 1: Option C looks promising, using an Async scope to handle the long-running external API call.
upvoted 0 times
...
Mendy
2 months ago
I agree, it's important to handle long-running processes asynchronously to avoid blocking.
upvoted 0 times
...
Ilene
2 months ago
Option C looks promising, using an Async scope to handle the long-running external API call. That way, Mule won't be blocked while waiting for the response.
upvoted 0 times
...
...
Florinda
2 months ago
I think option A is the best choice because we need to wait for the response from the external API.
upvoted 0 times
...

Save Cancel