Which Actions Build the Least-Privilege Dataverse Security Model?
You are implementing the Dataverse security model for an environment. The environment has two users: User1 and User2. User1 works in the finance department and reports directly to User2. The users must be able to perform the following: • User1: Work only with data relevant to the finance department • User2: Work with the data of direct reports only; requires access to data across multiple departments You need to finalize the security model implementation by using the principle of least privilege at all times. Which three actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Community Insight
The test measures whether you know that manager hierarchy security (depth 1) plus correct business-unit placement delivers the required scoping — the trap is selecting position hierarchy, which the scenario never mentions.
This Dataverse security question asks which three actions deliver least-privilege access for a finance employee (User1) and her cross-department manager (User2). The correct model is a finance business unit for User1 plus manager hierarchy security enabled at depth 1, configured from the Power Platform admin center.
The most common wrong pick is E, enabling position hierarchy with a depth of 2. Position hierarchies grant access based on organizational position levels, not on the direct manager–report relationship described here, and a depth of 2 would expose data of indirect reports, violating least privilege. B is also wrong because reorganizing users' positions does not implement the requested model.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Action A is required because hierarchy security (manager or position) is switched on at the environment level in the Power Platform admin center, under the environment's hierarchy security settings — you cannot finalize the model without going there. Action C is required because User1 must be placed in the finance business unit (limiting her record access to finance-relevant data) while her manager field is set to User2, which is exactly what the manager hierarchy reads. Action D completes the model: enabling manager hierarchy with a depth of 1 means User2 can see only data of her direct reports, precisely matching the stated requirement and never granting access to deeper levels — the essence of least privilege.Why the Other Options Are Wrong
Option E is wrong because the scenario defines access by the manager–report relationship, not by organizational position, and a depth of 2 would let a manager reach indirect reports' data, exceeding the "direct reports only" requirement. Option B is wrong because swapping or repositioning users is a workaround that breaks the real organizational reporting line; the correct fix is to correct User1's manager and business unit values, not to change who reports to whom. Choosing only a subset of A, C, and D would leave hierarchy security disabled or leave User1 in the wrong business unit, so all three are needed.Community Comment Notes
The single community submission selected A, C, and D, explaining "A. Navigate to the Power Platform admin center." and the manager/business-unit and depth-1 hierarchy steps, which matches this analysis. No dissenting comments were posted, so there is no competing viewpoint to reconcile — the vote distribution is likewise unavailable for this item.Official Reference
Exam Strategy
When a Dataverse question names a manager–report chain, default to manager hierarchy security and pick the smallest depth that covers the stated scope (direct reports = depth 1). Always include the environment-level navigation step when hierarchy security must be enabled, and never invent position hierarchies unless the question mentions positions or job roles.
Frequently Asked Questions
Why is position hierarchy with depth 2 (E) wrong for User2's access?
User2's access is defined by direct reports, not by position level. Manager hierarchy at depth 1 limits her to direct reports' data; position hierarchy with depth 2 would grant indirect-report access and break least privilege.
Why must User1's manager and business unit be modified (C)?
The business unit scopes User1 to finance-only data, and the manager field points to User2, which is the link manager hierarchy uses. Without both, the hierarchy has nothing to grant and User1's data remains out of scope.