Describe Dynamics 365 Customer Insights →mediumMultiple ChoiceObjective-mapped

MB-910 Describe Dynamics 365 Customer Insights Practice Question

Exhibit

Refer to the exhibit.

```json
{
  "name": "CustomerUnificationRule",
  "entities": ["OnlineSales", "LoyaltyData"],
  "matchConditions": [
    {
      "field": "Email",
      "operator": "exact",
      "weight": 1.0
    },
    {
      "field": "Phone",
      "operator": "fuzzy",
      "weight": 0.8
    }
  ],
  "deduplication": "enabled",
  "output": "UnifiedCustomerProfile"
}
```

A company has configured a data unification rule as shown in the exhibit. After running the process, they find that customers with the same email but different phone numbers are not being merged. What is the most likely reason?

⚠ Common exam trap

Test-takers frequently assume 'exact match' means visually identical, but Microsoft tests the nuance that exact matching in Customer Insights is literal byte-level comparison, so invisible characters like spaces break the match.

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 Email field values contain slight differences like leading/trailing spaces

Leading or trailing spaces in the Email field cause exact match comparisons to fail, even though the values appear identical visually. Customer Insights data unification rules use exact matching by default unless fuzzy matching is explicitly configured, so any whitespace discrepancy prevents the rule from recognizing duplicate records. Trimming or normalizing the Email field before matching would resolve this issue.

Answer analysis

Option-by-option breakdown

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

✗
Deduplication is not enabled for the rule
Why it's wrong here
The exhibit shows deduplication is enabled.
✗
The fuzzy match on Phone is overriding the exact match on Email
Why it's wrong here
Fuzzy match on Phone does not override exact match on Email; they are combined.
✓
The Email field values contain slight differences like leading/trailing spaces
Why this is correct
Exact match requires identical values; spaces or case differences can prevent matching.
✗
The output entity is not correctly configured
Why it's wrong here
The output entity is specified and likely correct.

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