Data-Architect Practice Questions

Data integrity and data usability are two aspects of data that an Enterprise data governance program aims to improve. Data integrity refers to the accuracy, consistency, and validity of the data across the enterprise2. Data usability refers to the ease of access, analysis, and interpretation of the data by the end users

According to the Data Modeling unit on Trailhead, some of the key actions that should be done when data modeling in Salesforce are identifying data elements, mapping legacy data, and implementing legacy data model. The unit states that “Before you start creating objects and fields in Salesforce, you need to identify the data elements that you want to store and work with. … Next, you need to map your legacy data to Salesforce objects and fields. … Finally, you need to implement your data model in Salesforce by creating custom objects and fields using declarative tools or Metadata API.” Therefore, these are the correct actions for migrating a legacy client server app to Salesforce.

 According to the Salesforce documentation1, ownership skew occurs when a large number of records (more than 10,000) are owned by a single user or queue. This can cause performance issues and lock contention when multiple users try to access or update those records. To prevent ownership skew, some of the recommended practices are:

Assign a default user as the owner of the records and do not assign any role to the default user (option C). This way, the records will not be visible to other users in the role hierarchy and will not cause sharing recalculations.

Keep users out of public groups that can be used as the source for sharing rules (option B). Sharing rules based on public groups can cause excessive sharing calculations and lock contention when many records are owned by a single user or queue.

Assign a default user as the owner of the records and assign the top most role in the hierarchy to the default user (option E). This way, the records will be visible to all users in the role hierarchy, but will not cause sharing recalculations or lock contention.

Assigning a default user as the owner of the records and assigning a role in the hierarchy (option A) is not a good practice, as it can cause sharing recalculations and lock contention when the role is updated or moved. Assigning “view all” permission on profile to give access to the records (option D) is also not a good practice, as it can bypass the security and sharing model and expose sensitive data to unauthorized users.