What describes private flows?

What describes private flows?

• A. flows without message sources
• B. private flows
• C. subflows
• D. flow processing strategy

Answer: (A)

Private flows are flows that have no inbound message sources, so they can’t be triggered directly by external messages. They’re meant for internal use, called from other flows via a flow-ref, to encapsulate reusable processing without exposing an API endpoint. That’s why describing private flows as “flows without message sources” is the most accurate. Subflows are a related concept used to share steps inside a flow, but they’re not the same thing as private flows. A flow processing strategy is about how messages are processed, not whether the flow has an inbound source.

Private flows are flows that have no inbound message sources, so they can’t be triggered directly by external messages. They’re meant for internal use, called from other flows via a flow-ref, to encapsulate reusable processing without exposing an API endpoint. That’s why describing private flows as “flows without message sources” is the most accurate. Subflows are a related concept used to share steps inside a flow, but they’re not the same thing as private flows. A flow processing strategy is about how messages are processed, not whether the flow has an inbound source.