Which MLOps control BEST ensures that only validated model versions are deployed to the production environment?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Here's the deal — b is correct because a model registry with enforced promotion workflows creates a technical gate that prevents unvalidated model versions from reaching production. By requiring validation sign-off as a prerequisite for the production tag, the control is automated and cannot be bypassed by individual engineers.
Full explanation below image
Full Explanation
B is correct because a model registry with enforced promotion workflows creates a technical gate that prevents unvalidated model versions from reaching production. By requiring validation sign-off as a prerequisite for the production tag, the control is automated and cannot be bypassed by individual engineers. Version control (A) maintains code history but does not enforce validation before deployment. Daily monitoring (C) detects post-deployment problems but does not prevent unvalidated models from being deployed. Hyperparameter logging (D) is documentation, not a deployment gate.