PL-900 Demonstrate the capabilities of Power Apps Practice Question
An organization has a model-driven app built on Dataverse. Users report that when they try to save a record, they receive an error about missing required fields, but they believe they filled them in. What is the most likely cause?
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
✓
A business rule is setting a field as required based on conditions
Business rules can dynamically set field requirements based on conditions, which may cause users to see missing required fields even if they filled in all originally required fields. Option B is incorrect because write permissions would prevent saving entirely, not just show missing required fields. Option C is incorrect because Power Automate flows run after a record is saved, not before, so they cannot block the save. Option D is incorrect because custom connectors are used for integrating external systems, not for Dataverse field validation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A business rule is setting a field as required based on conditions
Why this is correct
Business rules can set a column to required dynamically when conditions are met, so the field appears optional on the form yet blocks saving. Users believe they completed the fields, but the rule enforces a requirement the form does not visually indicate.
- ✗
The user does not have write permissions to the Dataverse table
Why it's wrong here
Missing write privileges on the Dataverse table produces an authorisation or privilege error, not a required-field validation message. It is tempting because permission problems commonly block record saves, and would be the cause when users can read records but cannot create or update them at all.
- ✗
A Power Automate flow is blocking the save
Why it's wrong here
Incorrect. Power Automate flows are triggered after a record is saved, so they cannot prevent the save.
- ✗
A custom connector is failing to validate data
Why it's wrong here
Custom connectors integrate external services; they do not participate in Dataverse table save validation, so they cannot generate a missing-required-field error. It is tempting because connector failures do interrupt app behaviour, and would be correct when data submitted to an external system fails validation there.
Go deeper
Related to this question
About these practice questions
One of 701 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 →
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.