PL-900 Practice Question: Demonstrate the capabilities of Microsoft Copilot Studio
A company has a copilot built with Microsoft Copilot Studio that handles customer inquiries. The copilot uses a topic that calls a Power Automate flow to create a case in Dynamics 365. During testing, the maker notices that when the flow fails, the copilot ends the conversation without informing the user. The maker wants the copilot to display a friendly error message and offer to retry the case creation. What should the maker do?
⚠ Common exam trap
The trap here is assuming that enabling 'Continue on error' or terminating the flow will automatically surface a user-friendly message, but only explicit topic branching provides that control.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
In the topic, add a condition after the flow action to check the flow's status and branch to a message node with a retry option.
To handle flow failures gracefully, the maker should add a condition node after the flow action that checks whether the flow succeeded. If it failed, the conversation branches to a message node that displays a user-friendly error and presents a retry option, such as a question node asking if the user wants to try again. This ensures the user is informed and can attempt the action again without restarting the entire conversation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
In the topic, add a condition after the flow action to check the flow's status and branch to a message node with a retry option.
Why this is correct
After a flow action, the topic can evaluate the output or use error handling. By adding a condition that checks if the flow succeeded, the maker can direct the conversation to a message node that displays a friendly error and offers a retry. This directly addresses the requirement to inform the user and provide a retry path.
- ✗
Enable the 'Continue on error' setting in the flow action within the topic.
Why it's wrong here
The 'Continue on error' setting in the topic's flow action allows the conversation to proceed even if the flow fails, but it does not provide a friendly error message or a retry option. It simply skips the error, which might lead to incorrect behavior. Additional nodes are needed to handle the error gracefully.
- ✗
Configure the Power Automate flow to send an email to the maker when it fails.
Why it's wrong here
Sending an email to the maker alerts the administrator but does not inform the user or offer a retry. The requirement is for the copilot to display a friendly error message and allow the user to retry. This approach does not improve the user experience during the conversation.
- ✗
Modify the flow to include a 'Terminate' action with a custom error message.
Why it's wrong here
A 'Terminate' action in Power Automate can set a status and message, but the copilot topic would still need to handle that output. Without additional logic in the topic, the copilot would not automatically display the message or offer a retry. The terminate action alone does not fulfill the user-facing requirement.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PL-900 question from scratch — 701 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This PL-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-900 exam.