Question 400 of 977
Describe Dynamics 365 Customer InsightshardMultiple ChoiceObjective-mapped

Quick Answer

The answer is to use conditional matching rules based on email and phone. This is correct because conditional matching rules in Dynamics 365 Customer Insights allow you to define a hierarchy of conditions—such as matching on email first, then falling back to phone—which resolves the conflict when data sources use different identifiers like a loyalty system’s email versus a POS system’s customer number. On the MB-910 exam, this tests your understanding of data unification strategies, often appearing in scenario-based questions where you must choose the most flexible approach to link records without a single common key. A common trap is selecting a simple exact match rule, which fails when IDs differ across sources. Remember the memory tip: “Conditional rules cascade—if email fails, phone prevails.”

MB-910 Describe Dynamics 365 Customer Insights Practice Question

This MB-910 practice question tests your understanding of describe dynamics 365 customer insights. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.

Your Customer Insights environment has multiple data sources with conflicting customer IDs. Some records from the loyalty system use email as ID, while the POS system uses a customer number. Which matching rule strategy should you use to unify these records?

Question 1hardmultiple choice
Full question →

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

Use conditional matching rules based on email and phone

Option A is correct because conditional matching rules allow you to define multiple conditions (e.g., match on email if available, otherwise match on phone) to resolve conflicts between different customer ID formats. This is the recommended approach in Dynamics 365 Customer Insights when data sources use different identifiers, as it maximizes the likelihood of correctly unifying records without requiring a single common key.

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.

  • Use conditional matching rules based on email and phone

    Why this is correct

    Matches on shared attributes when ID is different.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use exact match on customer numbers only

    Why it's wrong here

    IDs are different; exact match fails.

  • Set a priority order and keep the first source's ID

    Why it's wrong here

    This loses data from other sources.

  • Use fuzzy matching on first and last name

    Why it's wrong here

    Names may have variations.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often assume fuzzy matching on names is a safe fallback, but Microsoft specifically warns that name-based matching is error-prone and should only be used when no other unique identifiers are available.

Detailed technical explanation

How to think about this question

Under the hood, Dynamics 365 Customer Insights uses a matching rule engine that supports both exact and conditional (OR) logic across multiple attributes. Conditional matching rules evaluate conditions in sequence—for example, first try to match on email, then on phone—which is essential when data sources have overlapping but not identical identifiers. In a real-world scenario, a loyalty system might store email as the primary key while a POS system uses a customer number, and conditional rules can bridge these by also including a phone number that appears in both systems.

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 practice questions

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.

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.

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: Use conditional matching rules based on email and phone — Option A is correct because conditional matching rules allow you to define multiple conditions (e.g., match on email if available, otherwise match on phone) to resolve conflicts between different customer ID formats. This is the recommended approach in Dynamics 365 Customer Insights when data sources use different identifiers, as it maximizes the likelihood of correctly unifying records without requiring a single common key.

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

Keep practising

More MB-910 practice questions

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…

Sign in to join the discussion.

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.