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
The Generative answers node gives you a 'No answer found' output for exactly this case. You connect that fallback output to the Escalate system topic, so when SharePoint content can't answer, the agent hands off to a live agent instead of guessing or stalling.
Full Explanation
Copilot Studio's Generative answers node includes two output branches: a branch for when an answer is found and a branch for when no relevant content is found in the configured knowledge sources. The 'No answer found' output branch is the fallback path developers should configure to handle out-of-scope queries gracefully.
The best configuration is to configure the Generative answers node's fallback path and connect the 'No answer found' output to an Escalate system topic so the agent hands off to a live agent when content is unavailable. This 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.
Removing the Generative answers node entirely and replacing it with a series of Question nodes covering every possible topic is wrong because it 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.
Setting the Generative answers node's 'No answer found' branch to trigger a custom topic that sends the user back to the SharePoint knowledge base is wrong because it does not provide the required live-agent handoff. It may simply loop the user back to the same unavailable knowledge source, and it does not use the built-in Escalate system topic pattern that transfers the conversation to a human support queue. The correct approach uses the node's native 'No answer found' output connector, not a custom topic that returns the user to the knowledge base.
Enabling content moderation settings to block out-of-scope questions from reaching the Generative answers node 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.