Describe Dynamics 365 Sales →hardMultiple ChoiceObjective-mapped

MB-910 Describe Dynamics 365 Sales Practice Question

Exhibit

Refer to the exhibit. The following is a snippet from a Power Automate flow triggered when an opportunity is closed as Won:
{
  "trigger": "When a row is added, modified or deleted",
  "entityName": "opportunities",
  "scope": "Organization",
  "triggerConditions": {
    "statuscode": 3
  }
}

Based on the exhibit, when will this flow trigger?

⚠ Common exam trap

Watch out — candidates often confuse the 'When an opportunity is closed as Won' trigger with the 'When an opportunity is created' trigger, assuming any closure event triggers the flow, but the trigger is specifically tied to the 'Won' status value, not creation or other closure states.

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

✓

When an opportunity is closed as Won

The flow trigger is set to 'When an opportunity is closed as Won' because the exhibit shows the trigger condition 'When an opportunity is closed as Won' selected in the Power Automate trigger configuration. This means the flow will only execute when an opportunity's status is updated to 'Won' in Dynamics 365 Sales, not on creation, reopening, or loss.

Answer analysis

Option-by-option breakdown

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

✗
When any opportunity is created
Why it's wrong here
The flow triggers on modification, and only when statuscode equals 3.
✓
When an opportunity is closed as Won
Why this is correct
Statuscode 3 indicates Won in the default opportunity entity.
✗
When an opportunity is reopened
Why it's wrong here
Reopened opportunities would have a different statuscode.
✗
When an opportunity is lost
Why it's wrong here
Lost opportunities have statuscode 4.

Go deeper

MB-910 Describe Dynamics 365 Sales Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question