A sales manager wants her team's default Active Leads view to list leads in descending order of predictive score so the most promising leads appear first without any manual sorting each morning. The predictive score column is already present in the view. What is the most direct way for the consultant to accomplish this?
Select an answer to reveal the explanation.
Short Explanation
When someone wants a list to already be in the right order every time it opens, the setting for that lives right in the view itself, not in some background process and not in a habit sellers have to remember to repeat. A view has its own built-in sort order, and pointing that at the score column, highest first, means the ordering just happens automatically from that point forward for anyone who opens it. Building an automated process to physically shuffle records around would be solving a problem the platform already handles on its own, and it would add a maintenance burden for nothing. Relying on each person to manually sort it themselves every morning defeats the entire point of wanting this to be automatic. And hiding the lower-scoring leads entirely is a different request altogether, since it removes them from view rather than simply reordering what is shown, which is a much bigger change than what was actually asked for.
Full Explanation
The correct answer is C. A model-driven app view carries its own sort order as part of its definition, so setting that sort to the predictive score column in descending order makes every seller who opens the Active Leads view see it pre-sorted, with no manual step required, which is exactly what the manager asked for. Option A is incorrect because table records are not physically reordered in Dataverse; a flow built to attempt this would be solving a problem that does not exist and would add unnecessary complexity and maintenance overhead for no benefit over a simple view setting. Option B is incorrect because it requires every seller to repeat the same manual click every single morning, which directly contradicts the manager's stated goal of not needing manual sorting at all. Option D is incorrect because hiding lower-scored leads changes what is visible in the view rather than sorting what remains, and it silently drops leads from sight instead of simply placing the strongest ones at the top, which is a different and more disruptive outcome than what was requested. The direct fix is a one-time change to the view's sort configuration.