Which statement about private flows is accurate according to the material?

• A. They are typically flows without message sources
• B. They must be deployed to production
• C. They rely on SOAP endpoints
• D. They are always public

Answer: (A)

Private flows in MuleSoft are internal pieces of logic that don’t have their own inbound message source. They’re built to be reusable within an application and are invoked by other flows (for example, via a flow-ref) rather than being exposed to external clients. Because they don’t listen for external messages, they’re typically flows without message sources. This makes them ideal for modularizing common processing steps like transformations, validations, or routing logic that several public flows can share.

Other statements don’t fit because private flows aren’t defined by being deployed to production, nor by relying on SOAP endpoints, and they aren’t inherently public. They sit inside the application and are invoked internally, regardless of the specific transport or endpoint they may interact with.