A consultant at a distribution company is rolling out Dynamics 365 Sales predictive scoring for both the Leads and Opportunities tables, since sellers work leads through to close and want a likelihood signal at every stage. After enabling scoring on the Leads table, the consultant notices the Opportunities table still shows no predictive score column available to add. What should the consultant do to get a working score on Opportunities as well?
Select an answer to reveal the explanation.
Short Explanation
Picture two separate light switches, one wired to the Leads panel and one wired to the Opportunities panel. Flipping the Leads switch on does absolutely nothing to the Opportunities panel, because they are not wired together at all. Each table gets its own scoring setup, trained on that table's own history of wins and losses, and each one has to be switched on and configured on its own. So when the consultant sees no score showing up on Opportunities, the answer is not to wait, not to hope a sync job catches up, and not to reroute the Leads setup to cover both tables. It is simply to go build the second switch. Adding more administrators does not help either, since that only changes who is allowed to flip switches, not how many panels exist. The practical lesson is that rolling out scoring across a sales process that spans Leads and Opportunities means doing the setup work twice, once per table, each with its own relevant historical data.
Full Explanation
The correct answer is A. Predictive scoring in Dynamics 365 Sales is configured and enabled independently for each supported table, so turning it on for Leads does nothing for Opportunities. The consultant needs to go into the predictive scoring settings and set up a separate model targeting the Opportunities table, trained on that table's own historical won and lost records. Option B is incorrect because there is no background sync that propagates a score from one table's model to another; each model only ever scores the records in the table it was built for, and no amount of waiting changes that. Option C is incorrect because scoring models are bound to the table they were configured against, and redirecting a Leads model's target field to Opportunities is not a supported path and would not produce a valid Opportunities score. Option D is incorrect because the number of System Administrators has no bearing on which tables have scoring enabled; role assignment controls who can open and configure the feature, not which tables it covers. The fix is a configuration step for the Opportunities model itself, not a permissions or timing issue.