A senior engineer notices the current plan proposes disabling drift alerts because they generate too much noise. What is the risk of that decision?
Select an answer to reveal the explanation.
Short Explanation
Muting a noisy alarm doesn't fix the noise - it just means you won't hear it when there's a real fire. If you disable drift alerts, you remove the signal along with the noise, so real behaviour changes go undetected. Tune thresholds instead of turning monitoring off.
Full Explanation
Drift alerts exist specifically to flag when live behaviour diverges from the validated baseline; turning them off to reduce noise removes the team's only ongoing signal that something has actually changed, so genuine behaviour changes after deployment would go undetected.
The option about the training pipeline stopping successfully is incorrect because alerting configuration has no effect on whether a training pipeline builds.
The option about pre-deployment validation results becoming invalid retroactively is incorrect because validation results describe the model's state at the time they were produced and are not retroactively affected by later monitoring choices.
The option about the organisation losing the ability to deploy new models entirely is incorrect because disabling alerts affects visibility into one deployed model, not the organisation's overall ability to deploy.
For the exam, address alert noise by tuning thresholds, not by disabling the monitoring itself.