Question 271 of 977

Describe Dynamics 365 Customer Insights →mediumMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is that they will be matched as duplicates and merged based on the EmailMatch rule. This happens because Dynamics 365 Customer Insights evaluates data matching rules independently using an "any rule" logic—if the EmailMatch rule finds a match via the same email address, the system considers the records duplicates and merges them, regardless of conflicting data like different names or cities from other rules such as NameAndCityMatch. On the MB-910 exam, this concept tests your understanding that matching rules are not hierarchical; a single matching rule can override mismatches in other fields, which is a common trap where candidates assume all rules must agree. Remember the key principle: "any rule wins"—once one rule finds a match, the merge proceeds. A helpful memory tip is to think of it like a bouncer at a club: if the EmailMatch bouncer says "same email, you're in," the NameAndCityMatch bouncer cannot block the entry.

MB-910 Describe Dynamics 365 Customer Insights Practice Question

This MB-910 practice question tests your understanding of describe dynamics 365 customer insights. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

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?

Question 1mediummultiple choice

Full 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"
        }
      ]
    }
  ]
}

A
They will not be matched because the NameAndCityMatch rule requires fuzzy match on name and exact city
Why wrong: EmailMatch rule applies first.
B
They will be matched only if the confidence level is set to high on both rules
Why wrong: Each rule independently can cause match.
C
They will be matched only if both rules are satisfied
Why wrong: Rules are OR conditions.
D
They will be matched as duplicates and merged based on the EmailMatch rule
Exact email match triggers merge.

Full breakdown with real-world context →

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

Option D is correct because 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.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

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.
Related concept
Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that 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.

Detailed technical explanation

How to think about this question

In Dynamics 365 Customer Insights, data matching uses a 'match by any rule' approach where each rule is evaluated independently. When multiple rules exist, the system checks each rule's conditions; if any rule finds a match (e.g., same email), the records are merged. This is different from a 'match by all rules' logic, which would require all conditions to be true. The merge process uses a deduplication engine that applies survivorship rules to resolve conflicts in attributes like name and city, typically keeping the most recent or highest-confidence value.

KKey Concepts to Remember

Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.

TExam Day Tips

Watch for words such as best, first, most likely and least administrative effort.
Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related MB-910 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Describe Dynamics 365 Customer Insights practice questions

Practise MB-910 questions linked to Describe Dynamics 365 Customer Insights.

Describe Dynamics 365 Sales practice questions

Practise MB-910 questions linked to Describe Dynamics 365 Sales.

Describe Dynamics 365 Customer Service practice questions

Practise MB-910 questions linked to Describe Dynamics 365 Customer Service.

Describe Dynamics 365 Field Service practice questions

Practise MB-910 questions linked to Describe Dynamics 365 Field Service.

Explore the core capabilities of customer engagement apps in Dynamics 365 practice questions

Practise MB-910 questions linked to Explore the core capabilities of customer engagement apps in Dynamics 365.

Describe shared features and Copilot capabilities practice questions

Practise MB-910 questions linked to Describe shared features and Copilot capabilities.

MB-910 fundamentals practice questions

Practise MB-910 questions linked to MB-910 fundamentals.

MB-910 scenario practice questions

Practise MB-910 questions linked to MB-910 scenario.

MB-910 troubleshooting practice questions

Practise MB-910 questions linked to MB-910 troubleshooting.

Practice this exam

Start a free MB-910 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions 20 questions 30 questions 50 questions Timed 30

MB-910 practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this MB-910 question test?

Describe Dynamics 365 Customer Insights — This question tests Describe Dynamics 365 Customer Insights — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: They will be matched as duplicates and merged based on the EmailMatch rule — Option D is correct because 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.

What should I do if I get this MB-910 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

3 more ways this is tested on MB-910

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A company is using Dynamics 365 Customer Insights to get a unified view of their customers. They have data from their e-commerce platform, CRM system, and customer support tickets. Which step is required to ensure that the same customer is recognized across these different data sources?

easy

A.Enrich profiles with external data
✓ B.Configure data matching rules
C.Create measures and KPIs
D.Set up data export destinations

Why B: B is correct because data matching rules in Dynamics 365 Customer Insights define how records from different sources (e-commerce, CRM, support tickets) are identified as belonging to the same customer. These rules use conditions like email, phone, or name to deduplicate and unify customer profiles into a single entity, ensuring consistent recognition across all ingested data sources.

Variation 2. A data engineer is reviewing the unification configuration in Dynamics 35 Customer Insights. What does this configuration accomplish?

hard

A.Calculates average revenue
B.Predicts customer churn
C.Creates a segment of customers with email
✓ D.Matches customer records by exact email

Why D: Option D is correct because the matching rule uses exact match on the email field to unify records. Option A is wrong because it doesn't segment. Option B is wrong because it doesn't create predictions. Option C is wrong because it doesn't calculate measures.

Variation 3. Refer to the exhibit. A Customer Insights data engineer is configuring data unification for a POS system. What is the purpose of the 'matchConditions' in this JSON?

medium

✓ A.To identify records that refer to the same customer
B.To filter out incomplete transactions
C.To set the refresh schedule for the data source
D.To define the schema of the target entity

Why A: Match conditions define how records from different data sources are matched for unification. Option C is correct because it identifies records that refer to the same customer.

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

This MB-910 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MB-910 exam.