Error Handling in Power Automate: Scope and Configure Run After
Which TWO actions can be used to implement error handling in a Power Automate flow?
⚠ Common exam trap
PL-900 often tests the misconception that Condition or Compose actions handle errors — candidates overlook that Run After settings and Scope actions are the actual error-handling constructs.
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
✓
Use a Scope action to group actions and configure error handling
Option A is correct because the Scope action groups a set of actions into a single block, and its Run After settings can be configured so that a subsequent action (such as a Terminate or a notification) runs only when the Scope fails, times out, or is skipped, which is the standard pattern for try/catch-style error handling in Power Automate. Option D is correct because Run After settings define the dependency and outcome conditions (is successful, has failed, is skipped, has timed out) under which an action executes, and configuring an action to run after a previous action 'has failed' is the core mechanism for branching into error-handling logic. Option B is not the intended answer because a Condition action only evaluates data expressions at runtime and cannot by itself detect whether a prior action failed; failure detection is driven by Run After, not by Condition. Option C is not the intended answer because Compose merely outputs a value or expression for later use and does not provide any error-detection or error-handling behavior. Option E is not the intended answer because Apply to Each is a looping construct for iterating over arrays and does not implement error handling.
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 actions and configure error handling
Why this is correct
A Scope action groups actions into a block, and its 'Configure run after' settings let subsequent actions run on failure or timeout, enabling structured error handling. This satisfies the requirement for implementing error handling within a Power Automate flow.
- ✗
Add a Condition action to check for errors
Why it's wrong here
A Condition action evaluates data values and branches logic; it does not intercept runtime failures or route them to handlers. It suits business-rule branching, such as checking a field's value. Error handling requires configuring 'Configure run after' on subsequent actions or a Scope with parallel failure branches.
- ✗
Use a Compose action to store error details
Why it's wrong here
Compose merely stores a value or expression output for later reference; it neither catches nor redirects a failed action. It suits shaping data or holding intermediate results. Error handling needs 'Configure run after' settings or a Scope block whose failure branch runs remediation actions, which Compose alone cannot provide.
- ✓
Configure Run After settings
Why this is correct
Run After settings define each action's dependency on its predecessor's outcome, letting you branch on failure, timeout or skip. This is the native error-handling mechanism in Power Automate, satisfying the requirement to implement error handling within a flow.
- ✗
Add an Apply to Each action
Why it's wrong here
Apply to Each iterates over a collection; it provides no error-handling configuration such as run-after settings or parallel-failure thresholds. It is tempting because loops often contain the failing action, and wrapping steps in a Scope with run-after conditions is the actual mechanism for catching and routing errors.
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. Which TWO actions can be used to implement error handling in a Power Automate flow? (Choose two.)
medium- ✓ A.Configure Run After settings
- B.Apply to each
- C.Compose
- ✓ D.Scope
- E.Condition
Why A: 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.
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.