The answer is the estimatedvalue weight of 0.4, which overemphasizes revenue and causes predictive scoring weight imbalance. In predictive scoring models, each attribute like estimated value or probability is assigned a weight to normalize its influence on the final score. When the estimatedvalue weight is set to 0.4—the highest single weight in the configuration—it dominates the calculation, meaning that even opportunities with low probability will score highest simply because their revenue is very high. On the Microsoft Dynamics 365 Fundamentals CRM MB-910 exam, this scenario tests your understanding of how weight distribution directly impacts scoring outcomes, often appearing as a trap where you might assume probability is the primary driver. A useful memory tip: think of it as a seesaw—if revenue’s weight is too heavy, it tips the score away from likelihood, creating a predictive scoring weight imbalance that misaligns with sales priorities.
MB-910 Describe Dynamics 365 Sales Practice Question
This MB-910 practice question tests your understanding of describe dynamics 365 sales. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
The exhibit shows a configuration for predictive scoring. A sales rep notices that opportunities with very high estimated values are always scored highest regardless of low probability. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Clue: "always"
Why it matters: Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The estimatedvalue weight of 0.4 overemphasizes revenue
Option C is correct because the estimatedvalue weight of 0.4 is the highest single weight in the predictive scoring model, causing revenue to dominate the score. Even when probability is low, the high estimated value overrides other factors, leading to opportunities with very high estimated values always scoring highest. This imbalance means the model is not properly normalizing the influence of revenue versus likelihood of close.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 normalization method is incorrect
Why it's wrong here
Min-max normalization is standard; the issue is weight distribution.
✗
The createdon weight of 0.2 is too high
Why it's wrong here
Createdon weight is low and not the cause.
✓
The estimatedvalue weight of 0.4 overemphasizes revenue
Why this is correct
The highest weight on estimatedvalue causes high-value opportunities to dominate.
Clue confirmation
The clue words "most likely", "always" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The probability weight is too low
Why it's wrong here
Probability weight is 0.3, still significant but not dominant.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume the probability weight must be too low, but the real issue is the disproportionate weight on estimatedvalue (0.4) relative to other attributes, which directly causes the described behavior.
Detailed technical explanation
How to think about this question
Predictive scoring in Dynamics 365 Sales uses a weighted linear combination of attributes (e.g., estimated value, probability, created date) to compute a score from 0 to 100. The weights are normalized to sum to 1.0, so a weight of 0.4 for estimatedvalue means 40% of the final score is driven by revenue alone. In practice, this can cause sales reps to chase high-value but unlikely deals, misaligning with pipeline management best practices. The model can be tuned by adjusting weights or using custom scoring models to balance revenue and probability.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Describe Dynamics 365 Sales — This question tests Describe Dynamics 365 Sales — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The estimatedvalue weight of 0.4 overemphasizes revenue — Option C is correct because the estimatedvalue weight of 0.4 is the highest single weight in the predictive scoring model, causing revenue to dominate the score. Even when probability is low, the high estimated value overrides other factors, leading to opportunities with very high estimated values always scoring highest. This imbalance means the model is not properly normalizing the influence of revenue versus likelihood of close.
What should I do if I get this MB-910 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely", "always". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This MB-910 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MB-910 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.