MB-910 Describe Dynamics 365 Customer Insights Practice Question
Exhibit
Refer to the exhibit.
{
"name": "CustomerUnificationConfig",
"dataSources": [
{
"id": "ds_orders",
"kind": "Power Query",
"entities": [
{
"name": "Orders",
"fields": ["OrderID", "CustomerID", "OrderDate", "Amount"]
}
]
},
{
"id": "ds_web",
"kind": "Power Query",
"entities": [
{
"name": "WebVisits",
"fields": ["VisitID", "CustomerID", "Page", "Duration"]
}
]
}
],
"unify": {
"match": {
"rules": [
{
"entity1": "Orders",
"entity2": "WebVisits",
"conditions": [
{
"field1": "CustomerID",
"field2": "CustomerID",
"operator": "equals"
}
]
}
]
},
"merge": {
"conflictResolution": "SourceOrder",
"sourceOrder": ["ds_orders", "ds_web"]
}
}
}Refer to the exhibit. You are configuring data unification in Dynamics 365 Customer Insights - Data. After running the unification process, you notice that the merged profile contains the 'Amount' field from the Orders entity but the 'Duration' field from the WebVisits entity is missing. The conflict resolution is set to 'SourceOrder' with ds_orders first. Which action should you take to include the 'Duration' field in the unified profile?
⚠ Common exam trap
Candidates often confuse conflict resolution (which handles overlapping field values) with field inclusion (which determines which fields appear in the output), leading them to incorrectly choose reversing the source order or modifying matching rules instead of adjusting the merge configuration to include all fields.
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
✓
Modify the merge configuration to include all fields from both entities in the output profile.
The 'Duration' field is missing because the merge configuration is set to 'SourceOrder' with ds_orders first, meaning only fields present in the first source (ds_orders) are included in the unified profile by default. To include fields from ds_web (like 'Duration'), you must modify the merge configuration to explicitly include all fields from both entities in the output profile, overriding the default source-order-based field selection.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Change the matching rule to include the 'Duration' field as a condition.
Why it's wrong here
Matching rules are for identifying duplicates, not for field inclusion.
- ✓
Modify the merge configuration to include all fields from both entities in the output profile.
Why this is correct
The merge step must specify which fields to include in the unified profile.
- ✗
Add the 'Duration' field to the Orders entity definition.
Why it's wrong here
Adding a field to the source entity does not automatically include it in the merged profile.
- ✗
Reverse the source order to place ds_web first.
Why it's wrong here
Source order only affects conflict resolution; fields not merged will still be missing.
Go deeper
Related to this question
About these practice questions
One of 941 original MB-910 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.