MuleSoft Developer 2 Certification Practice Exam

The concept being tested is how to cap parallel work inside a Scatter-Gather. Scatter-Gather splits a message into multiple branches and processes those branches in parallel. To prevent overwhelming downstream systems or the Mule runtime, you can limit how many branches run at the same time. The maxConcurrency property provides that precise control: it sets the maximum number of concurrent branch executions. If there are more branches than this limit, the extras wait in a queue until a running branch finishes. Other terms don’t directly apply as the per-scatter limiter. Concurrency is a general idea of parallel work, but the specific property used to bound Scatter-Gather execution is maxConcurrency. ThreadPoolSize relates to the underlying thread pool used by the runtime more broadly, not the per-scatter concurrency limit, and parallelism isn’t the property used to gate the scatter’s parallel processing.