Skip to main content
  1. Public practice questions
  2. AB-620 Practice Exams | AI Agent Builder Associate
  3. AB-620 Practice Exam 5

Question 17 — AB-620 Practice Exam 5

For each statement below, indicate whether the answer is True or False

Response matrix
ItemTrue False
A Copilot Studio child agent is suitable when a component must be published separately and accessed directly by users. □□
A child-agent design is appropriate when one team owns and maintains the complete agent solution. □□
A component can be a good child-agent candidate when it does not require separate authentication, model configuration, or application lifecycle management processes. □□
A capability intended to be reused by several independent agents is best confined to a child agent inside one parent. □□

Correct answers

  1. A Copilot Studio child agent is suitable when a component must be published separately and accessed directly by users. → False
  2. A child-agent design is appropriate when one team owns and maintains the complete agent solution. → True
  3. A component can be a good child-agent candidate when it does not require separate authentication, model configuration, or application lifecycle management processes. → True
  4. A capability intended to be reused by several independent agents is best confined to a child agent inside one parent. → False

Explanations

False: A component that requires independent publication or direct availability outside the parent needs an architectural boundary that a child agent does not provide.

True: Child agents align well with solutions in which one team owns and manages the parent and its modular capabilities together.

True: Shared authentication, model configuration, and application lifecycle management requirements are consistent with the coupled design of child agents.

False: A child agent belongs to its parent solution. A capability intended for reuse across multiple independent agents requires a more independently deployable design.

A Copilot Studio child agent is suitable when a component must be published separately and accessed directly by users.

A child-agent design is appropriate when one team owns and maintains the complete agent solution.

A component can be a good child-agent candidate when it does not require separate authentication, model configuration, or application lifecycle management processes.

A capability intended to be reused by several independent agents is best confined to a child agent inside one parent.