DATA-ARCHITECT practice question 3 of 35
Universal Containers (UC) has lead assignment rules to assign leads to owners. Leads not routed by assignment rules are assigned to a dummy user. Sales rep are complaining of high load times and issues with accessing leads assigned to the dummy user. What should a data architect recommend to solve these performance issues?
Full set: 257 questionsThe scenario describes ownership data skew, where a single user owns a very large number of records (over 10,000). This concentration of ownership causes performance degradation during record access and sharing recalculations. The most effective solution is to distribute the ownership of these records across multiple "dummy" users. This reduces the number of records per owner, breaking up the skew and alleviating the performance bottleneck associated with the single, overloaded user. This approach directly targets the root cause of the problem.
A. Assign dummy user last role in role hierarchy: This does not resolve ownership skew, as the performance issue is tied to the number of records owned, not the user's position in the hierarchy.
C. Assign dummy user to highest role in role hierarchy: This would likely worsen performance by increasing the scope of sharing calculations for all users below this role.
D. Periodically delete leads to reduce number of leads: This is a data lifecycle strategy, not a solution for ownership skew. The core issue is the concentration of ownership, not the total record count.
1. Salesforce Architects, Architect's Guide to Record-Level Data Security. "Data Skew," p. 13. "Ownership skew is when a single user owns a very large number of records... To avoid ownership skew, make sure that no user owns more than 10,000 records." The guide recommends distributing records among multiple owners.
2. Salesforce Developer Documentation, Bulk API Developer Guide. "Locking and Performance," Section: "Record Locking Cheat Sheet". The guide discusses how large numbers of child records associated with a single parent can cause lock contention, a principle that extends to ownership where the owner is analogous to the parent in sharing calculations. Distributing ownership mitigates this.
3. Salesforce Help, Best Practices for Deployments with Large Data Volumes. "Designing Your Data Model," Section: "Data Skew". This document explains the different types of data skew, including ownership skew, and its performance implications. It recommends strategies like creating a pool of owners to distribute records.
Keep practicing
Take the free DATA-ARCHITECT practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other DATA-ARCHITECT practice questions
- Question 1Which three characteristics of a skinny table help improve report and query performance?
- Question 2Universal Containers (UC) has built a custom application on Salesforce to help track ship…
- Question 4Universal Container (UC) has accumulated data over years and has never deleted data from …
- Question 5Universals Containers’ system administrators have been complaining that they are not able…
- Question 6Universal Containers is experiencing frequent and persistent group membership locking iss…
- Question 7Universal container (UC) would like to build a Human resources application on Salesforce …
