How are flows identified and invoked in MuleSoft?

• A. In MuleSoft, flows are identified by name and can be called via flow reference components in other flows
• B. Flows are identified by numeric IDs only and cannot be invoked externally
• C. Flows must be defined in XML with no references
• D. Flows run only as standalone processes

Answer: (A)

Flows are identified by a unique name, and you invoke one flow from another using a Flow Reference that points to that name. The flow name serves as the handle the runtime uses to locate and execute the target flow, enabling modular, reusable design. When a flow reference is reached, the current message payload and variables are passed into the called flow, and control returns after that flow completes, allowing composition of complex processes. Flows are defined in the Mule application’s XML, and while you can expose a flow externally (for example via an HTTP listener), internal invocation between flows is done with the flow reference. They are not identified by numeric IDs, and they aren’t restricted to standalone execution since they’re designed to be called from other flows.