PL-900 Practice Question: Demonstrate the capabilities of Power Automate
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?
⚠ Common exam trap
PL-900 often tests the misconception that Switch is suitable for range-based conditions, but Switch only works with discrete values; candidates must recognize that nested Condition actions are required for multi-level if-then-else logic.
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
✓
Condition action with nested conditions
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.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Switch action with cases for each range
Why it's wrong here
A Switch action evaluates a single expression against discrete, static values, but this scenario requires evaluating a numeric expense amount against three overlapping ranges with dynamic thresholds. The Switch cannot handle conditions like "between $1,000 and $5,000" because it lacks operators for greater-than or less-than comparisons. It is tempting because Switch neatly organises multiple fixed-value branches, such as mapping status codes to approval paths, where each case matches an exact, non-numeric label.
- ✗
Apply to each with a condition inside
Why it's wrong here
Apply to each iterates over a collection, and a condition inside it branches per item; the scenario needs tiered branching on a single expense amount, not iteration. Apply to each is correct when processing an array of records, such as every line in a submitted expense report.
- ✓
Condition action with nested conditions
Why this is correct
Nested conditions let the flow first test whether the expense exceeds $5,000, then apply a second condition for the $1,000-$5,000 band. This branching satisfies the three-tier approval requirement, routing to both approvers, manager only, or none.
- ✗
Parallel branches for both approval paths
Why it's wrong here
Parallel branches run simultaneously, so both approval paths would execute regardless of amount, ignoring the $1,000 and $5,000 thresholds. Parallel branches are correct when independent actions must run concurrently, such as notifying two separate teams at once rather than choosing between them.
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.