According to the Salesforce documentation 2 , 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 Management 3 , 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.

Option B is correct because putting the business purpose in the Description of each field is a method that an architect can use to trace back configuration changes to the detailed requirements 1 .  The Description of each field provides a brief explanation of what the field is used for and why it is needed 2 .  Option D is correct because using the Force.com IDE to save the metadata files in source control is another method that an architect can use to trace back configuration changes to the detailed requirements 1 .  The Force.com IDE is an integrated development environment that allows developers to work with Salesforce metadata files and Apex code 3 .  Source control is a system that tracks and manages changes to code and configuration files 4 . Option A is not correct because reviewing the setup audit trail for configuration changes is not a method to trace back configuration changes to the detailed requirements, but a way to monitor and audit the changes made in the setup area. Option C is not correct because maintaining a data dictionary with the justification for each field is not a method to trace back configuration changes to the detailed requirements, but a document that provides information about the data entities and attributes in a system.

The recommended course of action to appropriately integrate the new Opportunity engagement system with Salesforce is to bring the stakeholders together to discuss the appropriate data strategy moving forward. This is because there may be valuable data in both systems that need to be reconciled and harmonized, and the Master Data Management (MDM) strategy may need to be revised or updated to accommodate the new system.  The other options are not recommended, as they may result in data loss, inconsistency, or duplication

Leverage an External ID from source system orders to import related order lines. This is the recommended solution because it allows you to use the upsert operation to match records based on the External ID field, which is indexed and unique.  This avoids the need to query the parent order IDs in Salesforce before importing the order line items, which can cause time-out errors or long delays 1 .

The issue that an architect will have when implementing the quarterly accounts receivable report in Salesforce is that Salesforce does not allow more than four objects in a single report type. A report type defines the set of records and fields available to a report based on the relationships between a primary object and up to four related objects. A report type has the following limitations:

It cannot include more than four objects in a single report type, which means that the report cannot compile data from five objects (Accounts, Contacts, Opportunities, Orders, and Order Line Items) at once.

It cannot include objects that are more than two relationships away from each other, which means that the report cannot access fields from Order Line Items through Opportunities and Orders.

It cannot include objects that have a many-to-many relationship with each other, which means that the report cannot access fields from Contacts and Opportunities through the junction object Opportunity Contact Role.

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.

Using an indexed data field with bounded data filters can improve the report performance by making the query more selective and reducing the number of records to scan.  Using formula fields to surface information from related entities on the report can also enhance the report performance by avoiding joins and complex calculations