PL-900 Practice Question: Demonstrate the capabilities of Power Automate
Which TWO triggers are available for Power Automate flows that start from a Dataverse table? (Choose 2)
⚠ Common exam trap
PL-900 often tests whether candidates can distinguish connector-specific triggers — the trap is picking Outlook or SharePoint triggers for a Dataverse scenario because the flow's outcome involves email or files, confusing the trigger source with the action target.
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
✓
When a row is added, modified, or deleted
Option B, "When a row is added, modified, or deleted," is correct because it is the Dataverse connector's combined change trigger that fires on create, update, or delete events against a specified table, letting a flow react to any of those data operations. Option E, "When a row is added," is correct because it is the Dataverse connector's dedicated trigger that fires only when a new row is created in a chosen table, which is exactly a Dataverse-based start condition. Option A is wrong because "When a new email arrives (Outlook)" is an Outlook connector trigger, not a Dataverse trigger. Option C is wrong because "When a new file is created (SharePoint)" is a SharePoint connector trigger. Option D is wrong because "PowerApps button" is a manual trigger invoked from a Power Apps control, not a Dataverse table change trigger.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
When a new email arrives (Outlook)
Why it's wrong here
The Outlook trigger responds to mailbox events, not Dataverse row changes, so it cannot start a flow from a table. It tempts because it is a genuine Power Automate trigger, correct when the flow must begin on receipt of an email rather than on a Dataverse record event.
- ✓
When a row is added, modified, or deleted
Why this is correct
The Dataverse 'When a row is added, modified, or deleted' trigger supports change type selection, letting one flow respond to create, update, or delete events. This satisfies the requirement for a trigger covering all three row operations on a Dataverse table.
- ✗
When a new file is created (SharePoint)
Why it's wrong here
SharePoint's file-created trigger listens to a document library, not a Dataverse table, so it cannot initiate a table-driven flow. It tempts because it is a valid trigger, and would be the right choice when the flow must start when a file is added to SharePoint.
- ✗
PowerApps button
Why it's wrong here
The PowerApps button trigger is invoked manually from an app, not by Dataverse row creation, update or deletion, so it does not satisfy the table trigger requirement. It tempts because it is a legitimate trigger, correct when a user must start the flow on demand from a canvas app.
- ✓
When a row is added
Why this is correct
The Dataverse 'When a row is added' trigger fires solely on row creation, providing a dedicated create-only trigger. This satisfies the requirement for a trigger that starts a flow when a new row is inserted into a Dataverse table.
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 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.