PL-900 Condition action Practice Question
Fabrikam Inc. uses Power Automate to automate expense report approvals. The flow is triggered when an expense report is submitted in a SharePoint list. The flow then sends an approval request to the expense approver via the Approvals connector. If approved, the flow updates the SharePoint list status to 'Approved' and sends a confirmation email to the submitter. If rejected, it updates the status to 'Rejected' and sends a rejection email. Currently, the flow works for single approvers, but the business now requires that if the expense amount exceeds $5,000, the approval must be sent to a senior manager instead of the regular manager. You need to modify the flow to meet this requirement with minimal maintenance. What should you do?
⚠ Common exam trap
PL-900 often tests whether candidates over-engineer with child flows or parallel branches when a simple Condition action is sufficient — the trap is choosing a more 'advanced' construct that actually violates the single-approver requirement.
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
✓
Add a Condition action to check the expense amount and then use two separate approval actions
Adding a Condition action that checks the expense amount and then branches to two separate approval actions is the simplest, lowest-maintenance way to route based on a threshold. It keeps everything in one flow, uses native controls, and requires no additional flows or complex orchestration. This directly satisfies the requirement with minimal moving parts.
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 Scope action to group the approval actions
Why it's wrong here
Scope groups actions for error handling; it cannot route an approval to a different approver based on the expense amount. It is tempting because scopes organise approval blocks, but the requirement needs a condition evaluating the amount before selecting the approver.
- ✗
Create a child flow that handles the approval routing
Why it's wrong here
A child flow adds a separate flow to maintain and still needs the amount-based routing logic inside it, so it does not satisfy minimal maintenance. Child flows suit reuse across multiple parent flows, not conditional approver selection within one existing flow.
- ✓
Add a Condition action to check the expense amount and then use two separate approval actions
Why this is correct
A Condition action evaluates the expense amount and routes to either the regular or senior manager approval action, satisfying the over-$5,000 routing requirement without rebuilding the flow. Two separate approval actions keep each branch explicit and require minimal ongoing maintenance.
- ✗
Add parallel branches for each approval path
Why it's wrong here
Parallel branches run both approval paths simultaneously rather than selecting one by amount, so the senior manager and regular manager would both receive requests. Parallel branches suit concurrent independent tasks, not mutually exclusive routing driven by a threshold condition.
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 →
Same concept, more angles
1 more way this is tested on PL-900
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You are designing a Power Automate flow that processes approvals for expense reports. If an expense exceeds $5,000, the flow must require approval from both the manager and the finance director. If the expense is between $1,000 and $5,000, only manager approval is needed. For expenses under $1,000, no approval is required. Which control structures should you use?
hard- A.Switch action with cases for each range
- B.Apply to each with a condition inside
- ✓ C.Condition action with nested conditions
- D.Parallel branches for both approval paths
Why C: The Condition action in Power Automate supports nested conditions, allowing you to evaluate the expense amount in a hierarchical manner: first check if it exceeds $5,000 (requiring both manager and finance director approval), then within the 'No' branch, check if it's between $1,000 and $5,000 (requiring only manager approval), and finally handle the under $1,000 case. This structure directly mirrors the decision tree described in the requirements. The Condition action is the native control for if-then-else logic in Power Automate, and nesting provides the necessary multi-level branching without unnecessary complexity.
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.