Thresholds and alerts need a place in the broader governance lifecycle, beyond just technical monitoring. What is the best answer for how they fit?
Select an answer to reveal the explanation.
Short Explanation
Thresholds and alerts aren't just plumbing - they're the trigger that gets you into the loop when something needs a decision. They connect ongoing model behavior to human review, closing the gap between monitoring and governance action.
Full Explanation
Thresholds and alerts fit governance because they connect ongoing model behavior to a human review step, closing the loop between monitoring and governance action. By triggering review at the right moment, they turn passive monitoring data into an actionable governance event.
The purely technical logging view is incorrect because their value comes from feeding governance decisions, not logging alone.
The validation-phase-only view is incorrect because ongoing monitoring after validation is when drift and operational risk emerge.
The factsheet-replacement view is incorrect because alerts and factsheets serve different purposes and are not interchangeable.
Exam caveat: describe thresholds and alerts as the link between monitoring data and governance review.