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?

AUse an HTTP Connector to invoke the API and wait for a response

BUse a Scheduler to check for a response every minute

CUse an HTTP Connector inside Async scope to invoice the API and wait for a response

DExpose an HTTP callback API in Mule and register it with the external system

Show Suggested 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

Earlean

10 days ago

I'm not sure, but option D seems interesting as it involves setting up an HTTP callback API in Mule.

upvoted 0 times

...

Selma

18 days 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

20 days 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

21 days 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

23 days 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

Peter

1 days ago

User 3: I agree. It's important to handle long-running processes asynchronously in Mule applications.

upvoted 0 times

...

Terina

3 days ago

It's definitely a good approach to ensure the Mule application remains responsive during the external API call.

upvoted 0 times

...

Daren

4 days ago

User 2: That's a good point. It will prevent Mule from being blocked while waiting for the response.

upvoted 0 times

...

Adolph

4 days ago

Using an HTTP Connector inside Async scope is a good way to handle this situation.

upvoted 0 times

...

Ruthann

7 days ago

User 1: Option C looks promising, using an Async scope to handle the long-running external API call.

upvoted 0 times

...

Mendy

7 days ago

I agree, it's important to handle long-running processes asynchronously to avoid blocking.

upvoted 0 times

...

Ilene

18 days 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

26 days ago

I think option A is the best choice because we need to wait for the response from the external API.

upvoted 0 times

...