PL-900 Demonstrate the capabilities of Power Apps Practice Question
A team is designing a model-driven app for customer service. They need to ensure that only agents in the 'Premium Support' role can see a custom field named 'SLA Level'. What is the best way to implement this security requirement?
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
✓
Configure field-level security in Microsoft Dataverse
Field-level security in Microsoft Dataverse allows administrators to restrict access to a specific field based on security roles. This ensures only agents in the 'Premium Support' role can see the 'SLA Level' field. Option A is incorrect because removing the field from the form would affect all users. Option B is not a standard security feature; Canvas apps are not designed for field-level permissions in model-driven apps. Option D is incorrect because a business rule can only make a field read-only, but it cannot hide the field from specific roles.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Remove the field from the form and create a separate form for Premium Support agents
Why it's wrong here
Removing the field from a form only hides it in that interface; the column remains readable via views, APIs and advanced find. It is tempting because form customisation is the usual way to tailor layouts, but field-level security is the mechanism that restricts column access by role.
- ✗
Use the 'Visible' property of the field in a Canvas app embedded in the model-driven app
Why it's wrong here
A Canvas app's Visible property controls rendering only within that app; the column stays readable through model-driven views, grids and the Web API. It is tempting because conditional visibility is a familiar pattern, but it does not enforce column-level security across the platform.
- ✓
Configure field-level security in Microsoft Dataverse
Why this is correct
Field-level security in Microsoft Dataverse restricts individual column access by user or team, satisfying the requirement that only Premium Support agents view 'SLA Level'. Column permissions are granted through field security profiles, which override table-level privileges, so other roles retain access to the record yet cannot read or update that specific field.
- ✗
Create a business rule that sets the field as read-only for non-Premium roles
Why it's wrong here
A business rule setting read-only still displays the field and its value to all users; it restricts editing, not visibility. It is tempting because business rules are the standard tool for field behaviour, but field-level security is what actually hides a column from roles lacking permission.
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.