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

Universal Containers has the following requirements: * The Commercial Account and Consumer Account support departments should not collaborate.​ * The…

Full set: 212 questions
Universal Containers has the following requirements: * The Commercial Account and Consumer Account support departments should not collaborate.​ * The Commercial and Consumer sales users roll up to the same VP of Sales, but there should be no collaboration between sales departments. * The Commercial sales department should share its customers with the Commercial support department. * The Consumer sales department shares its customers with the Consumer support department.​ * The Commercial and Consumer support departments roll up to the same Support Director.​ * The sales departments will remain the Account Owner for the Accounts that they sell to. What is the recommended Org-Wide Sharing Default for Accounts, and how would the Architect enable proper Commercial and Consumer Sales to Support Account Sharing for this scenario?
Answer options
A: Private Account Sharing with Sharing Rules from Commercial Sales Role(s) to Consumer Support Role(s) and Consumer Sales Role(s) to Commercial Support Role(s).
B: Private Account Sharing with Sharing Rules from Commercial support Role(s) to Commercial Support Role(s) and Consumer Sales Role(s) to Consumer Support Role(s).
C: Read-Only Account Sharing with Sharing Rules from Commercial Sales Role(s) to Consumer Support Group(s) and Consumer Sales Role(s) to Commercial Support Groups(s).
D: Private Account Sharing with Sharing Rules from Commercial Sales Group(s) to Commercial Support Groups(s) and Consumer Sales Group(s) to Consumer Support Group(s). Correct answer
Correct Answer:
D. Private Account Sharing with Sharing Rules from Commercial Sales Group(s) to Commercial Support Groups(s) and Consumer Sales Group(s) to Consumer Support Group(s).
Explanation

The requirement for sales and support departments to be segregated by business line (Commercial vs. Consumer) necessitates a restrictive sharing model. Setting the Organization-Wide Default (OWD) for Accounts to 'Private' is the correct foundation. To enable the required collaboration, sharing rules are needed. Using public groups (e.g., "Commercial Sales," "Commercial Support") is the most flexible and scalable method to group users for sharing, as it is independent of the role hierarchy. Sharing rules can then grant access from the Commercial Sales group to the Commercial Support group, and likewise for Consumer, fulfilling all requirements.

Why Incorrect

A. This option incorrectly proposes sharing across business lines (e.g., Commercial Sales to Consumer Support), which violates the core requirement of no collaboration between departments.
B. This option incorrectly shares from "Commercial support Role(s) to Commercial Support Role(s)," which is redundant and doesn't grant access from Sales to Support as required.
C. A 'Read-Only' OWD is incorrect because the sales departments own the accounts and need to edit them. This option also proposes incorrect cross-departmental sharing.

References

1. Salesforce Security Guide, "Sharing Rules," page 28. This section explains how sharing rules can be used to grant wider access to data for particular groups of users.

2. Salesforce Security Guide, "Organization-Wide Sharing Defaults," page 16. This section details how a Private OWD is the most restrictive setting, upon which a sharing model is built.

3. Salesforce Help, "Public Groups." This document describes public groups as a way to group users for sharing purposes, regardless of their role.

Scroll to Top