When is the flow processing strategy set to queued asynchronous?

• A. When the message source is not expecting a response
• B. When the destination is a VM
• C. When there is a transaction only
• D. When the endpoints are synchronous

Answer: (A)

Queued asynchronous processing is used when the flow is allowed to handle the message in the background, decoupling the caller from the processing. If the message source does not expect or require a reply, you can enqueue the event and return immediately to the sender. This setup lets Mule process the work asynchronously, improving throughput and avoiding blocking the source while the flow does its work downstream.

That’s why the option describing the message source not expecting a response is the best fit. If the source does expect a response—such as an HTTP request-reply—the flow should typically run synchronously or with a design that preserves the necessary request/response behavior. The destination type, transactional context, or whether endpoints are synchronous do not by themselves determine when to use queued asynchronous in the same definitive way.