Examkin

Question

Difficulty: MediumRole Hierarchy and Sharing Rules

Vanguard Commercial Real Estate uses a custom object named Property_Lease__c to manage leasing agreements. The Organization-Wide Default (OWD) for Property_Lease__c is set to Private. To prevent intermediate managers from automatically inheriting access to records owned by subordinate leasing agents, the administrator deselects the 'Grant Access Using Hierarchies' option on the Property_Lease__c object. However, executive directors still require Read-Only visibility into all lease agreements owned by agents assigned to the East Coast Leasing role. Which configuration should the system administrator implement to satisfy this security requirement?

  1. Create an owner-based sharing rule that shares Property_Lease__c records owned by members of the East Coast Leasing role with users in the Executive Directors role with Read-Only access.Answer
  2. B
    Re-enable the 'Grant Access Using Hierarchies' setting on the Property_Lease__c custom object so access automatically propagates up the role hierarchy.
  3. C
    Assign a permission set with the 'View All' object permission for Property_Lease__c to users in the Executive Directors role.
  4. D
    Change the Organization-Wide Default (OWD) setting for Property_Lease__c from Private to Public Read-Only.

Answer

Create an owner-based sharing rule that shares Property_Lease__c records owned by members of the East Coast Leasing role with users in the Executive Directors role with Read-Only access.
When 'Grant Access Using Hierarchies' is deselected for a custom object, vertical record access propagation up the role hierarchy is disabled. To grant access to a specific group of users (Executive Directors) for records owned by another specific group (East Coast Leasing), an owner-based sharing rule is the precise configuration required. It selectively opens up access without altering OWD or re-enabling hierarchy inheritance for intermediate managers.

Step-by-Step Solution

1
Analyze the Organization-Wide Default (OWD) baseline and custom hierarchy setting.
The baseline OWD is Private, and 'Grant Access Using Hierarchies' is disabled for Property_Lease__c, meaning automatic vertical access up the role hierarchy is turned off.
Disabling hierarchy access ensures intermediate managers above leasing agents do not inherit record access.
2
Determine the targeted sharing mechanism needed.
Selective Read-Only access is needed specifically for executive directors for records owned by the East Coast Leasing role.
Owner-based sharing rules allow admins to share records owned by members of a specific role with another designated role.
3
Evaluate why alternative administrative sharing tools are unsuitable.
Permission set 'View All' grants org-wide access across all owners, OWD Public Read-Only exposes records to all users, and re-enabling hierarchy access breaks the manager restriction constraint.
Only an owner-based sharing rule satisfies the exact target criteria under the principle of least privilege.

Key Concept

Owner-based Sharing Rules vs. Role Hierarchy Access Control
Estimated Time:1m 30s
Rate this question

Topics

Role Hierarchy and Sharing Rules

More questions from this topic