Which statement best describes the difference between a Flow and a Sub-flow in Mule 4?

• A. A Flow is an independent processing path that handles events; A Sub-flow is a reusable path that cannot be triggered directly and is invoked from flows using flow-ref.
• B. A Flow is a reusable path; Sub-flow is an independent processing path.
• C. A Flow is only used for testing; Sub-flow is used for inbound HTTP requests.
• D. A Flow is a memory management unit; Sub-flow is a database access layer.

Answer: (A)

The key idea is how a Flow and a Sub-flow function within a Mule 4 application. A Flow is an independent processing path that can be started by an inbound event, such as an HTTP request or a queue message. It represents a complete entry point and handles the full lifecycle of that event.

A Sub-flow, on the other hand, is a reusable piece of processing that has no inbound endpoint of its own. It’s designed to be invoked from within a Flow using a flow-ref. This lets you factor out common steps—like validation, transformation, or enrichment—so multiple Flows can reuse the same logic without duplicating it. The Sub-flow receives the current message, performs its operations, and returns control back to the calling Flow.

So the best description is that a Flow is an entry-point processing path that handles events, while a Sub-flow is a reusable path that cannot be triggered directly and is invoked from flows using flow-ref.