Question 20 — AB-620 Practice Exam 5
For each statement below, indicate whether the answer is True or False
| Item | True | False |
|---|---|---|
| A vague child agent description can cause description-based routing to send requests to the child agent that belong to another domain. | □ | □ |
| An extremely narrow child agent description improves routing because it prevents valid in-scope requests from being missed. | □ | □ |
| A description for a child agent should use concrete language for its domain while avoiding terms that unnecessarily overlap with adjacent domains. | □ | □ |
| Testing both clearly in-scope requests and nearby out-of-scope requests is unnecessary until after a Copilot Studio solution is live. | □ | □ |
Correct answers
- A vague child agent description can cause description-based routing to send requests to the child agent that belong to another domain. → True
- An extremely narrow child agent description improves routing because it prevents valid in-scope requests from being missed. → False
- A description for a child agent should use concrete language for its domain while avoiding terms that unnecessarily overlap with adjacent domains. → True
- Testing both clearly in-scope requests and nearby out-of-scope requests is unnecessary until after a Copilot Studio solution is live. → False
Explanations
True: A description with poorly defined boundaries can match requests that should be handled by another child agent or capability.
False: A description that is too narrow can fail to match legitimate requests within the child agent’s intended responsibility.
True: Concrete domain and query-type language helps establish a clear routing boundary, while avoiding overlapping terminology reduces ambiguity between related child agents.
False: Testing representative in-scope and adjacent requests during design helps reveal routing overlap or missed matches before deployment.
A vague child agent description can cause description-based routing to send requests to the child agent that belong to another domain.
An extremely narrow child agent description improves routing because it prevents valid in-scope requests from being missed.
A description for a child agent should use concrete language for its domain while avoiding terms that unnecessarily overlap with adjacent domains.
Testing both clearly in-scope requests and nearby out-of-scope requests is unnecessary until after a Copilot Studio solution is live.