Examkin

Question

Difficulty: HardOrganization-Wide Defaults (OWD)

Cloud Kicks tracks performance bonuses using a custom object named Partner_Incentive__c. Management mandates that users must only be able to view and edit records that they own. Additionally, compliance requirements state that managers and executives above record owners in the role hierarchy MUST NOT automatically inherit access to these sensitive record details. Which combination of security configurations should the administrator apply to meet these requirements?

  1. Set Default Internal Access to Private for Partner_Incentive__c and deselect the Grant Access Using Hierarchies checkbox.Answer
  2. B
    Set Default Internal Access to Public Read-Only for Partner_Incentive__c and assign Permission Sets to restrict visibility for managers.
  3. C
    Set Default Internal Access to Private for Partner_Incentive__c and modify manager Profiles to revoke inherited sharing access.
  4. D
    Set Default Internal Access to Private for Partner_Incentive__c and leave Grant Access Using Hierarchies enabled, as custom objects do not propagate private records up the hierarchy.

Answer

Set Default Internal Access to Private for Partner_Incentive__c and deselect the Grant Access Using Hierarchies option.
Setting the Default Internal Access of a custom object to Private restricts record visibility exclusively to record owners and administrators. Because 'Grant Access Using Hierarchies' is enabled by default on custom objects, deselecting this option is required to stop automatic access propagation to users higher in the role hierarchy.

Step-by-Step Solution

1
Determine the baseline record-level access requirement.
Since users must only view and edit records they own, the Organization-Wide Default (OWD) baseline must be set to Private.
OWD is the most restrictive baseline level of data access in Salesforce.
2
Analyze role hierarchy access behavior for custom objects.
By default, Salesforce enables 'Grant Access Using Hierarchies' for all objects, which propagates record access to users above the owner in the role hierarchy.
To prevent managers and executives from automatically seeing Private records owned by direct reports, this feature must be explicitly disabled.
3
Verify custom object administrative capabilities.
For custom objects, administrators can uncheck 'Grant Access Using Hierarchies' in OWD settings (unlike standard objects where it is permanently enabled).
This achieves the strict privacy requirement for higher-level roles.

Key Concept

Organization-Wide Defaults (OWD) and Grant Access Using Hierarchies for Custom Objects
Rate this question

Topics

Organization-Wide Defaults (OWD)

More questions from this topic