Describe Dynamics 365 Customer Insights →hardMultiple ChoiceObjective-mapped

MB-910 Describe Dynamics 365 Customer Insights Practice Question

Exhibit

Refer to the exhibit.

{
  "name": "CustomerProfile",
  "attributes": [
    {"name": "CustomerId", "dataType": "string"},
    {"name": "FirstName", "dataType": "string"},
    {"name": "LastName", "dataType": "string"},
    {"name": "Email", "dataType": "string"},
    {"name": "TotalPurchaseAmount", "dataType": "decimal"}
  ],
  "keys": [
    {"name": "CustomerId", "isPrimary": true}
  ]
}

You are reviewing the exhibit of a Customer Insights - Data entity definition. The company wants to create a segment of customers whose TotalPurchaseAmount is greater than 1000. Which attribute should be used in the segment condition?

⚠ Common exam trap

The trap here is that candidates may mistakenly think any customer attribute can be used in a numeric condition, but only attributes defined as numeric measures (like TotalPurchaseAmount) support comparison operators such as greater than.

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

✓

TotalPurchaseAmount

The segment condition requires an attribute that stores the total purchase amount for each customer. In Dynamics 365 Customer Insights - Data, the TotalPurchaseAmount attribute is a numeric measure that can be directly compared using a greater-than operator. Using any other attribute, such as CustomerId, FirstName, or Email, would not evaluate the purchase amount condition.

Answer analysis

Option-by-option breakdown

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

✗
CustomerId
Why it's wrong here
CustomerId is the identifier, not the purchase amount.
✗
FirstName
Why it's wrong here
FirstName is a name field, not purchase amount.
✗
Email
Why it's wrong here
Email is a contact field, not purchase amount.
✓
TotalPurchaseAmount
Why this is correct
TotalPurchaseAmount holds the purchase amount value.

Go deeper

MB-910 Describe Dynamics 365 Customer Insights Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question