Examkin

Question

Difficulty: Very hardOrganization-Wide Defaults (OWD)

Stellar Renewable Systems uses a custom object named Partner_Deal_Registration__c to track sensitive co-selling opportunities submitted by external partners. The corporate compliance team mandates two strict data access requirements for this object:
1. Baseline record access must be completely restricted so that users can only view and edit deal registrations they own or that are explicitly shared with them.
2. Managers and executive leadership must automatically inherit full record access (view and edit) for all deal registrations owned by their direct and indirect subordinates within the role hierarchy.

Which TWO administrative actions must be configured to satisfy these security requirements? (Select TWO answers.)

  1. Set the Default Internal Access for Partner_Deal_Registration__c to Private in Organization-Wide Defaults.Answer
  2. Ensure that the Grant Access Using Hierarchies checkbox remains selected for Partner_Deal_Registration__c.Answer
  3. C
    Set the Default Internal Access for Partner_Deal_Registration__c to Public Read-Only and create a Permission Set to revoke view access for non-owners.
  4. D
    Deselect the Grant Access Using Hierarchies setting for Partner_Deal_Registration__c and configure a Criteria-Based Sharing Rule targeting manager roles.

Answer

The administrator must set the Default Internal Access for Partner_Deal_Registration__c to Private and ensure the Grant Access Using Hierarchies checkbox remains checked on the custom object's sharing settings.
To satisfy the requirements, the administrator must establish Private baseline visibility in Organization-Wide Defaults so non-owners cannot view records by default, and ensure that 'Grant Access Using Hierarchies' remains selected on the custom object so managers in the role hierarchy automatically inherit access to records owned by their subordinates.

Step-by-Step Solution

1
Determine the most restrictive baseline access setting for the object.
Since users must only see records they own or have explicit access to, the Default Internal Access in Organization-Wide Defaults (OWD) must be set to Private.
OWD sets the foundational, most restrictive baseline level of record access across the entire organization.
2
Evaluate role hierarchy propagation requirements for custom objects.
The 'Grant Access Using Hierarchies' checkbox must remain selected for Partner_Deal_Registration__c.
While standard objects always grant access via the role hierarchy, custom objects allow administrators to turn hierarchy access on or off. Enabling it allows superior roles to automatically access subordinate records.
3
Validate against alternative permission models.
Reject methods attempting to restrict public access using profiles or permission sets, as Salesforce security is strictly additive.
Profiles and permission sets grant object-level permissions (CRUD) but cannot override OWD to revoke record-level sharing.

Key Concept

Organization-Wide Defaults (OWD) Baseline and Role Hierarchy Access for Custom Objects
Rate this question

Topics

Organization-Wide Defaults (OWD)

More questions from this topic