Describe Dynamics 365 Customer Insights →mediumMultiple ChoiceObjective-mapped

MB-910 Describe Dynamics 365 Customer Insights Practice Question

Exhibit

Refer to the exhibit. The following is a JSON snippet from a Dynamics 365 Customer Insights data unification configuration:
{
  "dataSources": [
    {
      "name": "CRM",
      "entities": ["Contact", "Account"]
    },
    {
      "name": "Loyalty",
      "entities": ["Member", "Transaction"]
    }
  ],
  "matchRules": [
    {
      "matchCondition": "Contact.Email = Member.Email",
      "mergeStrategy": "PriorityBased",
      "priorityOrder": ["CRM", "Loyalty"]
    }
  ]
}

Refer to the exhibit. A customer has configured data unification in Customer Insights. What will happen when a contact from CRM and a member from Loyalty have the same email address?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The CRM contact data will take priority and overwrite Loyalty member data in the unified profile

The merge strategy is PriorityBased with CRM first, so the CRM record takes precedence. Option B is wrong because a new unified profile is not created; instead, the existing CRM profile is enriched with data from the Loyalty record. Option C is wrong because the system automatically resolves matches based on the configured priority, not manual intervention. Option D is wrong because fields are not merged equally; the priority-based strategy means the CRM record's data overwrites the Loyalty member's data in the unified profile.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
The CRM contact data will take priority and overwrite Loyalty member data in the unified profile
Why this is correct
PriorityBased with CRM first means CRM wins.
✗
A new unified profile will be created with a new ID
Why it's wrong here
The unified profile will use the existing records.
✗
The system will prompt the user to manually resolve the match
Why it's wrong here
The configuration automatically applies the priority.
✗
All fields from both records will be merged equally
Why it's wrong here
PriorityBased gives precedence to one source.

Visual reference

Go deeper

MB-910 Describe Dynamics 365 Customer Insights Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question