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

Quick Answer

The correct action is to modify the merge configuration to include all fields from both entities in the output profile. This is necessary because when conflict resolution is set to 'SourceOrder' with ds_orders first, the unification process defaults to including only the fields present in the first source entity, ds_orders, thereby excluding fields unique to subsequent entities like the 'Duration' field from ds_web. On the MB-910 exam, this scenario tests your understanding of data unification and merge configuration in Dynamics 365 Customer Insights, specifically how source order priority can inadvertently drop fields from secondary sources. A common trap is assuming that all fields automatically merge; instead, you must explicitly configure the merge to retain fields from every entity. Remember the tip: "Source order picks the winner, but you must list the roster" — meaning the order resolves conflicts, but you must manually specify all fields you want in the unified profile.

MB-910 Describe Dynamics 365 Customer Insights Practice Question

This MB-910 practice question tests your understanding of describe dynamics 365 customer insights. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.

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?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "first"

    Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.

Question 1hardmultiple choice
Full 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"]
    }
  }
}

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.

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.

  • 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.

    Clue confirmation

    The clue word "first" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • 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.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates 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.

Detailed technical explanation

How to think about this question

In Dynamics 365 Customer Insights - Data, the merge configuration's 'SourceOrder' conflict resolution determines which source's data is used when fields overlap, but it does not control field inclusion; by default, only fields from the first source are projected unless 'Include all fields' is selected. Under the hood, the unification process uses a projection step that can be customized to map fields from multiple entities into the unified profile, and failing to enable this causes fields unique to secondary sources to be dropped.

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: 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.

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.

Are there clue words in this question I should notice?

Yes — watch for: "first". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.

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

Same concept, more angles

2 more ways this is tested on MB-910

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. Refer to the exhibit. In Dynamics 365 Customer Insights - Data, the merge configuration uses 'LastUpdated' conflict resolution. What does this setting imply for the unified customer profile when there is conflicting data between the Customer and Purchase entities?

easy
  • A.The value from the entity with the highest priority will be used.
  • B.The value from the entity that was last updated will be used.
  • C.The value from the Customer entity will always be used.
  • D.The value from the most recent data source will be used.

Why B: When 'LastUpdated' conflict resolution is selected in Dynamics 365 Customer Insights - Data merge configuration, the unified customer profile uses the value from the entity (Customer or Purchase) that was most recently updated. This ensures that the freshest data takes precedence, regardless of entity priority or data source order.

Variation 2. Refer to the exhibit. A customer has configured data unification in Customer Insights. What will happen when a contact from CRM and a member from Loyalty have the same email address?

medium
  • A.The CRM contact data will take priority and overwrite Loyalty member data in the unified profile
  • B.A new unified profile will be created with a new ID
  • C.The system will prompt the user to manually resolve the match
  • D.All fields from both records will be merged equally

Why A: Option A is correct because the merge strategy is PriorityBased with CRM first, so the CRM record takes precedence. Option B is wrong because the strategy is not to merge all fields equally. Option C is wrong because it's not a custom merge. Option D is wrong because the strategy is not to create a new record.

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.