PL-900 Demonstrate the capabilities of Power Apps Practice Question
Exhibit
Refer to the exhibit.
{
"name": "ExpenseReport",
"fields": [
{"name": "Title", "type": "text"},
{"name": "Amount", "type": "currency"},
{"name": "Date", "type": "dateonly"},
{"name": "Approved", "type": "boolean", "default": false}
]
}Refer to the exhibit. A developer is creating a model-driven app based on a custom Dataverse table defined by this JSON. The app needs a form that shows the Approved field only when the amount is greater than 1000. Which feature should the developer use?
⚠ Common exam trap
PL-900 often tests the distinction between declarative business rules and code-based form scripting, tricking candidates into choosing JavaScript when the requirement is a simple conditional visibility that business rules handle natively.
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
✓
Business rule
Business rules in Power Apps model-driven apps are server-side/client-side logic components that can show, hide, enable, disable, or set field values based on conditions without writing code. They support conditional visibility tied to another field's value (e.g., show Approved only when Amount > 1000), and they run on both the form and the Dataverse layer. This makes them the correct no-code feature for the described requirement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Business rule
Why this is correct
A business rule runs client-side on the form, evaluating the Amount column and conditionally showing or hiding the Approved field when Amount exceeds 1000. This delivers the conditional visibility requirement without custom code or JavaScript.
- ✗
Form scripting
Why it's wrong here
Form scripting applies to classic Dynamics 365 forms using JavaScript, not to conditional visibility in modern model-driven apps. It tempts because scripting historically controlled field behaviour. The requirement is met by a business rule, which shows or hides the Approved field based on the amount value.
- ✗
Workflow process
Why it's wrong here
A workflow process runs asynchronously on record create or update and cannot control field visibility on a form. Business rules provide conditional show/hide logic driven by another column's value, which is exactly the Approved-when-amount-exceeds-1000 requirement.
- ✗
Power Automate flow
Why it's wrong here
Conditional visibility of a form field is a client-side rule evaluated as the user edits the record, which Power Automate cannot provide; flows run asynchronously on server events after save. Flows are tempting for automation such as approvals or notifications triggered by record changes, not for dynamic form behaviour.
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.