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
Candidates often confuse Scope with Condition. Scope is for grouping actions into a single unit, not for implementing conditional logic. Ensure you use a Condition action to evaluate the expense amount and route approvals accordingly.
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 to check the expense amount allows the flow to branch to different approval actions based on the amount. If the expense exceeds $5,000, the approval request is sent to a senior manager; otherwise, it goes to the regular manager. This approach is simple, easy to maintain, and aligns with Power Automate's built-in conditional logic. Option A (Scope) is used for grouping actions but does not provide conditional branching. Option B (child flow) adds unnecessary complexity for this straightforward scenario. Option D (parallel branches) would send approvals to both managers simultaneously, which does not meet the conditional requirement.
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
Incorrect. A Scope action groups actions together but does not provide conditional logic to check the expense amount.
- ✗
Create a child flow that handles the approval routing
Why it's wrong here
Incorrect. A child flow adds unnecessary complexity for this simple conditional requirement. The flow can be easily implemented with a Condition action.
- ✓
Add a Condition action to check the expense amount and then use two separate approval actions
Why this is correct
Correct. Adding a Condition action to check the expense amount and then using separate approval actions based on the result is the simplest and most maintainable approach.
- ✗
Add parallel branches for each approval path
Why it's wrong here
Incorrect. Parallel branches would send approvals to both managers simultaneously, which does not meet the conditional requirement of sending only to the senior manager when the amount exceeds $5,000.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PL-900 question from scratch — 904 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 scenario requires conditional logic to evaluate the expense amount and branch accordingly. A Condition action is ideal for the primary split (above/below thresholds), and nested conditions handle the sub-branches (e.g., condition for >$5,000 with nested approval actions, else condition for $1,000-$5,000, else no approval). Option A is incorrect because a Switch action is suitable for discrete values, not numerical ranges. Option B is incorrect because Apply to each is used for iterating over arrays, not for conditional branching. Option D is incorrect because Parallel branches execute actions concurrently and do not implement decision-based branching logic.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.