Which parameter controls the maximum concurrency for a Flow in Mule?

• A. Flow: max concurrency
• B. Batch Job: Max concurrency
• C. Scatter-Gather: Max concurrency
• D. HTTP connector: use persistent connections

Answer: (A)

In Mule, you control how many messages a Flow can process at the same time by setting the Flow's max concurrency. This directly determines how many messages can be handled in parallel by that Flow, up to the configured limit. If this is set higher, more messages can be processed concurrently, improving throughput for flows that can safely run in parallel. The other options refer to different constructs: a Batch Job has its own concurrency settings for batch steps, Scatter-Gather has a separate setting for how many branches run in parallel, and the HTTP connector setting relates to connection reuse rather than Flow-level processing concurrency. Therefore, the Flow: max concurrency parameter is the one that controls the maximum concurrent processing for a Flow.