A model governance team uses SAS Model Manager to enforce a policy that all models must be validated before promotion to production. Which SAS Model Manager feature enforces this workflow policy?
Select an answer to reveal the explanation.
Short Explanation
Here's the deal — SAS Model Manager enforces this with workflow states and role-based transitions, so you can't promote a model until a designated validator completes validation. That's why the workflow states and role-based access controls option is the right one.
Full Explanation
The workflow states and transitions with role-based access controls preventing promotion without a completed validation step by a designated validator role is correct because SAS Model Manager implements lifecycle workflow management with defined states (Development, Validation, Production, Retired) and role-based transitions. Administrators can configure workflow policies so only models in the Validated state can be promoted to Production, and only users with the Validator role can approve validation. The model comparison view that automatically selects the best-performing model for promotion is an analysis view, not a promotion gate. The model monitoring thresholds that block scoring if performance drops below a minimum KS threshold are post-deployment controls, not pre-promotion gates. The model registration step requiring a performance report attachment before saving is not a standard enforced workflow gate in SAS Model Manager.