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 instance has ingested data from a CRM and an e-commerce platform. After unification, some customers appear as duplicates. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Matching rules are too strict
Why wrong: Strict rules cause missed matches, not duplicates.
Matching rules are too loose
Loose rules can merge unrelated records.
Data sources have different field names
Why wrong: Field mapping addresses this, not duplicates.
Confidence level is set too low
Why wrong: Low confidence prevents matches.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Matching rules are too loose
When matching rules are too loose, the system merges records that are not truly the same customer, creating duplicates after unification. In Customer Insights, matching rules define the conditions (e.g., exact match on email, fuzzy match on name) that determine whether records from different sources represent the same entity. Loose rules allow records with minor differences to be considered matches, leading to false positives and duplicate customer profiles.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Matching rules are too strict
Why it's wrong here
Strict rules cause missed matches, not duplicates.
Matching rules are too loose
Why this is correct
Loose rules can merge unrelated records.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Data sources have different field names
Why it's wrong here
Field mapping addresses this, not duplicates.
Confidence level is set too low
Why it's wrong here
Low confidence prevents matches.
Common exam traps
The trap here is that candidates often confuse 'matching rules' with 'data mapping' or 'confidence levels,' assuming duplicates come from unmapped fields or low confidence, rather than understanding that overly permissive matching criteria directly cause false positive merges.
Detailed technical explanation
Customer Insights uses a deduplication engine that applies matching rules defined in the 'Match' step of the unification process. These rules can use exact, fuzzy, or phonetic matching (e.g., using the Jaro-Winkler algorithm for name similarity). If rules are too loose, the system may match records with slightly different spellings (e.g., 'Jon' vs. 'John') or different email domains, creating duplicate unified profiles that require manual review to resolve.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Describe Dynamics 365 Customer Insights — study guide chapter
Learn the concepts, then practise the questions
Describe Dynamics 365 Customer Insights practice questions
Targeted practice on this topic area only
All MB-910 questions
977 questions across all exam domains
Microsoft Dynamics 365 Fundamentals CRM MB-910 study guide
Full concept coverage aligned to exam objectives
MB-910 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise MB-910 questions linked to Describe Dynamics 365 Customer Insights.
Practise MB-910 questions linked to Describe Dynamics 365 Sales.
Practise MB-910 questions linked to Describe Dynamics 365 Customer Service.
Practise MB-910 questions linked to Describe Dynamics 365 Field Service.
Practise MB-910 questions linked to Explore the core capabilities of customer engagement apps in Dynamics 365.
Practise MB-910 questions linked to Describe shared features and Copilot capabilities.
Practise MB-910 questions linked to MB-910 fundamentals.
Practise MB-910 questions linked to MB-910 scenario.
Practise MB-910 questions linked to MB-910 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Describe Dynamics 365 Customer Insights — This question tests Describe Dynamics 365 Customer Insights — Read the scenario before looking for a memorised answer..
The correct answer is: Matching rules are too loose — When matching rules are too loose, the system merges records that are not truly the same customer, creating duplicates after unification. In Customer Insights, matching rules define the conditions (e.g., exact match on email, fuzzy match on name) that determine whether records from different sources represent the same entity. Loose rules allow records with minor differences to be considered matches, leading to false positives and duplicate customer profiles.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
Keep practising
Last reviewed: Jun 24, 2026
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.
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.
Sign in to join the discussion.