Salesforce Updated Data-Architect Exam Questions and Answers by kajus

According to the Salesforce documentation2, duplicate leads are leads that have the same or similar information as other leads in Salesforce. Duplicate leads can cause poor customer experience, higher costs, and inaccurate reporting. To mitigate the issues caused by duplicate leads, some of the recommended practices are:

Standardize lead information across all channels (option B). This means using consistent formats, values, and fields for capturing lead data from different sources, such as web forms, email campaigns, or third-party vendors. This can help reduce data quality issues and make it easier to identify and prevent duplicate leads.

Implement a third-party solution to clean and enrich lead data (option D). This means using an external service or tool that can validate, correct, update, and enhance lead data before or after importing it into Salesforce. This can help improve data quality and accuracy, and reduce duplicate leads.

Implement a de-duplication strategy to prevent duplicate leads (option E). This means using Salesforce features or custom solutions that can detect and block duplicate leads from being created or imported into Salesforce. For example, using Data.com Duplicate Management3, which allows defining matching rules and duplicate rules for leads and other objects.

Building a process to manually search and merge duplicates (option A) is not a good practice, as it can be time-consuming, error-prone, and inefficient. Building a custom solution to identify and merge duplicate leads (option C) is also not a good practice, as it can be complex, costly, and difficult to maintain. It is better to use existing Salesforce features or third-party solutions that can handle duplicate leads more effectively.

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 help uniquely identify customer across multiple systems, a data architect should recommend creating a custom field as external ID to maintain the customer ID from the MDM solution. An external ID is a custom field that has the “External ID” attribute enabled, which means that it contains unique record identifiers from a system outside of Salesforce. By using the customer ID from the MDM solution as an external ID in Salesforce CRM, Contract Management system, and Marketing solution, the data architect can ensure that each customer can be easily identified and integrated across these systems. Option A is incorrect because storing the Salesforce ID in all the solutions to identify the customer will not work if the customer records are created or updated in other systems besides Salesforce CRM. Option B is incorrect because creating a custom object that will serve as a cross reference for the customer ID will require additional configuration effort and may not be consistent with the actual customer records in each system. Option C is incorrect because creating a customer database and using this ID in all systems will require additional infrastructure cost and maintenance effort.

Both C and D are valid methods to automatically archive and delete inactive Account data that is older than 3 years1. You can use an ETL tool or the Data Loader to schedule jobs to export and delete data based on certain criteria3. Option A is not recommended because the Force.com Workbench is a web-based tool that does not support scheduling or automation. Option B is not suitable because the weekly export file from the Salesforce UI does not delete data from Salesforce.