Valid Sharing-and-Visibility-Architect Dumps shared by ExamDiscuss.com for Helping Passing Sharing-and-Visibility-Architect Exam! ExamDiscuss.com now offer the newest Sharing-and-Visibility-Architect exam dumps, the ExamDiscuss.com Sharing-and-Visibility-Architect exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com Sharing-and-Visibility-Architect dumps with Test Engine here:
Universal Containers (UC) has a partner community for its 200 distributors. UC customer accounts are assigned an individual distributor. The organization-wide default setting for the custom Delivery object is Private. How should an architect advise UC to grant all users at a distributor access to delivery records for all customers assigned to a particular distributor?
Correct Answer: C
Recent Comments (The most recent comments are at the top.)
test - Dec 02, 2025
**Correct Answer: C. Create a Sharing Set for the Distributor profile to grant access to the Delivery object.**
---
### **Explanation**
UC is using a **Partner Community** with **multiple users per distributor**, and the Delivery object is **OWD = Private**.
Because **each distributor is assigned to specific customer accounts**, and UC wants **all users at that distributor** to access the Delivery records for the customers they own, the correct tool is:
### ✅ **Sharing Sets**
Sharing Sets allow Customer Community and Partner Community users to automatically gain access to records **based on their Account or Contact**, without having to create roles or complex rules.
If the Delivery object has a lookup to **Account** (the customer), then a Sharing Set can grant access to all Delivery records where:
* **Delivery.Account = User.Account**
This automatically gives all users under a distributor’s partner account access to those Delivery records.
---
### Why the other choices are incorrect:
#### **A. Public Groups & Sharing Rules**
Sharing rules for *external users* (community users) **do not work with Public Groups**. Public Groups are for internal users only.
#### **B. Role Hierarchy Sharing**
Partner Community users **do not get full hierarchical inheritance**, and using roles for 200 distributors would create complexity and performance issues.
---
### ✔️ Best Recommendation:
**C. Create a Sharing Set for the Distributor profile to grant access to the Delivery object.**...
Recent Comments (The most recent comments are at the top.)
**Correct Answer: C. Create a Sharing Set for the Distributor profile to grant access to the Delivery object.**
---
### **Explanation**
UC is using a **Partner Community** with **multiple users per distributor**, and the Delivery object is **OWD = Private**.
Because **each distributor is assigned to specific customer accounts**, and UC wants **all users at that distributor** to access the Delivery records for the customers they own, the correct tool is:
### ✅ **Sharing Sets**
Sharing Sets allow Customer Community and Partner Community users to automatically gain access to records **based on their Account or Contact**, without having to create roles or complex rules.
If the Delivery object has a lookup to **Account** (the customer), then a Sharing Set can grant access to all Delivery records where:
* **Delivery.Account = User.Account**
This automatically gives all users under a distributor’s partner account access to those Delivery records.
---
### Why the other choices are incorrect:
#### **A. Public Groups & Sharing Rules**
Sharing rules for *external users* (community users) **do not work with Public Groups**.
Public Groups are for internal users only.
#### **B. Role Hierarchy Sharing**
Partner Community users **do not get full hierarchical inheritance**, and using roles for 200 distributors would create complexity and performance issues.
---
### ✔️ Best Recommendation:
**C. Create a Sharing Set for the Distributor profile to grant access to the Delivery object.**...