SHARING-AND-VISIBILITY-DESIGNER practice question 24 of 30

At Universal Containers, Accounts and Contacts are normally visible to all employees, and Proposals (custom object) are visible to the Account owner…

Full set: 212 questions
At Universal Containers, Accounts and Contacts are normally visible to all employees, and Proposals (custom object) are visible to the Account owner and managers. However, some Proposals are considered confidential and are managed by a Strategic Proposals team. These Proposals should not be visible to anyone in the Sales group other than the owner and the strategic team. How should the architect design for this requirement?
Answer options
A: Proposal Owner set to the Strategic Deals Team Queue and set the Account relationship to Master-Detail.
B: Disable Grant Access Using Hierarchies and set an Owner-Based Sharing rule for Strategic Deals team.
C: Proposal Owner set to the Strategic Deals Team Queue and create an owner-based sharing rule to grant visibility to the Account owner
D: Disable Grant Access Using Hierarchies and set a Criteria-Based Sharing rule for Strategic Deals team. Correct answer
Correct Answer:
D. Disable Grant Access Using Hierarchies and set a Criteria-Based Sharing rule for Strategic Deals team.
Explanation

The core requirement is to prevent managers in the sales hierarchy from viewing specific, confidential Proposal records owned by their subordinates. The standard mechanism for this is to disable 'Grant Access Using Hierarchies' for the Proposal object in the Organization-Wide Defaults. This action stops the automatic upward sharing through the role hierarchy. To then grant access to the Strategic Proposals team, a criteria-based sharing rule is the most effective tool. This rule can identify confidential proposals (e.g., via a checkbox field) and share them with a public group containing the Strategic Proposals team members, regardless of who owns the record.

Why Incorrect

A. A queue is for record ownership, not for sharing access with a specific team. A Master-Detail relationship would make Proposal sharing dependent on the Account, which is public.
B. An owner-based sharing rule shares records owned by members of a specific group/role. The requirement is to share records with the strategic team, irrespective of the owner.
C. Using a queue for ownership is incorrect for this scenario, and an owner-based rule is not the right mechanism to grant access to the strategic team.

References

1. Salesforce Help, Control Who Sees What, "Sharing Rules". This document explains that criteria-based sharing rules are used to grant access to records based on their field values, which is ideal for identifying "confidential" records.

2. Salesforce Help, Organization-Wide Sharing Defaults. This page details the "Grant Access Using Hierarchies" setting and explains that deselecting it for a custom object prevents managers from gaining automatic access to records owned by users below them in the hierarchy.

3. Salesforce Architect's Handbook, Record-Level Security, "Declarative Sharing". This resource contrasts owner-based and criteria-based sharing, highlighting that criteria-based rules are necessary when access depends on record attributes rather than ownership.

Scroll to Top