PL-900 Practice Question: Demonstrate the capabilities of Power Automate
A healthcare organization uses Power Automate to process patient intake forms. The flow retrieves data from a Microsoft Forms response, creates a record in a Microsoft Dataverse table, and sends a confirmation email. The organization needs to ensure that if the Dataverse record creation fails, the flow retries the operation up to three times before sending an error notification. What should they configure?
⚠ Common exam trap
The trap here is overlooking that retry policies are set per action, and error handling requires 'Configure run after' rather than assuming the flow will automatically notify on failure.
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
✓
Configure the Dataverse action's retry policy to a fixed interval with a count of 3, and add a 'Configure run after' on a subsequent action to send an error notification if the action fails.
The Dataverse action supports a built-in retry policy that can be configured to retry a specified number of times with a chosen interval. Setting it to a fixed interval with a count of 3 ensures up to three retries. To send an error notification after all retries fail, you add a subsequent action with 'Configure run after' set to run only if the Dataverse action fails. This leverages native error handling and meets the requirement without custom loops.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a 'Do until' loop to retry the Dataverse action until it succeeds or three attempts are made, then send an error notification.
Why it's wrong here
A 'Do until' loop can implement custom retry logic, but it is more complex and less efficient than using the built-in retry policy. It requires managing a counter and handling exceptions manually. The built-in retry policy is designed for this purpose and is simpler. While this approach could work, it is not the recommended best practice and introduces unnecessary complexity.
- ✓
Configure the Dataverse action's retry policy to a fixed interval with a count of 3, and add a 'Configure run after' on a subsequent action to send an error notification if the action fails.
Why this is correct
Setting the retry policy on the Dataverse action to a fixed interval with a count of 3 ensures the action retries up to three times if it fails. Then, by adding a 'Configure run after' on a subsequent action (e.g., send error notification) to run only if the Dataverse action fails, the flow can send an error notification after retries are exhausted. This combination meets the requirement precisely.
- ✗
Wrap the Dataverse action in a 'Scope' and set its retry policy to 3, then add a parallel branch to send an error notification.
Why it's wrong here
Using a 'Scope' with a retry policy is valid, but the retry policy is set on individual actions, not on the scope itself. You would need to set the retry policy on the Dataverse action inside the scope. Adding a parallel branch does not handle errors from the scope; you need a 'Configure run after' on a subsequent action. This option is partially correct but incomplete and misconfigures where the retry policy is applied.
- ✗
Set the 'Retry Policy' on the Dataverse action to 'Exponential' with a count of 3.
Why it's wrong here
The retry policy can be set to exponential with a count, but the default retry policy already retries four times. Setting it to three times may not align with the requirement to retry up to three times. However, the retry policy applies to the action level, and if it fails after retries, the flow will fail unless a 'Configure run after' is used. This option alone does not ensure an error notification is sent; additional error handling is needed.
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.