PL-900 Practice Question: Describe the business value of Microsoft Power Platform
An organization plans to deploy a Power Platform solution that uses Dataverse as the data source. They need to ensure that users can only see records from their own department. What should they implement?
⚠ Common exam trap
Candidates often confuse column-level security (which controls field visibility) with record-level security (which controls row visibility), leading them to choose option C when the requirement is about seeing entire records from their own department.
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 units and security roles with team-based access
Business units and security roles with team-based access are the correct implementation because Dataverse uses a hierarchical security model where business units define the organizational structure and security roles control record-level permissions. By configuring business units per department and assigning users to teams within those units, you can enforce that users only see records belonging to their own department through record ownership and sharing rules.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Power Automate to filter records
Why it's wrong here
Power Automate reacts to events and moves data between services; it cannot intercept every Dataverse query to hide rows from a user's view. Power Automate would be correct for triggering notifications or approvals when a record is created, not for row-level read restriction.
- ✗
Audit logging
Why it's wrong here
Audit logging records who accessed or changed records after the fact; it cannot restrict which rows a user retrieves. Audit logging would be correct when the requirement is tracing activity for compliance or investigation, not enforcing department-scoped record visibility.
- ✗
Column-level security profiles
Why it's wrong here
Column-level security profiles restrict which fields a user can read, not which rows; department scoping requires record-level control. Column-level profiles would be correct when users must see a record but be blocked from specific sensitive columns such as salary.
- ✓
Business units and security roles with team-based access
Why this is correct
Business units partition users and records by department, while security roles grant read, write, and delete privileges at that scope. Team-based ownership then shares records within the department, restricting visibility so users see only their own department's data.
Go deeper
Related to this question
About these practice questions
This PL-900 question is part of Courseiva's 701-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.