The answer is to map the custom field to the forecast category in the forecasting configuration. This is correct because Dynamics 365 Sales forecasting engine defaults to the standard 'Est. Revenue' field for revenue aggregation; custom revenue fields are ignored unless explicitly linked. By mapping the custom field within the forecast category setup, you tell the system exactly which field to use for calculating pipeline amounts, fixing the incorrect forecasting. On the MB-910 exam, this tests your understanding of forecast configuration versus simple field creation—a common trap is assuming custom fields automatically feed into reports. Remember, the forecast category acts as a bridge: if your team uses custom revenue field forecasting, you must map that field to the category, not just add it to the opportunity form. Memory tip: “Map it to tap it”—you must map the custom field to the forecast category for the system to tap its value.
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.
A sales manager notices that the opportunity pipeline report shows incorrect forecasting amounts. The sales team uses custom revenue fields instead of the standard 'Est. Revenue' field. What should the administrator configure to ensure accurate forecasting?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Map the custom field to the forecast category in the forecasting configuration
The forecasting engine in Dynamics 365 Sales relies on the 'Est. Revenue' field by default. When a sales team uses custom revenue fields, those fields are not automatically included in forecast calculations. Mapping the custom field to the forecast category in the forecasting configuration explicitly tells the system to use that field's value for revenue aggregation, ensuring accurate pipeline amounts.
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.
✗
Enable the custom field in the opportunity form
Why it's wrong here
Custom fields need to be mapped in forecasting configuration, not just enabled on forms.
✓
Map the custom field to the forecast category in the forecasting configuration
Why this is correct
Mapping the custom field to the forecast category ensures it is used in pipeline calculations.
Related concept
Read the scenario before looking for a memorised answer.
✗
Add the custom field to the lead entity
Why it's wrong here
Forecasting is based on opportunities, not leads.
✗
Configure sales acceleration rules to include the custom field
Why it's wrong here
Sales acceleration deals with lead assignment, not revenue mapping for forecasting.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume making a custom field visible on the form (Option A) is sufficient for it to be included in system calculations, but Dynamics 365 requires explicit mapping in the forecast configuration to override the default revenue field.
Detailed technical explanation
How to think about this question
Under the hood, Dynamics 365 Sales forecasting uses a 'Forecast Configuration' entity that defines which fields are mapped to revenue, quantity, and other metrics. When a custom field is mapped, the system replaces the standard 'Est. Revenue' field in the aggregation query with the custom field's value. This mapping is stored in the 'msdyn_forecastconfiguration' table, and the forecast grid recalculates using the mapped field during each refresh. A subtle behavior: if the custom field is not present on all opportunity records, the forecast may show null or zero for those records, so the administrator must ensure the field is populated consistently.
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: Map the custom field to the forecast category in the forecasting configuration — The forecasting engine in Dynamics 365 Sales relies on the 'Est. Revenue' field by default. When a sales team uses custom revenue fields, those fields are not automatically included in forecast calculations. Mapping the custom field to the forecast category in the forecasting configuration explicitly tells the system to use that field's value for revenue aggregation, ensuring accurate pipeline amounts.
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.
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.