Master the Salesforce Certified Data Architect (WI24) Data-Architect Exam with Confidence!

Analytics/BI Owners and Data Domain Stewards are appropriate roles as members of a team that makes decisions on enterprise-wide data governance. Analytics/BI Owners are responsible for defining the business requirements and metrics for data analysis and reporting, and Data Domain Stewards are responsible for defining and enforcing the data quality standards and rules for specific data domains. Salesforce Administrators and Operational Data Users are not suitable roles for this team, as they are more focused on the operational aspects of data management, such as configuration, maintenance, and usage.

 According to the How to avoid row lock or race condition in Apex blog post, one of the ways to prevent race condition in Apex is to use the FOR UPDATE keyword in SOQL statements. The blog post states that “We need to lock the records on which we are working such that other batches or threads will not be having any effect on them. How can we lock a record, then? We need to make use of FOR UPDATE keyword in the SOQL query.” Therefore, a data architect should recommend this solution to guarantee that records are not being updated at the same time by different processes.

Persistence is the data pattern that will allow a data architect to satisfy the requirements, while also keeping limits in mind. Persistence means storing data from external sources in Salesforce objects, either standard or custom. This allows you to access the data within Salesforce and use it for reporting, analytics, workflows, and other features. Persistence also helps you avoid hitting API limits or performance issues when accessing large volumes of data from external systems. You can use various tools such as Data Loader, Bulk API, or Platform Events to persist IoT data from connected devices to a cloud database in Salesforce.

To capture and report on any changes made to ten text fields on the Contact object for the past 3 months, the data architect should write an Apex trigger on Contact after insert and after update events and store the old values in another custom object, or turn on field Contact object history tracking for these ten fields and create reports on contact history. An Apex trigger can capture the old and new values of the fields, as well as the user and time of the change, and store them in a custom object that can be used for reporting. Field history tracking can also track the changes to the fields and store them in a history table that can be used for reporting. However, field history tracking only retains data for up to 18 months or 24 months with an extension, so it may not be suitable for longer-term reporting needs. The other options are not feasible or effective for capturing and reporting on field data changes.

 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.

Pre-processing the data means transforming and cleansing the data before loading it into Salesforce. This can reduce the errors and conflicts that might occur during the data load. Using Data Loader with SOAP API to upsert with zip compression enabled can also improve the performance and efficiency of the data load by reducing the network bandwidth and avoiding duplication

To allow only the owner of a contact record to delete that contact, the data architect should create a “before delete” trigger to check if the current user is not the owner. The trigger can use the UserInfo.getUserId() method to get the current user’s ID and compare it with the OwnerId field of the contact record. If they are not equal, the trigger can add an error to the record and prevent it from being deleted. The other options are not suitable for meeting the requirements, as they would either restrict the edit access or delete access for all users, regardless of ownership.

Changing the opportunity amount field access to read only for sales users using field level security is the best way to address the overriding issue. This way, the sales users can still view the opportunity amount field but cannot edit it, and PPS can update it as the trusted source

A required Lookup relationship ensures that the Shipment record must have a value for each of the three parent records, and also prevents the deletion of those parent records if they are referenced by a Shipment record. A Master-Detail relationship would not allow separate sharing models for each custom object, and a VLOOKUP formula field would not enforce the relationship or prevent deletion

The correct answer is A, B, and D. To maintain the relationship hierarchy during migration, a data architect should use data loader to export the data from source org and then import or upsert into the target org in sequential order, create an external ID field for each object in the target org and map source record IDs to this field, and replace source record IDs with new record IDs from the target org in the import file. These steps will ensure that the records are linked correctly and the relationships are preserved. Option C is incorrect because redefining the master detail relationship fields to lookup relationship fields in the target org will change the behavior and security of the data model. Option E is incorrect because keeping the relationship fields populated with the source record IDs in the import file will cause errors and prevent the records from being imported.