Examkin

Question

Difficulty: HardRole Hierarchy and Sharing Rules

Vanguard Asset Operations utilizes a custom object named `Equipment_Audit__c` to log site safety reviews. The Organization-Wide Default (OWD) for `Equipment_Audit__c` is configured as Private, and the Grant Access Using Hierarchies setting for this custom object was previously deselected by an administrator.

The administrator must now meet two new security requirements:
1. Regional Operations Managers must automatically gain Read/Write access to all `Equipment_Audit__c` records owned by Field Inspectors who report below them in the role hierarchy.
2. Members of the internal Compliance department (organized into the Public Group "Compliance Auditors") must be granted Read-Only access to any `Equipment_Audit__c` record where `Audit_Status__c` equals "Non-Compliant", regardless of record ownership.

Which TWO configuration actions should the administrator take to fulfill these requirements? (Select 2)

  1. Select the 'Grant Access Using Hierarchies' checkbox in Organization-Wide Defaults for the Equipment_Audit__c object.Answer
  2. Create a criteria-based sharing rule on Equipment_Audit__c to grant Read-Only access to the 'Compliance Auditors' Public Group when Audit_Status__c equals 'Non-Compliant'.Answer
  3. C
    Create an owner-based sharing rule on Equipment_Audit__c to share records owned by Field Inspectors with Regional Operations Managers.
  4. D
    Assign a Permission Set containing the 'View All' object permission for Equipment_Audit__c to all Regional Operations Managers.
  5. E
    Change the Organization-Wide Default (OWD) setting for Equipment_Audit__c from Private to Public Read-Only.

Answer

The administrator must select the 'Grant Access Using Hierarchies' checkbox for the Equipment_Audit__c object and create a criteria-based sharing rule targeting records with Audit_Status__c equal to 'Non-Compliant' shared with the 'Compliance Auditors' Public Group.
Selecting the 'Grant Access Using Hierarchies' option for the custom object ensures that users higher in the role hierarchy automatically inherit the access rights of their subordinates. Creating a criteria-based sharing rule allows sharing records based on field values (Audit_Status__c = 'Non-Compliant') with the specified Public Group ('Compliance Auditors'). Together, these two steps address both business requirements securely and efficiently.

Step-by-Step Solution

1
Analyze requirement 1: Regional Operations Managers must access records owned by Field Inspectors below them in the hierarchy.
Recognize that custom objects allow toggling 'Grant Access Using Hierarchies'. When unchecked, managers do not inherit subordinate record access. Checking this setting restores native upward access inheritance.
Grant Access Using Hierarchies is enabled by default for custom objects but can be deselected. Re-enabling it satisfies role hierarchy access propagation cleanly without custom rules.
2
Analyze requirement 2: Compliance department members must access records meeting specific field criteria (Audit_Status__c = 'Non-Compliant').
Determine that access based on record field values requires a criteria-based sharing rule.
Criteria-based sharing rules evaluate record field values (not ownership) to share records matching defined criteria with designated users, roles, or public groups.

Key Concept

Role Hierarchy Access Inheritance and Criteria-Based Sharing Rules
Estimated Time:2m 0s
Rate this question

Topics

Role Hierarchy and Sharing Rules

More questions from this topic