A client's Dynamics 365 Sales administrator wants sellers to view the predictive score and grade on each lead, but wants only the sales operations team to be able to adjust the scoring model's configuration, such as which fields are included as predictors. A consultant is asked how to structure this. What should the consultant recommend?
Select an answer to reveal the explanation.
Short Explanation
There's a real difference between looking at a number someone else calculated and being the one who decides how that number gets calculated. Sellers just need to see the score and grade on the leads they're already working, so they only need read access to that information. The people who decide which signals feed the model, on the other hand, are making a configuration decision that affects everyone's leads, so that capability belongs with a smaller group and gets locked down through role-based access. There's no need to hand out administrator rights to the whole team, no need to strip scoring away from sellers between reviews, and no need to stand up a whole separate environment just to protect a setting. Ordinary security roles are built exactly for this kind of split between who can see something and who can change it.
Full Explanation
The correct answer is B. Viewing a lead's predictive score and grade only requires read access to the lead record and its AI insights, while changing which fields the model uses as predictors is a configuration action that should be limited through security roles to the sales operations team, keeping day-to-day visibility separate from the ability to alter how the model itself works. Option A is incorrect because predictive scoring configuration privileges can and should be scoped through normal security roles; granting System Administrator to every user is unnecessary and removes any meaningful separation of duties. Option C is incorrect because disabling scoring for sellers and re-enabling it only for reviews would strip sellers of the score and grade they need for daily prioritization, which is the opposite of what the client wants. Option D is incorrect because splitting the scoring configuration into a separate environment adds unnecessary complexity and would disconnect the model from the production lead data it needs to train and score against; environment separation is not how Dynamics 365 Sales scopes configuration access, security roles are.