Describe Dynamics 365 Sales →mediumMultiple ChoiceObjective-mapped

MB-910 Describe Dynamics 365 Sales Practice Question

Exhibit

Refer to the exhibit.

```xml
<Entity name="opportunity">
  <Attributes>
    <Attribute name="name" RequiredLevel="none" />
    <Attribute name="customerid" RequiredLevel="required" />
    <Attribute name="estimatedvalue" RequiredLevel="required" />
    <Attribute name="probability" RequiredLevel="none" />
  </Attributes>
  <BusinessRules>
    <Rule name="SetProbability">
      <Condition attribute="estimatedvalue" operator="gt" value="10000" />
      <Action attribute="probability" value="0.5" />
    </Rule>
  </BusinessRules>
</Entity>

The exhibit shows a configuration snippet. A sales rep creates an opportunity with an estimated value of $15,000 but the probability remains at the default (0%). What is the most likely reason?

⚠ Common exam trap

It's easy for candidates to assume the condition operator is wrong (Option D) because the rule didn't fire, but the most common oversight in Dynamics 365 is failing to publish the business rule or not setting it to run on the create event, not a logic error in the condition.

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 business rule is not published or is not set to run on create

A business rule that sets the probability based on the estimated value must be published and configured to run on the create event. If it is not published or not set to run on create, the rule will not execute when the opportunity is first created, leaving the probability at its default value (0%).

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 estimatedvalue attribute is required
Why it's wrong here
Required fields do not prevent business rules.
✗
The probability attribute is set to not required
Why it's wrong here
Required level does not affect business rule execution.
✓
The business rule is not published or is not set to run on create
Why this is correct
If the business rule is inactive or not configured for create, it won't run.
✗
The condition operator is incorrect
Why it's wrong here
The condition operator is correct for values greater than 10,000.

Go deeper

MB-910 Describe Dynamics 365 Sales Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question