A sales manager wants her team's assigned leads view to automatically surface the leads most likely to convert at the top of the list each morning, without sellers manually reordering anything themselves. Which configuration should the consultant use to achieve this?
Select an answer to reveal the explanation.
Short Explanation
You want the leads most likely to convert sitting at the top when sellers open the view, so add the predictive score column and sort by it in descending order. That lets the view rank automatically without manual reordering. Sorting by newest creation date only shows recency, nightly emails are unnecessary, and duplicate detection doesn't rank leads.
Full Explanation
The correct configuration is to add the predictive score column to the view and sort leads by that field in descending order. Since the predictive lead scoring model already produces a numeric score reflecting conversion likelihood, the most direct way to surface the most promising leads automatically is to let the view itself sort by that score, so the view always reflects current priority without any manual reordering by sellers. Sorting the view by the created-on date in descending order is incorrect because it only reflects how recently a lead entered the system, which has no bearing on how likely it is to convert and would frequently push high-potential older leads down the list. Building a Power Automate flow that emails a ranked list of leads to each seller every night is incorrect because it introduces unnecessary complexity and a separate artifact outside the working view, when the view itself can already be configured to sort by score directly within the application the sellers already use. Enabling duplicate detection rules on the lead entity is incorrect because duplicate detection rules address data quality by flagging or preventing redundant records; they have no relationship to ranking leads by conversion likelihood and would not change how the view is ordered.