You are coding a customer-service multi-agent solution where a single user-facing orchestrator must delegate to billing, shipping, and returns specialists without those specialists talking directly to end users. Which pattern should you implement?
Select an answer to reveal the explanation.
Short Explanation
You need a single front door for the user, so use hub-and-spoke / orchestrator-subagent. The orchestrator handles the conversation and calls billing, shipping, and returns as spokes. Full mesh, forced sequential, or ungoverned broadcast all break that clean handoff.
Full Explanation
Orchestration patterns include hub-and-spoke and orchestrator-subagent. The hub-and-spoke orchestrator-subagent pattern matches a single conversational owner with delegated specialists. The fully mesh peer-to-peer approach where each specialist opens its own user channel breaks channel consistency and complicates security/session state. The sequential-only pipeline that always runs billing then shipping then returns imposes unnecessary steps for narrow intents. The broadcast-every-message-to-all-specialists-and-merge approach increases cost and contradiction risk without arbitration. Implement specialist calls as tool or agent-to-agent invocations returning results to the hub for final user wording. Exam tip: If only one agent should speak to the user, think hub-and-spoke.