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:
Universal1 Containers (UC) is a non-profit organization with more than 20,000,000 members (donors). UC decided to assign those accounts to donations reps based on their regions. Donations reps ended up owning more than 50,000 donors each. The donation reps started to see significant degradation of the system performance. What is the reason for this problem?
Correct Answer: C
Recent Comments (The most recent comments are at the top.)
test - Nov 21, 2025
**Correct Answer: C — There is an Account ownership data skew problem.** ✅
### **Explanation**
**Data skew** occurs in Salesforce when **a single user owns a very large number of records**—usually more than 10,000–50,000.
* In this scenario, each donation rep owns **50,000+ donor accounts**. * This causes **performance degradation** because:
* Sharing calculations * Recalculations of record-level security * Roll-up summaries (if any) * Triggers and workflow rules
All of these processes become slower as Salesforce attempts to manage the large number of records owned by a single user.
---
### Why the other options are incorrect:
**A. The donations reps' access to the assigned accounts is wrong**
* Incorrect; access is not the core issue here. Performance degradation is caused by ownership skew, not permission misconfiguration.
* While sharing recalculation can cause temporary performance issues, the root cause here is **ownership data skew**, which triggers frequent sharing calculations automatically.
---
✔ **Correct: C — Account ownership data skew is causing the performance problem.**...
Recent Comments (The most recent comments are at the top.)
**Correct Answer: C — There is an Account ownership data skew problem.** ✅
### **Explanation**
**Data skew** occurs in Salesforce when **a single user owns a very large number of records**—usually more than 10,000–50,000.
* In this scenario, each donation rep owns **50,000+ donor accounts**.
* This causes **performance degradation** because:
* Sharing calculations
* Recalculations of record-level security
* Roll-up summaries (if any)
* Triggers and workflow rules
All of these processes become slower as Salesforce attempts to manage the large number of records owned by a single user.
---
### Why the other options are incorrect:
**A. The donations reps' access to the assigned accounts is wrong**
* Incorrect; access is not the core issue here. Performance degradation is caused by ownership skew, not permission misconfiguration.
**B. Salesforce sharing recalculation kicked off**
* While sharing recalculation can cause temporary performance issues, the root cause here is **ownership data skew**, which triggers frequent sharing calculations automatically.
---
✔ **Correct: C — Account ownership data skew is causing the performance problem.**...