Orchestrators, sub-agents, crews, delegation, and handoffs — the vocabulary of systems where agents work together.
Key vocabulary
Orchestrator agent — the coordinator that decomposes tasks and delegates to sub-agents.
Sub-agent — a specialised agent that receives a delegated sub-task and returns results.
Crew — a named group of agents with defined roles working toward a shared goal.
Handoff — transferring control from one agent to another, with context.
Agent-to-agent protocol — the defined format for how agents pass tasks and results.
0 / 25 completed
1 / 25
In a multi-agent system, the orchestrator agent is responsible for:
Orchestrator = the coordinator. It breaks the high-level goal into sub-tasks, assigns each to the right sub-agent, collects results, and synthesises the final output.
2 / 25
When a team says “we delegate the code review sub-task to the security sub-agent,” delegation means:
Delegation = assigning a sub-task with necessary context. Good delegation includes: clear task description, relevant context, expected output format, and constraints.
3 / 25
An agent handoff occurs when:
Handoff = passing the baton. Agent A hands off to Agent B with accumulated context (what has been done, what is needed, what constraints apply). Must include enough context to continue without losing progress.
4 / 25
A crew in multi-agent frameworks refers to:
Crew = a structured team of agents with roles (Researcher, Writer, Reviewer) and a shared goal. This pattern makes multi-agent collaboration explicit and manageable.
5 / 25
An agent-to-agent protocol defines:
Agent-to-agent protocol (e.g., MCP) standardises communication between agents. Defines: task format, context structure, result format, error codes, and cancellation signals.
6 / 25
PR #1234 has been submitted for the new user authentication service. During code review, Sarah comments: "I've routed this validation logic to Agent 'AuthVerify' – it handles all checks against our external API and returns a success/failure status. I've configured Agent 'RateLimit' to throttle requests if we hit the API limit."
Which of the following best describes Sarah's action in this scenario?
Sarah is demonstrating multi-agent orchestration by strategically *routing* the validation logic. This isn't simply assigning it to one developer; instead, she's leveraging different agents – 'AuthVerify' for direct API interaction and 'RateLimit' for throttling – based on their specific expertise. The key here is the automated distribution of work across agents, which avoids bottlenecks and improves system efficiency. Option A highlights a common misunderstanding about error handling; it's not the primary focus of orchestration in this context.
7 / 25
David from the DevOps team Slack channel writes: "Hey team, Agent 'Deployer' is now running automated deployments to staging based on the new orchestration rules. It's pulling the latest code from the 'staging' branch and performing integration tests before pushing to the QA environment.". What does 'pulling the latest code from the 'staging' branch' specifically represent within this multi-agent setup?
This describes a core aspect of automated workflows – Agent 'Deployer' is *fetching* the latest code. Option A is incorrect because it speaks to a manual action. Option C misinterprets conflict resolution; agents typically handle that automatically. Option D suggests an outdated branch strategy. The key here is autonomous retrieval, hence option B.
8 / 25
Maria in a PR description for PR #5678 (related to the new recommendation engine) states: "I've integrated Agent 'DataQuery' to retrieve user preferences. This agent dynamically queries our preference database, returning relevant data to Agent 'RecommendationGenerator' which then uses this information to create personalized suggestions.". What is Maria primarily demonstrating about the system architecture?
Maria's description highlights a key benefit of multi-agent orchestration – *separation of concerns*. Each agent has a specific responsibility (data retrieval vs. recommendation generation). Option A suggests a monolithic architecture which is typically less scalable and maintainable. Options C and D are incorrect as they describe centralized control or direct user intervention, respectively.
9 / 25
Ben, during a standup meeting, reports: "I've configured Agent 'Monitoring' to continuously track the performance of the payment processing service. It sends alerts to Agent 'Alerting' whenever response times exceed 2 seconds or transaction success rates drop below 99%."
This illustrates *reactive orchestration*. The agents aren't just passively observing; they're configured to *respond* to specific events (performance thresholds). Option A is incorrect as Ben isn't actively monitoring. Option C misrepresents the collaborative nature of the agents. Option D describes a problematic and likely insecure approach.
10 / 25
Chloe comments on a code review for PR #9012 (related to the new inventory management system): "I've utilized Agent 'InventoryUpdate' to synchronize stock levels across all warehouses. This agent communicates with our warehouse management API, ensuring accurate real-time data.". What is Chloe's primary intention when using Agent 'InventoryUpdate'?
Chloe's use of 'InventoryUpdate' signifies *automated synchronization*. This agent is designed to *continuously exchange data* with external APIs – a key characteristic of orchestrated workflows. Options A and C describe incorrect approaches; option D suggests an unnecessary disruption of existing processes.
11 / 25
PR #1234 has been submitted for the new user authentication service. During code review, Sarah comments: "I've routed this validation logic to Agent 'AuthVerify' – it handles all checks against our external API and returns a success/failure status. I've configured Agent 'RateLimit' to throttle requests if we hit the API limit."
Which of the following best describes Sarah's action in this scenario?
Sarah is demonstrating multi-agent orchestration by strategically *routing* the validation logic. This isn't simply assigning it to one developer; instead, she's leveraging different agents – 'AuthVerify' for direct API interaction and 'RateLimit' for throttling – based on their specific expertise. The key here is the automated distribution of work across agents, which avoids bottlenecks and improves system efficiency. Option A highlights a common misunderstanding about error handling; it's not the primary focus of orchestration in this context.
12 / 25
David from the DevOps team Slack channel writes: "Hey team, Agent 'Deployer' is now running automated deployments to staging based on the new orchestration rules. It's pulling the latest code from the 'staging' branch and performing integration tests before pushing to the QA environment.". What does 'pulling the latest code from the 'staging' branch' specifically represent within this multi-agent setup?
This describes a core aspect of automated workflows – Agent 'Deployer' is *fetching* the latest code. Option A is incorrect because it speaks to a manual action. Option C misinterprets conflict resolution; agents typically handle that automatically. Option D suggests an outdated branch strategy. The key here is autonomous retrieval, hence option B.
13 / 25
Maria in a PR description for PR #5678 (related to the new recommendation engine) states: "I've integrated Agent 'DataQuery' to retrieve user preferences. This agent dynamically queries our preference database, returning relevant data to Agent 'RecommendationGenerator' which then uses this information to create personalized suggestions.". What is Maria primarily demonstrating about the system architecture?
Maria's description highlights a key benefit of multi-agent orchestration – *separation of concerns*. Each agent has a specific responsibility (data retrieval vs. recommendation generation). Option A suggests a monolithic architecture which is typically less scalable and maintainable. Options C and D are incorrect as they describe centralized control or direct user intervention, respectively.
14 / 25
Ben, during a standup meeting, reports: "I've configured Agent 'Monitoring' to continuously track the performance of the payment processing service. It sends alerts to Agent 'Alerting' whenever response times exceed 2 seconds or transaction success rates drop below 99%."
This illustrates *reactive orchestration*. The agents aren't just passively observing; they're configured to *respond* to specific events (performance thresholds). Option A is incorrect as Ben isn't actively monitoring. Option C misrepresents the collaborative nature of the agents. Option D describes a problematic and likely insecure approach.
15 / 25
Chloe comments on a code review for PR #9012 (related to the new inventory management system): "I've utilized Agent 'InventoryUpdate' to synchronize stock levels across all warehouses. This agent communicates with our warehouse management API, ensuring accurate real-time data.". What is Chloe's primary intention when using Agent 'InventoryUpdate'?
Chloe's use of 'InventoryUpdate' signifies *automated synchronization*. This agent is designed to *continuously exchange data* with external APIs – a key characteristic of orchestrated workflows. Options A and C describe incorrect approaches; option D suggests an unnecessary disruption of existing processes.
16 / 25
PR #1234 has been submitted for the new user authentication service. During code review, Sarah comments: "I've routed this validation logic to Agent 'AuthVerify' – it handles all checks against our external API and returns a success/failure status. I've configured Agent 'RateLimit' to throttle requests if we hit the API limit."
Which of the following best describes Sarah's action in this scenario?
Sarah is demonstrating multi-agent orchestration by strategically *routing* the validation logic. This isn't simply assigning it to one developer; instead, she's leveraging different agents – 'AuthVerify' for direct API interaction and 'RateLimit' for throttling – based on their specific expertise. The key here is the automated distribution of work across agents, which avoids bottlenecks and improves system efficiency. Option A highlights a common misunderstanding about error handling; it's not the primary focus of orchestration in this context.
17 / 25
David from the DevOps team Slack channel writes: "Hey team, Agent 'Deployer' is now running automated deployments to staging based on the new orchestration rules. It's pulling the latest code from the 'staging' branch and performing integration tests before pushing to the QA environment.". What does 'pulling the latest code from the 'staging' branch' specifically represent within this multi-agent setup?
This describes a core aspect of automated workflows – Agent 'Deployer' is *fetching* the latest code. Option A is incorrect because it speaks to a manual action. Option C misinterprets conflict resolution; agents typically handle that automatically. Option D suggests an outdated branch strategy. The key here is autonomous retrieval, hence option B.
18 / 25
Maria in a PR description for PR #5678 (related to the new recommendation engine) states: "I've integrated Agent 'DataQuery' to retrieve user preferences. This agent dynamically queries our preference database, returning relevant data to Agent 'RecommendationGenerator' which then uses this information to create personalized suggestions.". What is Maria primarily demonstrating about the system architecture?
Maria's description highlights a key benefit of multi-agent orchestration – *separation of concerns*. Each agent has a specific responsibility (data retrieval vs. recommendation generation). Option A suggests a monolithic architecture which is typically less scalable and maintainable. Options C and D are incorrect as they describe centralized control or direct user intervention, respectively.
19 / 25
Ben, during a standup meeting, reports: "I've configured Agent 'Monitoring' to continuously track the performance of the payment processing service. It sends alerts to Agent 'Alerting' whenever response times exceed 2 seconds or transaction success rates drop below 99%."
This illustrates *reactive orchestration*. The agents aren't just passively observing; they're configured to *respond* to specific events (performance thresholds). Option A is incorrect as Ben isn't actively monitoring. Option C misrepresents the collaborative nature of the agents. Option D describes a problematic and likely insecure approach.
20 / 25
Chloe comments on a code review for PR #9012 (related to the new inventory management system): "I've utilized Agent 'InventoryUpdate' to synchronize stock levels across all warehouses. This agent communicates with our warehouse management API, ensuring accurate real-time data.". What is Chloe's primary intention when using Agent 'InventoryUpdate'?
Chloe's use of 'InventoryUpdate' signifies *automated synchronization*. This agent is designed to *continuously exchange data* with external APIs – a key characteristic of orchestrated workflows. Options A and C describe incorrect approaches; option D suggests an unnecessary disruption of existing processes.
21 / 25
PR #1234 has been submitted for the new user authentication service. During code review, Sarah comments: "I've routed this validation logic to Agent 'AuthVerify' – it handles all checks against our external API and returns a success/failure status. I've configured Agent 'RateLimit' to throttle requests if we hit the API limit."
Which of the following best describes Sarah's action in this scenario?
Sarah is demonstrating multi-agent orchestration by strategically *routing* the validation logic. This isn't simply assigning it to one developer; instead, she's leveraging different agents – 'AuthVerify' for direct API interaction and 'RateLimit' for throttling – based on their specific expertise. The key here is the automated distribution of work across agents, which avoids bottlenecks and improves system efficiency. Option A highlights a common misunderstanding about error handling; it's not the primary focus of orchestration in this context.
22 / 25
David from the DevOps team Slack channel writes: "Hey team, Agent 'Deployer' is now running automated deployments to staging based on the new orchestration rules. It's pulling the latest code from the 'staging' branch and performing integration tests before pushing to the QA environment.". What does 'pulling the latest code from the 'staging' branch' specifically represent within this multi-agent setup?
This describes a core aspect of automated workflows – Agent 'Deployer' is *fetching* the latest code. Option A is incorrect because it speaks to a manual action. Option C misinterprets conflict resolution; agents typically handle that automatically. Option D suggests an outdated branch strategy. The key here is autonomous retrieval, hence option B.
23 / 25
Maria in a PR description for PR #5678 (related to the new recommendation engine) states: "I've integrated Agent 'DataQuery' to retrieve user preferences. This agent dynamically queries our preference database, returning relevant data to Agent 'RecommendationGenerator' which then uses this information to create personalized suggestions.". What is Maria primarily demonstrating about the system architecture?
Maria's description highlights a key benefit of multi-agent orchestration – *separation of concerns*. Each agent has a specific responsibility (data retrieval vs. recommendation generation). Option A suggests a monolithic architecture which is typically less scalable and maintainable. Options C and D are incorrect as they describe centralized control or direct user intervention, respectively.
24 / 25
Ben, during a standup meeting, reports: "I've configured Agent 'Monitoring' to continuously track the performance of the payment processing service. It sends alerts to Agent 'Alerting' whenever response times exceed 2 seconds or transaction success rates drop below 99%."
This illustrates *reactive orchestration*. The agents aren't just passively observing; they're configured to *respond* to specific events (performance thresholds). Option A is incorrect as Ben isn't actively monitoring. Option C misrepresents the collaborative nature of the agents. Option D describes a problematic and likely insecure approach.
25 / 25
Chloe comments on a code review for PR #9012 (related to the new inventory management system): "I've utilized Agent 'InventoryUpdate' to synchronize stock levels across all warehouses. This agent communicates with our warehouse management API, ensuring accurate real-time data.". What is Chloe's primary intention when using Agent 'InventoryUpdate'?
Chloe's use of 'InventoryUpdate' signifies *automated synchronization*. This agent is designed to *continuously exchange data* with external APIs – a key characteristic of orchestrated workflows. Options A and C describe incorrect approaches; option D suggests an unnecessary disruption of existing processes.
What will I practice in "Multi-Agent Orchestration Vocabulary | Coders Lingo"?
This is an AI Agents Language exercise set. It walks through 25 scenario-based multiple-choice questions built around real usage of AI Agents Language terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 25 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the AI Agents Language vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more AI Agents Language exercises?
See the AI Agents Language exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — AI Agents Language vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.