What is the default processing strategy of a one-way flow?

What is the default processing strategy of a one-way flow?

• A. Synchronous
• B. Queued-asynchronous
• C. Asynchronous with batching
• D. Parallel processing

Answer: (B)

One-way flows don’t return a response to the sender, so Mule processes them asynchronously by default to avoid blocking the caller. This default uses a queue, so the message is accepted quickly and the actual work happens in the background, enabling decoupling between producer and consumer. The queued-asynchronous pattern also supports reliability and back-pressure—messages can be retried or persisted in the queue if needed. Synchronous would wait for a response, which isn’t appropriate for a one-way flow. Processing in batches or in parallel can be useful in other contexts, but they aren’t the standard default behavior for a one-way flow.

One-way flows don’t return a response to the sender, so Mule processes them asynchronously by default to avoid blocking the caller. This default uses a queue, so the message is accepted quickly and the actual work happens in the background, enabling decoupling between producer and consumer. The queued-asynchronous pattern also supports reliability and back-pressure—messages can be retried or persisted in the queue if needed. Synchronous would wait for a response, which isn’t appropriate for a one-way flow. Processing in batches or in parallel can be useful in other contexts, but they aren’t the standard default behavior for a one-way flow.