Examkin

Soru

Zorluk: OrtaRole Hierarchy and Sharing Rules

Nexus Logistics utilizes a custom object named Shipment_Audit__c with an Organization-Wide Default (OWD) set to Private. The 'Grant Access Using Hierarchies' setting is currently deselected for this object.

The Salesforce Administrator needs to meet the following record access requirements:
1. Regional Operations Managers must have Read access to Shipment Audit records owned by Logistics Coordinators below them in the role hierarchy, but ONLY when the Audit_Status__c field is set to 'Action Required'.
2. The Corporate Compliance team, located in a completely separate branch of the role hierarchy, must have Read/Write access to ALL Shipment Audit records, regardless of record owner or status.

Which TWO configuration steps must the administrator execute to fulfill these requirements? (Select 2 options.)

  1. Create a criteria-based sharing rule on Shipment_Audit__c sharing records where Audit_Status__c equals 'Action Required' with the Regional Operations Manager role.Cevap
  2. Create an owner-based sharing rule on Shipment_Audit__c sharing records owned by All Internal Users with the Corporate Compliance role with Read/Write access.Cevap
  3. C
    Enable the 'Grant Access Using Hierarchies' setting on the Shipment_Audit__c custom object.
  4. D
    Create a Permission Set granting Read and Edit object permissions on Shipment_Audit__c and assign it to the Corporate Compliance users.
  5. E
    Configure a Public Read/Write Organization-Wide Default setting specifically for the Corporate Compliance user profile.

Cevap

The administrator must create a criteria-based sharing rule on Shipment_Audit__c sharing records where Audit_Status__c equals 'Action Required' with the Regional Operations Manager role, and create an owner-based sharing rule sharing records owned by All Internal Users with the Corporate Compliance role with Read/Write access.
The criteria-based sharing rule correctly grants access only to records meeting the specific criteria ('Action Required') to the Regional Operations Manager role. The owner-based sharing rule shares all records owned by internal users with the Corporate Compliance role across hierarchy branches with Read/Write access.

Adım Adım Çözüm

1
Analyze the conditional access requirement for Regional Operations Managers.
Since access depends on a specific field value ('Action Required') rather than unconditional role-hierarchy inheritance, a criteria-based sharing rule targeting the Regional Operations Manager role is required.
Grant Access Using Hierarchies cannot filter records by field criteria.
2
Analyze the broad access requirement for the Corporate Compliance team.
Since Corporate Compliance sits in a separate role hierarchy branch and requires Read/Write access to all records, an owner-based sharing rule sharing records owned by 'All Internal Users' with the Corporate Compliance role must be created.
Role hierarchy alone does not open cross-branch access when OWD is Private.

Anahtar Kavram

Combining criteria-based and owner-based sharing rules to extend access beyond OWD when role hierarchy inheritance is insufficient or conditional.
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

Role Hierarchy and Sharing Rules

Bu konudan daha fazla soru