MB-910 Describe Dynamics 365 Customer Insights Practice Question
You are a Dynamics 365 consultant for a multinational retail company. The company has recently deployed Dynamics 365 Customer Insights to unify customer data from point-of-sale (POS) systems, an e-commerce platform, and a loyalty program. The data ingestion pipeline is working, and unified customer profiles are being created. However, the marketing team reports that segments built using the 'LastPurchaseDate' attribute are not returning accurate results. Specifically, a segment defined as 'Customers who purchased in the last 30 days' includes customers whose last purchase was over 60 days ago, and excludes some customers who purchased yesterday. The data source for purchase transactions is updated daily via an incremental refresh. The 'LastPurchaseDate' field is computed from the transaction entity. Upon investigation, you notice that the unified profile entity shows a 'LastPurchaseDate' that is older than the most recent transaction for some customers. What is the most likely cause of this issue, and what should you do to fix it?
⚠ Common exam trap
Watch out — candidates often assume that refreshing the data source automatically updates the unified profiles and computed attributes, but in Customer Insights, unification is a separate orchestration step that must be explicitly scheduled or triggered after data refresh.
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
✓
The unification process has not been re-run after the latest data refresh; schedule the unification to run after each data refresh.
In Dynamics 365 Customer Insights, the unification process is a separate step that merges and deduplicates data from multiple sources into unified customer profiles. Even if the data source is refreshed incrementally, the unified profile entity will not reflect the latest transaction data until the unification process is re-run. Since the segment uses the 'LastPurchaseDate' from the unified profile, it will show stale data until unification is executed after each refresh.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The matching rules are incorrectly configured, causing the system to use an older transaction; update the matching rules.
Why it's wrong here
Incorrect. Matching rules affect deduplication, not field values.
- ✗
The transaction data is in a different data source that is not linked to the profile; create a new data source and link it.
Why it's wrong here
Incorrect. The data source is already linked; the data is being ingested.
- ✓
The unification process has not been re-run after the latest data refresh; schedule the unification to run after each data refresh.
Why this is correct
Correct. Unification must be re-run to incorporate new data into profiles.
- ✗
The incremental refresh is not configured correctly; reconfigure the data source to use full refresh instead.
Why it's wrong here
Incorrect. The incremental refresh is working; the transaction data is current.
Go deeper
Related to this question
About these practice questions
This MB-910 question is part of Courseiva's 941-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.