Examkin

Question

Difficulty: HardOrganization-Wide Defaults (OWD)

An administrator at a security firm is configuring record-level access for a custom object named Vendor_Audit__c and evaluating default access behaviors across standard and custom objects. The compliance team requires that records be kept confidential by default, while allowing management access control flexibility. Which of the following statements correctly describe Organization-Wide Default (OWD) capabilities and security principles for this scenario? (Select TWO choices.)

  1. Setting the Organization-Wide Default for Vendor_Audit__c to Private establishes the baseline access, ensuring users cannot view records owned by others unless granted access through hierarchy or sharing.Answer
  2. Disabling 'Grant Access Using Hierarchies' is configurable for custom objects like Vendor_Audit__c, whereas standard objects always enforce access propagation up the role hierarchy.Answer
  3. C
    Modifying Profile object permissions to remove Read access is the recommended approach to restrict record-level visibility for specific users while keeping OWD set to Public Read/Write.
  4. D
    Enabling 'Grant Access Using Hierarchies' on a custom object grants record access strictly to direct managers, preventing higher-level roles in the hierarchy branch from inheriting access.

Answer

The correct statements are that setting OWD to Private establishes the default record-level baseline access, and that 'Grant Access Using Hierarchies' can be disabled for custom objects but is mandatory for standard objects.
Setting OWD to Private ensures records are inaccessible by default to non-owners, establishing the foundational record security baseline. Additionally, custom objects provide the administrative flexibility to uncheck 'Grant Access Using Hierarchies', whereas standard objects mandate hierarchy access propagation.

Step-by-Step Solution

1
Evaluate baseline record visibility requirements.
Setting Organization-Wide Defaults (OWD) to Private restricts record visibility so that users cannot see records owned by others unless explicitly granted access.
OWD is the only mechanism in Salesforce that sets the baseline record-level access across the organization.
2
Analyze Role Hierarchy inheritance differences between custom and standard objects.
Custom objects allow administrators to deselect 'Grant Access Using Hierarchies', whereas standard objects enforce hierarchy access automatically and cannot be disabled.
Salesforce architecture allows flexibility for custom objects while locking mandatory hierarchy inheritance for standard objects.
3
Identify misconceptions regarding profiles and hierarchy depth.
Profiles manage broad object permissions rather than record-level visibility, and hierarchy grants extend to all superior roles above the owner in the hierarchy branch.
Understanding the separation of Object-Level Security (Profiles/Permission Sets) and Record-Level Security (OWD/Sharing) is essential to proper security configuration.

Key Concept

Organization-Wide Defaults (OWD) set the baseline record access in Salesforce. Profiles/Permission Sets grant object-level access (CRUD) but cannot restrict record access below OWD. Furthermore, 'Grant Access Using Hierarchies' can only be disabled on custom objects.
Rate this question

Topics

Organization-Wide Defaults (OWD)

More questions from this topic