Describe Dynamics 365 Customer Insights →mediumMultiple ChoiceObjective-mapped

MB-910 Describe Dynamics 365 Customer Insights Practice Question

Exhibit

Refer to the exhibit.

{
  "triggers": [
    {
      "id": "btn_click",
      "name": "ButtonClicked",
      "entityType": "Contact",
      "eventType": "CustomEvent",
      "fields": ["ContactId", "ButtonName", "Timestamp"]
    }
  ],
  "segments": [
    {
      "id": "active_users",
      "name": "Active Users",
      "entityType": "Contact",
      "query": "Contact.Status eq 'Active'"
    }
  ],
  "journeys": [
    {
      "id": "welcome",
      "name": "Welcome Journey",
      "trigger": "btn_click",
      "segment": "active_users",
      "actions": [
        {
          "type": "SendEmail",
          "emailTemplate": "WelcomeEmail"
        }
      ]
    }
  ]
}

Refer to the exhibit. You are setting up a journey in Dynamics 365 Customer Insights - Journeys. The journey is triggered by a custom event 'ButtonClicked' and targets the 'Active Users' segment. After publishing, the journey does not start. What is the most likely cause?

⚠ Common exam trap

Test-takers frequently assume journey startup failures are caused by missing event mappings or authentication issues, when in fact the most common cause is an invalid segment query that fails validation before the journey can begin.

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 segment query uses an invalid field name for the Contact entity.

A segment query referencing an invalid field name for the Contact entity will cause the segment to fail to resolve, preventing the journey from starting. In Dynamics 365 Customer Insights - Journeys, the journey engine validates the segment before launching; if the segment query contains a field that does not exist on the Contact entity, the segment cannot be evaluated, and the journey remains in a 'Draft' or 'Stopped' state.

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 email template 'WelcomeEmail' does not exist.
Why it's wrong here
A missing email template would cause an error when the email action is executed, but the journey would still start.
✗
The custom event requires authentication that is not configured.
Why it's wrong here
Custom events do not require authentication by default.
✓
The segment query uses an invalid field name for the Contact entity.
Why this is correct
An invalid field in the segment query prevents the segment from being evaluated.
✗
The trigger event does not include a 'ContactId' field.
Why it's wrong here
The trigger includes ContactId, but even if missing, the journey could still start with other identifiers.

Visual reference

Go deeper

MB-910 Describe Dynamics 365 Customer Insights Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question