PL-900 Demonstrate the capabilities of Power Apps Practice Question
A model-driven app uses a business process flow to guide users through a sales process. The flow has multiple stages, and users complain that they can move to the next stage without completing required fields. What should the app maker do to enforce data entry?
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
✓
Set the fields as required in the business process flow stage
Setting fields as required in the business process flow stage ensures they must be filled before progressing to the next stage. Option A is incorrect because setting fields as business required in the entity applies globally, not just within the flow, and would affect all forms and views. Option C is incorrect because validation rules apply to the field's data integrity, not to flow stage transitions. Option D is incorrect because making fields read-only would prevent data entry entirely, not enforce required completion.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set the fields as business required in the entity
Why it's wrong here
Business required on the entity blocks saving the record, but does not stop a user advancing a business process flow stage; stage-gated enforcement needs required fields configured on the stage itself. Entity-level required fields are the right choice when the constraint must apply to every record regardless of process flow position.
- ✓
Set the fields as required in the business process flow stage
Why this is correct
Marking fields as required on the business process flow stage enforces data entry at stage level, blocking progression until those columns are populated. This directly satisfies the stem's constraint: users currently advance stages without completing required fields. Required-stage columns apply validation to the flow itself, unlike form-level requirements, which only govern the form.
- ✗
Add a validation rule on the entity fields
Why it's wrong here
Validation rules belong to Microsoft Dataverse tables and fire on save, not on stage navigation, so users still advance stages with empty fields. They suit enforcing field-level logic such as comparing dates or conditional ranges, not gating business process flow progression.
- ✗
Make the fields read-only in the business process flow stage
Why it's wrong here
Read-only fields cannot be edited at all, so technicians could never supply the data; this prevents entry rather than enforcing it. Read-only is correct when a stage should display values sourced elsewhere, such as fields populated by an earlier stage or calculated column.
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.