Suggested answer

Multi-agent orchestration is an architecture where a primary agent (the orchestrator) decomposes a complex goal into subtasks and delegates them to specialised worker agents, rather than one agent handling everything.

1. Orchestrator Agent: Receives the high-level user request, reasons about how to decompose it, and routes subtasks to appropriate worker agents. It synthesises the results from workers into a final response. It is responsible for the overall goal completion and managing the interaction state across agent handoffs.
2. Worker Agent: A specialised agent with a narrowly scoped set of Topics and Actions — e.g., a dedicated "Billing Agent" or "Inventory Agent". It receives a specific delegated task, executes it, and returns a result to the orchestrator. Worker agents have limited scope by design, making them easier to test, maintain, and reuse across multiple orchestrator agents. Handoff: The mechanism by which control (and relevant context) is passed from one agent to another. Context passing must be explicitly designed — workers need sufficient context from the orchestrator to complete their task without asking the user to repeat information.

Practice content for interview preparation; not an official vendor answer. Verify details against current product documentation.

Community comments (0)

No comments yet.

Sign in or create a free account to add a comment. Comments are moderated before they appear.

Plain text only, 3–2000 characters. A moderator reviews every comment before it is published.