Examkin

Soru

Zorluk: OrtaOrganization-Wide Defaults (OWD)

Universal Containers uses a custom object named Contract_Review__c to manage sensitive legal evaluations of enterprise customer agreements. Company policy requires that, by default, contract review records must be restricted so that only the record owner and users higher in the role hierarchy can access them. Additionally, the administrator must grant Read access to regional compliance officers who are outside the record owner's direct management chain. Which TWO configuration actions should the administrator take to satisfy these security requirements?

  1. Set the Organization-Wide Default (OWD) internal access for Contract_Review__c to Private.Cevap
  2. Create criteria-based or owner-based sharing rules to extend Read access to regional compliance officers.Cevap
  3. C
    Set the Organization-Wide Default (OWD) internal access to Public Read-Only and restrict object Read permissions via Profiles for unauthorized users.
  4. D
    Deselect the Grant Access Using Hierarchies option on Contract_Review__c to prevent manager access.

Cevap

The administrator must set the Organization-Wide Default internal access for the custom object to Private and create sharing rules to grant Read access to regional compliance officers.
The correct configuration strategy requires establishing a Private Organization-Wide Default for the custom object to secure records at the baseline level, while relying on default role hierarchy propagation and sharing rules to open up Read access for specific cross-functional teams.

Adım Adım Çözüm

1
Determine the baseline security requirement.
Since record access must be restricted to record owners and their management chain by default, the Organization-Wide Default (OWD) must be set to Private.
Organization-Wide Defaults define the most restrictive baseline access level for all users in the organization.
2
Evaluate role hierarchy behavior.
Ensure Grant Access Using Hierarchies remains enabled for the custom object.
By keeping hierarchy access enabled, users positioned above the owner in the role hierarchy automatically inherit access to owned records.
3
Extend access to lateral or cross-functional teams.
Define criteria-based or owner-based sharing rules targeting regional compliance officers.
Salesforce security principles mandate starting with a restrictive OWD baseline and using sharing rules to open up access to additional roles or public groups.

Anahtar Kavram

Salesforce Sharing Architecture and OWD Baseline Configuration
Bu soruyu puanla

Konular

Organization-Wide Defaults (OWD)

Bu konudan daha fazla soru