SHARING-AND-VISIBILITY-ARCHITECT practice question 3 of 15

Universal Containers (UC) operates worldwide, with offices in more than 100 regions in 10 different countries, and has established a very complex Role Hierarchy to control data visibility. In the new fiscal year, UC is planning to reorganize the roles and reassign account owners. Which feature should an architect recommend to avoid problems with this operation?

Full set: 78 questions

Domain Performance and Scalability

Answer options
A: Partition data using Divisions
B: Skinny table
C: Deferred Sharing Recalculation Correct answer
Correct Answer:
C. Deferred Sharing Recalculation
Explanation

A large-scale reorganization of a complex role hierarchy and mass reassignment of record owners will trigger extensive sharing recalculations. This process is resource-intensive and can lead to significant performance degradation and record locking, disrupting business operations. The Deferred Sharing Recalculation feature is designed specifically for this scenario. It allows an administrator to suspend the automatic recalculations, perform all the necessary changes to roles and ownership, and then resume the recalculation process during a planned maintenance window. This minimizes the impact on users and ensures system stability during the transition.

Why Incorrect

A. Partition data using Divisions: Divisions are used to segment large data volumes to improve the performance of reports, list views, and searches, not to manage the impact of a sharing recalculation event.
B. Skinny table: Skinny tables are a performance feature that optimizes read-only operations, such as reports and list views, by creating a custom table with frequently used fields. They do not affect sharing calculation processes.

References

1. Salesforce Architects, Architect's Guide to Record-Level Security, Version 1.1, Page 31, "Managing Recalculations": "When you make changes to roles, territories, or public groups that are used in sharing rules, Salesforce recalculates sharing rules to add or remove access as needed... For large-scale recalculations, you can defer sharing calculations and then schedule the recalculation to run during your organization’s off-peak hours."

2. Salesforce Help, "Defer Sharing Calculations": "To improve performance, you can suspend and resume sharing calculations. Suspending calculations is useful before you create or modify roles, territories, groups, or sharing rules in a way that might initiate a large number of recalculations."

3. Salesforce Help, "What are Divisions?": "Divisions let you segment your organization's data into logical sections, making searches, reports, and list views more meaningful to users. Divisions are useful for organizations with extremely large amounts of data."

4. Salesforce Developer Documentation, "Query & Search Optimization Cheat Sheet": "A skinny table is a custom table in the Force.com platform that contains a subset of fields from a standard or custom base Salesforce object... Salesforce can use skinny tables to return results for reports, list views, and SOQL queries more quickly." This confirms skinny tables are for query performance, not sharing recalculation.

Scroll to Top