PL-900 Practice Question: Demonstrate the capabilities of Power Automate
Which TWO actions can be used to implement error handling in a Power Automate flow? (Choose two.)
⚠ Common exam trap
PL-900 often tests the misconception that control flow actions like 'Condition' or 'Apply to each' can handle errors, when in fact error handling requires 'Configure Run After' and 'Scope'.
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 Run After settings
Option A (Configure Run After settings) is correct because Power Automate lets you set each action's 'Run after' property to fire on Succeeded, Failed, Skipped, or Timed Out, so a subsequent action can handle or compensate for a prior action's failure. Option D (Scope) is correct because a Scope is a container action that groups multiple actions and exposes the same Run After configuration, enabling try/catch-style patterns where a following Scope or action runs only when the first Scope fails. Options B (Apply to each), C (Compose), and E (Condition) are not error-handling mechanisms: Apply to each is a loop, Compose simply outputs a value or expression, and Condition branches on data values rather than on action success or failure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Configure Run After settings
Why this is correct
Run After settings define whether an action runs after the preceding action succeeds, fails, is skipped, or times out, letting the flow branch on failure. This satisfies the stem's requirement for implementing error handling within a Power Automate flow.
- ✗
Apply to each
Why it's wrong here
Apply to each iterates over a collection and offers no built-in failure capture; a failing iteration stops or skips items without a defined recovery path. It is intended for looping over arrays. Error handling instead comes from Scope blocks combined with Configure run after conditions.
- ✗
Compose
Why it's wrong here
Compose only outputs its inputs and has no error-handling configuration; it cannot catch failures or define alternate branches. It is used to shape or store data within a flow. The Configure run after setting on subsequent actions, plus Scope with run-after conditions, provides the actual error handling.
- ✓
Scope
Why this is correct
A Scope groups actions into a block whose failure can be caught by a subsequent Configure run after setting, enabling try-catch style error handling. This lets the flow branch to remediation or notification actions when any contained action fails.
- ✗
Condition
Why it's wrong here
A Condition evaluates an expression and branches the flow; it does not catch, retry or log failures. It is tempting because branching looks like handling, but error handling requires configuring the action's run-after settings or a Scope with parallel failure paths.
Go deeper
Related to this question
About these practice questions
This PL-900 question is part of Courseiva's 701-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.