A Copilot Studio agent is configured with a Generative answers node connected to a company SharePoint knowledge base. During testing, users ask questions outside the scope of the SharePoint content—the agent either confabulates an answer or returns an unhelpful 'I don't know' response. A developer must configure the agent to gracefully handle out-of-scope questions by escalating to a live agent. Which configuration best addresses this requirement?
Select an answer to reveal the explanation.
Short Explanation and Infographic
The Generative answers node has a built-in off-ramp—the 'No answer found' output. Connecting that output to the Escalate topic is like programming a phone system: if the AI can't help, automatically transfer to a real person.
Full explanation below image
Full Explanation
Copilot Studio's Generative answers node includes two output branches: one for when an answer is found and one for when no relevant content is found in the configured knowledge sources. The 'No answer found' output branch is the fallback path that developers should configure to handle out-of-scope queries gracefully.
Option D is correct because it accurately describes the proper mechanism: connecting the 'No answer found' output of the Generative answers node to the built-in 'Escalate' system topic. The Escalate system topic initiates a handoff to a configured live agent queue or routing system (such as Omnichannel for Customer Service), providing a seamless transition from AI to human support.
Option A is wrong because removing the Generative answers node eliminates the AI-driven knowledge retrieval entirely. Replacing it with Question nodes for 'every possible topic' is not scalable and defeats the purpose of AI-powered knowledge retrieval. Users cannot anticipate every topic to list.
Option B is wrong because it describes a conceptually similar idea but uses imprecise terminology—'set the No answer found branch to trigger an Escalate topic' is close, but the phrasing implies an action node rather than using the Generative answers node's native output branching. The correct approach uses the node's native 'No answer found' output connector, not an action trigger. Additionally, option D more precisely describes using the system topic pattern.
Option C is wrong because content moderation is designed to filter harmful or inappropriate content, not to manage knowledge gaps. Blocking out-of-scope questions at the moderation layer would suppress legitimate user questions without providing any resolution, creating a poor user experience.
Exam tip: Know the two output branches of the Generative answers node: the success path (answer found) and the fallback path (no answer found). Escalation patterns in Copilot Studio use the built-in 'Escalate' system topic. Configuring the fallback path is a common exam scenario.