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

A dummy user at Universal Containers owns more that 10,000 lead records. The system assigned all these leads to a dummy user. This is causing performance issues whenever role hierarchy changes. Which two options should be recommended to improve performance? Choose 2 answers.

Full set: 212 questions
Answer options
A: Assign​​ownership​​to​​a​​small​​number​​of​​users. Correct answer
B: Add the dummy user into a public group.
C: Add the dummy user to the bottom of the role hierarchy.
D: Do​​not​​assign​​a​​role​​to​​the​​dummy​​user. ​ Correct answer
Correct Answer:
A. Assign​​ownership​​to​​a​​small​​number​​of​​users.; D. Do​​not​​assign​​a​​role​​to​​the​​dummy​​user. ​
Explanation

This scenario describes ownership data skew, where a single user owns a vast number of records, causing performance degradation during sharing recalculations triggered by role hierarchy changes. The two primary strategies to mitigate this are to remove the skewed owner from processing and to reduce the skew itself. Not assigning a role to the dummy user (D) removes them from the role hierarchy, so their records are not processed during hierarchy-based sharing recalculations. Additionally, distributing the records among multiple users (A) reduces the concentration of ownership, minimizing the impact of any single user's records on performance.

Why Incorrect

B. Adding the user to a public group is for sharing records to a set of users; it does not resolve performance issues related to record ownership.
C. Placing the user at the bottom of the hierarchy helps but is less effective than removing the role entirely, as they are still part of the hierarchy.

References

1. Salesforce Architects. (2022). Designing Record Access for Enterprise Scale. Section: "Data Skew". "Ownership skew... To mitigate this, don’t assign the user to a role. If the user requires a role, place them in a separate role at the top of the hierarchy... Also, distribute records as evenly as possible across the owners."

2. Salesforce Help. (2023). Record-Level Access: Under the Hood. "To avoid performance issues with role hierarchy changes, don't assign a role to users that own a large number of records (for example, more than 10,000)."

3. Salesforce Trust. (2021). Best Practices for Deployments with Large Data Volumes. Section: "Record Ownership". "Distribute ownership of records across as many users as possible... For integration users or other users who own a large number of records, do not assign them a role in the role hierarchy."

Scroll to Top