MB-280 Exam Dumps : Microsoft Dynamics 365 Customer Experience Analyst

Requirement Analysis:

The organization is collecting lead data from two sources: a web form created in Customer Insights - Journeys and manual entries by sales users. This setup could lead to duplicate entries if a lead is submitted through the web form and then entered manually by a sales user afterward.

To ensure data integrity and avoid duplication, it is essential to implement a mechanism that identifies and manages duplicates automatically.

Solution - Enabling Duplicate Detection:

In Dynamics 365, duplicate detection can be configured to alert users or prevent the creation of records that already exist based on certain criteria (such as email).

By enabling duplicate detection based on email addresses, the system will compare incoming lead data with existing records and prompt users if a duplicate is identified. This feature will ensure that leads collected from different sources are not duplicated unnecessarily.

Steps to Enable Duplicate Detection for Leads Based on Email:

Navigate to Settings > Data Management > Duplicate Detection Rules in Dynamics 365.

Create a new Duplicate Detection Rule for the Lead entity. Specify that the system should check for duplicate records based on the email field.

Publish the rule and ensure it is activated.

After activation, this rule will prompt users whenever a duplicate email is detected, either from the Customer Insights - Journeys web form or manual entry by sales users.

Start Auditing:

Enabling Start Auditing is the primary step to activate auditing for Dynamics 365. This setting ensures that changes to data, including field updates on records, are tracked and logged.

Without enabling this checkbox, no data changes will be recorded, as it is the fundamental requirement for auditing across all entities and fields.

To identify duplicate records, you need to configure both duplicate detection rules and duplicate detection jobs.

Since Terra Flora requires identifying duplicate pet records across various fields, creating three duplicate detection rules is likely necessary to cover different columns (such as name, breed, and dietary requirements) in the Pet table.

One duplicate detection job is sufficient to run these rules concurrently, scanning the database for duplicates across the specified columns. This job can be scheduled or run manually.

Option B is correct as it ensures comprehensive coverage with three rules addressing various fields and one job to manage the duplicate detection process.

References from Microsoft Documentation:

For guidance on setting up duplicate detection jobs and rules, refer to Detect duplicate records in Dynamics 365.