Salesforce Certified Data Architect Practice Test - Questions Answers

Enabling ''Set Audit Fields'' allows the user loading the data to set the value of the standard CreatedDate field to match the original date from the legacy system. This is a one-time permission that can be revoked after the migration is completed.The other options would either not work or require additional customization

Creating a trigger on Contact and adding an error to the record with a custom label allows the architect to use the translation workbench to translate the error message based on the user's language. Creating a validation rule and translating the error message with translation workbench also achieves the same result.The other options would either not provide translation functionality or not display an error message

Custom metadata records are deployable using packages, which makes them easier to migrate from one environment to another. Custom settings records are not deployable using packages, and they are copied from production to sandbox. Custom metadata types are not available for reporting, and custom metadata records are not editable in Apex.

Creating a custom object related to the Invoice object with a picklist field for the Type allows the architect to categorize the attachments and report on them by Type. The standard Attachment object does not have a ContentType picklist field, and adding a custom picklist field to it would not be best practice.

When denormalizing a data model into a single object with a picklist field, the data architect should consider the Bulk API limitations on picklist fields and the standard list view in-line editing.The Bulk API has a limit of 1,000 distinct picklist values per file1, which could be an issue if there are more than 1,000 venues in the future.The standard list view in-line editing allows users to edit multiple records at once, which could introduce data quality issues if the venue picklist is not validated or restricted2. The other options are not relevant to denormalizing a data model.

To improve the performance of SOQL queries that retrieve data from the Order_c object, the data architect should work with Salesforce Support to enable Skinny Tables and make the queries more selective using indexed fields.Skinny Tables are custom tables that contain frequently used fields and are kept in sync with the base tables3. They can improve performance by reducing the number of table joins and using indexes.Making the queries more selective using indexed fields can also improve performance by reducing the query execution time and avoiding query timeouts4. The other options are not effective or recommended for improving SOQL performance.

To improve data quality and avoid data skew, the data architect should create a picklist field with values sorted alphabetically for tracking shipping status on opportunity. A picklist field ensures that only valid values are entered and prevents typos or variations in spelling. Sorting the values alphabetically makes it easier for users to find and select the correct value. Data skew occurs when a large number of records are owned by a single user or have a single value for a field. Creating a picklist field with a limited number of values does not cause data skew, as long as the distribution of values is balanced and not skewed towards one value.

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.

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.