Describe Dynamics 365 Customer Insights →mediumMultiple ChoiceObjective-mapped

MB-910 Describe Dynamics 365 Customer Insights Practice Question

Exhibit

Refer to the exhibit.

{
  "dataSources": [
    {
      "name": "CRM_Contacts",
      "kind": "Common Data Service",
      "tables": ["contact"]
    },
    {
      "name": "Web_Submissions",
      "kind": "PowerQuery",
      "tables": ["form_submissions"]
    }
  ],
  "unification": {
    "rules": [
      {
        "field": "emailaddress1",
        "type": "exact",
        "weight": 1.0
      }
    ]
  }
}

A customer administrator configures the unification shown. After running unification, they notice that some records from the Web_Submissions source have empty email fields. What will happen to those records?

⚠ Common exam trap

Many candidates assume empty fields cause errors or are ignored entirely, but Microsoft tests the specific behavior that empty match attributes result in unmatched profiles rather than failures or deletions.

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

✓

They will remain as unmatched profiles

In Dynamics 365 Customer Insights, when a unification rule is configured and a record from a source (e.g., Web_Submissions) has an empty email field, that record cannot be matched to any existing customer profile based on the email attribute. Instead of causing an error or being deleted, the record is retained as an unmatched profile. Unmatched profiles are stored separately and can be reviewed, merged, or acted upon later, ensuring no data loss occurs during the unification process.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
They will cause an error and stop unification
Why it's wrong here
Empty fields are handled gracefully.
✗
They will match to CRM contacts with empty email
Why it's wrong here
Empty vs empty might match but unlikely.
✓
They will remain as unmatched profiles
Why this is correct
No match possible, so they stay separate.
✗
They will be deleted from the data source
Why it's wrong here
Data is not deleted.

Go deeper

MB-910 Describe Dynamics 365 Customer Insights Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question