Describe Dynamics 365 Customer Insights →mediumMultiple ChoiceObjective-mapped

MB-910 Describe Dynamics 365 Customer Insights Practice Question

Exhibit

{
  "matchingRules": [
    {
      "name": "EmailMatch",
      "type": "standard",
      "conditions": [
        {
          "attribute": "email",
          "operator": "exactMatch",
          "confidenceLevel": "high"
        }
      ]
    },
    {
      "name": "NameAndCityMatch",
      "type": "standard",
      "conditions": [
        {
          "attribute": "fullname",
          "operator": "fuzzyMatch",
          "confidenceLevel": "medium"
        },
        {
          "attribute": "city",
          "operator": "exactMatch",
          "confidenceLevel": "medium"
        }
      ]
    }
  ]
}

Refer to the exhibit. You are configuring data matching rules in Dynamics 365 Customer Insights. What will happen if a customer record from the e-commerce source and a record from the CRM have the same email address but different names and cities?

⚠ Common exam trap

Many candidates assume all matching rules must be satisfied for a match to occur, but Dynamics 365 Customer Insights uses an 'OR' logic where any single rule can trigger a match, not an 'AND' logic.

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

✓

They will be matched as duplicates and merged based on the EmailMatch rule

In Dynamics 365 Customer Insights, data matching rules are evaluated independently and the system uses a 'match by any rule' logic. If the EmailMatch rule is configured and a match is found (same email address), the records will be considered duplicates and merged, regardless of other rules like NameAndCityMatch. The other rules only apply if they are the ones that trigger the match; they do not block a match already found by a different rule.

Answer analysis

Option-by-option breakdown

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

✗
They will not be matched because the NameAndCityMatch rule requires fuzzy match on name and exact city
Why it's wrong here
EmailMatch rule applies first.
✗
They will be matched only if the confidence level is set to high on both rules
Why it's wrong here
Each rule independently can cause match.
✗
They will be matched only if both rules are satisfied
Why it's wrong here
Rules are OR conditions.
✓
They will be matched as duplicates and merged based on the EmailMatch rule
Why this is correct
Exact email match triggers merge.

Go deeper

MB-910 Describe Dynamics 365 Customer Insights Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question