The correct answer is D, creating a custom role with record-level security and configuring sharing to restrict record visibility for doctors in a model-driven app. This approach works because record-level security in Dataverse allows you to define granular permissions on specific rows in a table, such as limiting access to only those appointments where the doctor is the owner or related user via the Doctor lookup field. On the Microsoft Power Platform Fundamentals PL-900 exam, this scenario tests your understanding of how to apply security concepts to real-world data access requirements, often appearing as a trap where options like sharing the app or using field-level security seem plausible but fail to filter which records a user can see. A common mistake is confusing field-level security, which hides columns, with record-level security, which controls row visibility. Memory tip: think “row-level” for “who sees which rows,” and remember that sharing the app only grants access to the app itself, not to specific data.
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. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
You are building a model-driven app for a healthcare organization to manage patient appointments. The app uses a Dataverse table 'Appointments' with columns: Patient (lookup to Contact), Doctor (lookup to User), AppointmentDate, Status (Scheduled, Completed, Cancelled). You need to ensure that doctors cannot view appointments of other doctors. Doctors belong to a security role 'Doctor'. Which approach should you use? A) Create a team with all doctors and share the app with the team. B) Configure field-level security to hide the Doctor field. C) Use hierarchy security to limit access based on the Doctor field. D) Create a custom role with record-level security and configure sharing to only allow doctors to see their own appointments.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a custom role with record-level security and configure sharing to only allow doctors to see their own appointments.
Option D is correct because record-level security can be configured to restrict access to records where the doctor is the owner or related user. Option A: Sharing the app does not restrict data visibility. Option B: Field-level security hides fields but does not filter records. Option C: Hierarchy security is for manager-subordinate relationships, not for this scenario.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
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 field-level security to hide the Doctor field.
Why it's wrong here
Field-level security hides the field but does not filter records.
✓
Create a custom role with record-level security and configure sharing to only allow doctors to see their own appointments.
Why this is correct
Record-level security can restrict access to records where the user is the owner or a related user.
Related concept
Static NAT maps one inside address to one outside address.
✗
Create a team with all doctors and share the app with the team.
Why it's wrong here
Sharing the app does not control data access; all team members would see all records.
✗
Use hierarchy security to limit access based on the Doctor field.
Why it's wrong here
Hierarchy security is for reporting relationships, not for record ownership.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
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 the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related PL-900 NAT questions on configuration and troubleshooting.
Demonstrate the capabilities of Power Apps — This question tests Demonstrate the capabilities of Power Apps — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Create a custom role with record-level security and configure sharing to only allow doctors to see their own appointments. — Option D is correct because record-level security can be configured to restrict access to records where the doctor is the owner or related user. Option A: Sharing the app does not restrict data visibility. Option B: Field-level security hides fields but does not filter records. Option C: Hierarchy security is for manager-subordinate relationships, not for this scenario.
What should I do if I get this PL-900 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related PL-900 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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.