The correct answer is to configure a field security profile for the Priority field and grant read-only access to other roles. This works because field-level security in model-driven apps with Dataverse allows administrators to restrict write access to sensitive fields at a granular level, overriding the default permissions granted by a user’s security role. On the Microsoft Power Platform Fundamentals PL-900 exam, this question tests your understanding of the difference between entity-level security roles and field-level security profiles—a common trap is confusing business rules (which apply universally) with field-level restrictions. Remember that field security profiles are the only way to lock down a specific field like Priority for certain roles while leaving it editable for others, such as Service Managers. A helpful memory tip: think of field security as a “fine-grained lock” on a single column, whereas a security role is the “front door” to the entire table.
PL-900 Demonstrate the capabilities of Power Apps Practice Question
This PL-900 practice question tests your understanding of demonstrate the capabilities of power apps. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A business analyst creates a model-driven app to manage customer service cases. The app includes a custom form with a field called 'Priority' that has three options: Low, Medium, High. The analyst wants to ensure that only users in the 'Service Managers' security role can change the priority of a case. What should the analyst do?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure a field security profile for the Priority field and grant read-only access to other roles.
Option B is correct because field-level security profiles allow restricting write access to specific fields based on user roles. Option A is wrong because business rules apply to all users. Option C is wrong because the security role itself controls entity-level access, not field-level. Option D is wrong because the custom field's properties do not include role-based restrictions.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Configure a field security profile for the Priority field and grant read-only access to other roles.
Why this is correct
Field security profiles control read and write access per field per role.
Related concept
Authentication checks who the user is.
✗
Edit the Service Manager security role to include write privileges for the Case entity.
Why it's wrong here
Entity-level privileges do not restrict specific fields.
✗
Set the Priority field to 'Read-Only' in the form editor.
Why it's wrong here
Form settings are not security controls and can be bypassed.
✗
Create a business rule to hide the field when the user is not a Service Manager.
Why it's wrong here
Business rules run on the form but do not enforce server-side security.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
Authentication checks who the user is.
Authorization controls what the user is allowed to do after login.
Privilege levels affect access to EXEC and configuration commands.
AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
→Do not assume successful login means full administrative access.
→Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
→Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related PL-900 questions on access control and AAA configuration.
Demonstrate the capabilities of Power Apps — This question tests Demonstrate the capabilities of Power Apps — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Configure a field security profile for the Priority field and grant read-only access to other roles. — Option B is correct because field-level security profiles allow restricting write access to specific fields based on user roles. Option A is wrong because business rules apply to all users. Option C is wrong because the security role itself controls entity-level access, not field-level. Option D is wrong because the custom field's properties do not include role-based restrictions.
What should I do if I get this PL-900 question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related PL-900 questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.