Northwind Traders has five different Copilot Studio agents — one each for Sales, HR, IT, Finance, and Legal departments. All five agents need to handle the same 'Office Location Lookup' functionality. The team wants to avoid maintaining five separate copies of this topic. What is the recommended approach?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Duplicating topics across five agents is like photocopying a policy manual into five binders — every update requires five edits. Copilot Studio's agent library lets you define a topic once and reuse it across agents. The correct answer is B.
Full explanation below image
Full Explanation
## Why B is Correct Copilot Studio supports agent libraries (also called component libraries or shared topic libraries) that allow teams to create topics once and share them across multiple agents. When the underlying topic is updated in the library, all agents referencing it pick up the change without individual edits. This follows the DRY (Don't Repeat Yourself) principle for agent development.
## Why the Distractors Are Wrong A (Duplicate topics): Maintaining five copies creates drift — teams will inevitably update some but not all, leading to inconsistent behavior across agents.
C (Power Automate flow): A flow can centralize backend logic (data retrieval), but the conversational topic itself (trigger phrases, response nodes, variable handling) still needs to be built in each agent. This solves only part of the problem.
D (Master agent redirect): Redirecting five agents to a sixth agent adds latency, complicates conversation context passing, and is not the recommended pattern for shared topic reuse.
## Exam Tip The AB-620 exam distinguishes between sharing conversational topic logic (use agent/component libraries) and sharing backend data logic (use Power Automate or connectors). Match the tool to what layer is being shared.