PL-900 Practice Question: Demonstrate the capabilities of Power Automate
Exhibit
Refer to the exhibit.
```json
{
"definition": {
"$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
"triggers": {
"When_an_item_is_created": {
"type": "ApiConnection",
"inputs": {
"host": {
"connectionName": "shared_sharepointonline",
"operationId": "OnNewItem"
},
"parameters": {
"dataset": "https://contoso.sharepoint.com/sites/Sales",
"table": "Leads",
"triggerCondition": "@equals(triggerBody()?['Status'], 'New')"
}
}
}
},
"actions": {
"Send_email": {
"type": "ApiConnection",
"inputs": {
"host": {
"connectionName": "shared_office365",
"operationId": "SendEmail"
},
"parameters": {
"To": "sales@contoso.com",
"Subject": "New Lead Created",
"Body": "A new lead has been created."
}
}
}
}
}
}Refer to the exhibit. A Power Automate flow is triggered when an item is created in a SharePoint list. However, the flow runs for every new item, even those with Status other than 'New'. What is the issue?
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 expression is incorrect because it references triggerBody() which is not available in trigger conditions.
Trigger conditions in Power Automate cannot use the triggerBody() function. Instead, they must use triggerOutputs() to reference values from the trigger. Therefore, the expression @equals(triggerBody()?['Status'], 'New') is invalid and will not filter items, causing the flow to run for all new items regardless of their Status value.
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 trigger condition expression is incorrect because it references triggerBody() which is not available in trigger conditions.
Why this is correct
Trigger conditions must use triggerOutputs() or workflow() functions.
- ✗
The SharePoint connection is not configured correctly.
Why it's wrong here
The connection name is valid.
- ✗
The trigger should be set to 'When an item is created or modified'.
Why it's wrong here
Changing trigger type does not fix the expression issue.
- ✗
The flow should use a Condition action instead of a trigger condition.
Why it's wrong here
Trigger conditions can filter triggers, but the expression is invalid.
Go deeper
Related to this question
About these practice questions
One of 904 original PL-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways 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 have a Power Automate flow that sends an email notification when a new file is added to a SharePoint document library. Users report that emails are not being sent for some files. What is the most likely cause?
medium- A.The flow uses a premium connector that requires a license
- B.The file is being co-authored by multiple users
- ✓ C.A trigger condition is filtering out some files
- D.The file content contains sensitive information
Why C: Trigger conditions in Power Automate allow you to define expressions that must evaluate to true for the flow to run. If a condition is configured to filter out certain files (e.g., based on file name, metadata, or size), those files will not trigger the flow, and no email will be sent. This is the most likely cause when emails are missing for some files but not all.
Variation 2. You have a Power Automate flow that sends a notification to a Teams channel when a high-priority ticket is created in Dynamics 365. The flow works correctly for most tickets, but occasionally a ticket is missed. Upon checking the flow runs, you see that some runs show 'Skipped' status. What is the most likely cause?
medium- ✓ A.The trigger has a condition that filters out tickets with priority lower than 'High'.
- B.The flow requires a premium license, but some users have standard licenses.
- C.The flow's concurrency setting is too high, causing some triggers to be ignored.
- D.The flow uses a connection that has expired or lacks permissions.
Why A: The 'Skipped' status in Power Automate indicates that the flow was triggered but the trigger condition evaluated to false. In this scenario, the trigger has a condition that only allows high-priority tickets to proceed. When a ticket is created with a priority lower than 'High', the condition fails and the run is skipped. Option A correctly identifies this filter. Option B is incorrect because licensing issues would typically cause errors, not skips. Option C is wrong because high concurrency leads to queuing not skipping. Option D is incorrect as expired connections would cause failure, not skip.
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.