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

Which three areas should the Architect review in order to increase performance of "Record Access" and "Sharing" calculations? Choose 3 answers.

Full set: 212 questions
Answer options
A: Custom​​Object​​data,​​to​​ensure​​that​​no​​Account​​has​​more​​than​​10,000​​Custom​​Objects​​that​​look​​up​ ​to​​it. Correct answer
B: Opportunity​​data,​​to​​ensure​​that​​no​​Account​​has​​more​​than​​10,000​​Opportunity​​records​​that​​are​ ​related​​to it. Correct answer
C: Record​​ownership,​​to​​ensure​​that​​no​​user​​owns​​more​​than​​10,000​​Object​​records​​in​​the​​system. Correct answer
D: Apex Managed Sharing triggers, to ensure that no trigger is querying more that 10,000 Object records.
Correct Answer:
A. Custom​​Object​​data,​​to​​ensure​​that​​no​​Account​​has​​more​​than​​10,000​​Custom​​Objects​​that​​look​​up​ ​to​​it.; B. Opportunity​​data,​​to​​ensure​​that​​no​​Account​​has​​more​​than​​10,000​​Opportunity​​records​​that​​are​ ​related​​to it.; C. Record​​ownership,​​to​​ensure​​that​​no​​user​​owns​​more​​than​​10,000​​Object​​records​​in​​the​​system.
Explanation

To optimize sharing calculation performance, it's crucial to address data skew. Data skew occurs when a single record owns or is the parent to an excessive number of other records. The three primary types are Account data skew (an Account with over 10,000 contacts, opportunities, or custom object children), Ownership skew (a single user owning over 10,000 records), and Lookup skew (a large number of records looking up to a single record). Reviewing these three areas helps identify and mitigate the root causes of slow record access and sharing recalculations.

Why Incorrect

D. While inefficient Apex can harm performance, the question targets the underlying data structure issues that cause slow "Sharing" calculations, which are best described by data skew (A, B, C), not general Apex query limits.

References

1. Salesforce Architects, Designing Record Access for Enterprise Scale, "Avoid Data Skew", pp. 10-12. This guide details the three main types of data skew: Account Skew, Ownership Skew, and Lookup Skew, and explicitly uses the 10,000 record count as a threshold for performance degradation.

2. Salesforce Help, Record-Level Access: Under the Hood, "The Force.com Record Access Model". This document explains how ownership and parent-child relationships are fundamental to the sharing system and how imbalances (skew) in these areas lead to performance issues.

Scroll to Top