Salesforce Exam Salesforce MuleSoft Developer II Topic 4 Question 4 Discussion

Actual exam question for Salesforce's Salesforce MuleSoft Developer II exam

Question #: 4
Topic #: 4

[All Salesforce MuleSoft Developer II Questions]

A Mule implementation uses a HTTP Request within an Unit Successful scope to connect to an API.

How should a permanent error response like HTTP:UNAUTHORIZED be handle inside Until Successful to reduce latency?

AConfigure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.

BIn Until Successful configuration, set the retry count to 1 for error type HTTP: UNAUTHORIZED.

CPut the HTTP Request inside a try scope in Unit Successful.
In the error handler, use On Error Continue to catch permanent errors like HTTP UNAUTHORIZED.

DPut the HTTP Request inside a try scope in Unit Successful.
In the error handler, use On Error Propagate to catch permanent errors like HTTP UNAUTHORIZED.

Show Suggested Answer

Suggested Answer: C

To handle a permanent error response like HTTP:UNAUTHORIZED inside Until Successful, the developer should put the HTTP Request inside a try scope in Unit Successful, and use On Error Continue to catch permanent errors like HTTP UNAUTHORIZED in the error handler. This way, the developer can avoid retrying requests that will always fail due to a permanent error, and reduce latency. On Error Continue allows the flow to continue processing after handling the error. Reference: https://docs.mulesoft.com/mule-runtime/4.3/until-successful-scope https://docs.mulesoft.com/mule-runtime/4.3/on-error-continue-concept

by Truman at May 20, 2024, 04:06 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

Xuan

7 months ago

I'm going to have to go with the Mule-tiple choice option C. Get it? Mule-tiple? Eh, tough crowd.

upvoted 0 times

...

Celestine

7 months ago

Option B is like putting a band-aid on a bullet wound. Why not just fix the underlying issue and get the right authorization?

upvoted 0 times

...

Herminia

8 months ago

On Error Continue? Sounds like a dangerous option to me. Wouldn't that just keep retrying the request indefinitely?

upvoted 0 times

Shalon

7 months ago

C: A) Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.

upvoted 0 times

...

Francoise

7 months ago

B: D) Put the HTTP Request inside a try scope in Unit Successful. In the error handler, use On Error Propagate to catch permanent errors like HTTP UNAUTHORIZED.

upvoted 0 times

...

Arlen

7 months ago

A: A) Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.

upvoted 0 times

...

Chauncey

7 months ago

C) Put the HTTP Request inside a try scope in Unit Successful. In the error handler, use On Error Continue to catch permanent errors like HTTP UNAUTHORIZED.

upvoted 0 times

...

Julio

7 months ago

A) Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.

upvoted 0 times

...

Luther

7 months ago

C) Put the HTTP Request inside a try scope in Unit Successful. In the error handler, use On Error Continue to catch permanent errors like HTTP UNAUTHORIZED.

upvoted 0 times

...

Carisa

7 months ago

A) Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.

upvoted 0 times

...

Melissia

8 months ago

I like how Option D propagates the error instead of just continuing. That way, you can handle it further up the flow if needed.

upvoted 0 times

...

Chantell

8 months ago

Hmm, I'm not sure setting the retry count to 1 for just the HTTP:UNAUTHORIZED error is the best solution. Wouldn't it be better to handle all permanent errors the same way?

upvoted 0 times

...

Ellsworth

8 months ago

Option C looks like the best way to handle permanent errors in Until Successful. Catching them with On Error Continue and retrying is a smart approach.

upvoted 0 times

Laurene

7 months ago

Absolutely, having a solid error handling mechanism is crucial for maintaining the reliability of the Mule implementation.

upvoted 0 times

...

Tyra

7 months ago

I see your point. It's important to choose the right error handling strategy based on the specific requirements of the API integration.

upvoted 0 times

...

Jade

7 months ago

That's true, but using On Error Continue provides more flexibility in handling different types of errors.

upvoted 0 times

...

Nikita

7 months ago

I think setting the retry count to 1 for HTTP: UNAUTHORIZED errors in Until Successful could also be a good approach.

upvoted 0 times

...

Keith

7 months ago

It definitely helps in reducing latency and ensuring the API connection is successful in the long run.

upvoted 0 times

...

Angella

8 months ago

I agree, using On Error Continue to catch and handle HTTP: UNAUTHORIZED errors efficiently is key.

upvoted 0 times

...

Audry

8 months ago

Yes, I agree. It's important to handle those errors properly to reduce latency.

upvoted 0 times

...

Tammara

8 months ago

Option C looks like the best way to handle permanent errors in Until Successful. Catching them with On Error Continue and retrying is a smart approach.

upvoted 0 times

...

Leonard

8 months ago

Option C looks like the best way to handle permanent errors in Until Successful. Catching them with On Error Continue and retrying is a smart approach.

upvoted 0 times

...