PL-900 Practice Question: Demonstrate the capabilities of Microsoft Copilot Studio

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Add a Fallback topic that tells the customer to call the support phone number when the copilot does not understand.

  Why it's wrong here

  A fallback topic handles unrecognized input by offering alternative guidance, but it does not transfer the session to a human agent. Telling the customer to call a phone number abandons the live chat rather than escalating it, and it does not involve Dynamics 365 Customer Service at all. This approach conflicts with the stated requirement for a live handoff to an agent.

• ✗

  Create a Power Automate cloud flow that sends an email to the support manager whenever the phrase 'talk to a person' is detected.

  Why it's wrong here

  Emailing a manager is an asynchronous notification, not a live chat handoff. It would not place the customer into the Dynamics 365 Customer Service queue or connect them to an agent in real time. While a flow can be useful for alerts, it does not satisfy the requirement that the conversation itself transfers to a human agent, so this action is unnecessary and insufficient.

• ✓

  In Dynamics 365 Customer Service, configure an Omnichannel workstream and queue that can receive the escalated conversations.

  Why this is correct

  The Omnichannel engagement hub must have a workstream and queue configured to accept and route incoming conversations. These components define the skills, capacity, and assignment rules that determine which human agent receives the escalated chat. Without a receiving queue, the handoff from Copilot Studio has nowhere to land, so the conversation cannot reach a live agent and the escalation fails.

• ✗

  Publish the copilot to the 'Mobile app' channel and enable the 'Require authentication' option.

  Why it's wrong here

  Publishing to the Mobile app channel controls where the copilot is reachable, not how live chats escalate to agents. Requiring authentication verifies user identity but does not create a route into the Customer Service agent workspace. These settings could even block the intended web chat scenario, so they do not contribute to the live-agent handoff requirement and are incorrect for this task.

• ✓

  In Copilot Studio, configure the copilot to use the Dynamics 365 Customer Service handoff, which passes the conversation to the Omnichannel engagement hub.

  Why this is correct

  Copilot Studio includes a native handoff capability for Dynamics 365 Customer Service. Enabling it routes the live conversation into the Omnichannel engagement hub, where routing rules and queues deliver the chat to an available human agent. Without this copilot-side handoff configuration, the conversation would simply end or loop in the bot, so this step is required to move the customer into the agent workspace.

Go deeper

Related to this question