The correct answer is to modify the matching rules to be stricter. This approach reduces duplicates after customer insights unification by requiring more fields—such as email and phone in addition to name—to match before records are merged, which cuts down on false positives while preserving all original data. In Dynamics 365 Customer Insights, matching rules control how profile attributes are compared during the unification process, and making them stricter increases precision without deleting or overwriting any information, unlike manual cleanup or outright deletion. On the MB-910 exam, this scenario tests your understanding of data quality controls within Customer Insights, often appearing as a trap where candidates mistakenly choose to delete duplicates or adjust merge priorities. Remember the key principle: stricter rules prevent unnecessary merges, not data loss. A helpful memory tip is “Stricter is safer”—tighten the match criteria to keep your data intact and your records clean.
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.
A company uses Dynamics 365 Customer Insights and notices that some customer records are duplicated after unification. They want to reduce duplicates without losing data. What should they do?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Modify the matching rules to be stricter
Modifying the matching rules to be stricter reduces the number of false-positive duplicates by requiring more fields to match (e.g., adding email and phone to name matching). This preserves all data while preventing unnecessary merges, unlike deletion or manual processes. In Dynamics 365 Customer Insights, matching rules define which profile attributes are compared during unification, and stricter rules increase precision without data loss.
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.
Read the scenario before looking for a memorised answer.
✗
Delete all duplicate records from the source systems
Why it's wrong here
Source data should remain intact; Customer Insights manages unification.
✗
Increase the confidence score threshold for matching
Why it's wrong here
Increasing threshold would increase duplicates, not reduce.
✗
Run the deduplication process manually
Why it's wrong here
Automated deduplication runs on schedule; manual run doesn't change rules.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse 'increasing the confidence score threshold' (which only affects fuzzy match sensitivity) with 'modifying matching rules' (which changes the actual conditions for a match), leading them to choose option C instead of A.
Detailed technical explanation
How to think about this question
In Dynamics 365 Customer Insights, the unification process uses a two-step approach: match and merge. Matching rules are defined using conditions like 'exact' or 'fuzzy' matching on attributes (e.g., name, email, phone). Stricter rules (e.g., requiring exact match on email AND fuzzy match on name) reduce false positives by increasing the specificity of the match condition. The confidence score threshold (0–1) controls the minimum similarity for fuzzy matches, but adjusting it alone does not change the rule structure; combining stricter rules with an appropriate threshold is the best practice for precision.
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.
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: Modify the matching rules to be stricter — Modifying the matching rules to be stricter reduces the number of false-positive duplicates by requiring more fields to match (e.g., adding email and phone to name matching). This preserves all data while preventing unnecessary merges, unlike deletion or manual processes. In Dynamics 365 Customer Insights, matching rules define which profile attributes are compared during unification, and stricter rules increase precision without data loss.
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 →
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 using Dynamics 365 Customer Insights notices that the unified customer profiles show duplicate records for some customers. They have already configured matching rules. What should they do to resolve the duplicate records that are not being merged?
hard
A.Disable data unification and start over
✓ B.Review and refine the matching rules, and use the merge conflicts resolution feature
C.Delete duplicate records manually in the source systems
D.Re-ingest all data from source systems
Why B: If duplicates remain, adjusting matching rules or using manual merge helps. Option C is correct. Option A is unrelated. Option B deletes data without resolution. Option D is too drastic.
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.
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.