Question 22 — AB-620 Practice Exam 1
A Copilot Studio solution uses a parent agent with separate child agents for order lookup and returns. What two architectural benefits does this design provide when each domain requires many specialized actions and must remain easy to maintain? (Select two answers)
Each child receives its own tool capacity at its orchestration layer
Related instructions, tools, and knowledge can be grouped by domain
Each child can be released independently from the parent solution
Each child must exchange data with the parent through an external deployment
Correct answers
Each child receives its own tool capacity at its orchestration layer
Related instructions, tools, and knowledge can be grouped by domain
Explanations
Correct:
Each child receives its own tool capacity at its orchestration layer
Tool limits are applied per orchestration layer. Separating domains into child agents prevents all domain-specific tools from competing for capacity solely within the parent's orchestration layer.
Related instructions, tools, and knowledge can be grouped by domain
Keeping domain-specific capabilities together gives each child a focused purpose and narrows the set of choices involved in routing, which improves organization, maintenance, and routing precision.
Wrong:
Each child can be released independently from the parent solution
Child agents are managed and published as part of their parent. Independent release cycles are a reason to consider a connected agent instead.
Each child must exchange data with the parent through an external deployment
Child agents reside within the same solution as the parent. This makes structured exchange through inputs and outputs more direct than coordination with separately deployed agents.