Which two points should an Architect consider in this situation?

Universal Containers (UC) operates worldwide with offices in more than 100 regions in 10 different countries role hierarchy to control data visibility. In the new fiscal year, UC is planned to reorganize the roles and reassign accounts owners.

Which two points should an Architect consider in this situation? Choose 2 answers
A . Using a temporary parking lot account to improve performance.
B . Changing complex role hierarchy can cause a high level of sharing recalculation.
C . Restricting the organization-sharing configurations to private.
D . Replacing Account records ownerships massively can cause data skew.

View Answer

Answer: B,D

Explanation:

Changing the role hierarchy and reassigning account owners can have a significant impact on the data visibility and performance of Salesforce.

An architect should consider the following points in this situation:

Changing complex role hierarchy can cause a high level of sharing recalculation. Depending on the sharing settings, roles can control the level of visibility that users have into the Salesforce data. Users at any given role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy, unless the sharing model for an object specifies otherwise. When the role hierarchy is changed, Salesforce must recalculate the sharing rules and group membership for all the affected users and records, which can take a long time and consume a lot of system resources. Therefore, changing a complex role hierarchy should be done carefully and preferably during off-peak hours1.

Replacing account records ownerships massively can cause data skew. Data skew occurs when more than 10,000 child records are related to the same parent record, or more than 10,000 records of any object are owned by a single user. This can cause performance issues, such as locking, timeouts, and failures, when updating or sharing those records. When account owners are reassigned massively, it can create or worsen data skew, especially if the accounts have many child records, such as contacts and opportunities. Therefore, replacing account records ownerships massively should be avoided or minimized23.

Reference:

: [Design Your Data Model Unit | Salesforce Trailhead]

: [Data Skew in Salesforce – Why it Matters | Salesforce Ben]

: [Ownership Data Skew | Designing Record Access for Enterprise Scale | Salesforce Developers]