A financial services firm tracks compliance evaluations using a custom object named Risk_Assessment__c. The Organization-Wide Default (OWD) for Risk_Assessment__c is set to Private, and Grant Access Using Hierarchies is enabled. The system administrator needs to meet the following access requirements:
1. Compliance Senior Managers must automatically view and edit Risk Assessment records owned by Compliance Officers who report beneath them.
2. External Risk Auditors must have Read access to all Risk Assessment records where the Risk Level picklist field is set to 'High', regardless of record ownership.
Which two administrative actions are required to satisfy these security requirements? (Select 2 answers)
- Rely on the default Role Hierarchy structure, ensuring Compliance Senior Managers occupy roles above Compliance Officers.Answer
- Create a criteria-based sharing rule on Risk_Assessment__c that shares records with Risk Level equal to 'High' with External Risk Auditors.Answer
- CDeselect the 'Grant Access Using Hierarchies' checkbox on the Risk_Assessment__c custom object to isolate record visibility.
- DCreate a new Permission Set with 'View All' object permissions for Risk_Assessment__c and assign it to External Risk Auditors.
Answer
The requirement is met by leveraging the existing Role Hierarchy for manager-subordinate record access and creating a criteria-based sharing rule to grant access to External Risk Auditors based on the Risk Level field value.
Role hierarchy access naturally rolls record access upward to users higher in the role structure when Grant Access Using Hierarchies is enabled. Additionally, criteria-based sharing rules selectively share records based on field values (e.g., Risk Level = 'High') to target groups or roles.
Step-by-Step Solution
Key Concept
Role Hierarchy and Criteria-Based Sharing Rules