PL-900 Practice Question: Demonstrate the capabilities of Power Automate
Exhibit
Refer to the exhibit.
{
"triggers": {
"When_an_item_is_created_or_modified": {
"inputs": {
"dataset": "https://contoso.sharepoint.com/sites/sales",
"table": "Orders",
"triggerConditions": "@equals(triggerOutputs()?['body/Status'], 'New')"
}
}
}
}A Power Automate flow uses the trigger configuration shown. Users report that the flow does not start when a new order is added with Status = 'Pending'. What is the most likely cause?
⚠ Common exam trap
The trap here is that candidates often overlook the trigger condition configuration and assume the flow should run on any new item, confusing the trigger event type (creation/modification) with the filtering logic applied by the condition.
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
✓
The trigger condition only allows items with Status = 'New'
The trigger condition explicitly filters for items where Status equals 'New'. When a new order is added with Status = 'Pending', the condition evaluates to false, so the flow does not trigger. Trigger conditions in Power Automate act as a pre-filter on the trigger event, preventing the flow from running if the condition is not met.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The SharePoint dataset URL is incorrect
Why it's wrong here
An incorrect dataset URL would prevent the flow from connecting to the list entirely, so no orders of any Status would trigger it, not just Pending ones. It tempts because misconfigured connections commonly break triggers, and would be correct if every run failed.
- ✗
The flow is paused or turned off
Why it's wrong here
A paused flow would stop all runs regardless of Status value, yet the stem describes failures specific to Pending orders, so the trigger condition itself is at fault. It tempts because pausing is a common cause of silent flow failure, and would be correct if no runs occurred at all.
- ✗
The trigger only fires on modification, not creation
Why it's wrong here
The SharePoint trigger fires on both item creation and modification by default, so a creation-only event still triggers it; the failure lies in the condition filter. It tempts when triggers are deliberately set to modified items only, which would be correct if new orders never fired at all.
- ✓
The trigger condition only allows items with Status = 'New'
Why this is correct
The trigger's condition filters on Status = 'New', so Power Automate never fires for orders created with Status = 'Pending'. The condition must be edited to match the intended value before the flow can start.
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 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.