Question 960
At a business rolling out a new model-backed workflow, an AI project leader faces this situation: An AI service needs recurring certificate renewal, data refresh and model review but these tasks are not scheduled. Operational reliability must be measured after the initial deployment. Which governance precaution best applies to this situation?
Explanation
Correct Answer
In a business rolling out a new model-backed workflow, the key precaution is: Do not schedule model updates without considering change freeze windows and approval gates. The planned action is: Create an owned calendar for patching, data quality checks, drift reviews and model retirement. This caution matters because: Long-term operations require planned recurring technical and governance maintenance activities. The team should still verify: The receiving team has scheduled activities and can identify the next accountable reviewer.
Incorrect Answers
Model lifecycle governance requires tracked versions, owners, approvals and supported states. The appropriate correction for the reported case is: Create an owned calendar for patching, data quality checks, drift reviews and model retirement.
Deployment infrastructure must be sized for realistic demand rather than prototype traffic alone. Fixing that different mechanism would not address the current root cause: long-term operations require planned recurring technical and governance maintenance activities.
Model correctness and serving availability are separate dimensions of operational performance. Its verification is distinct from the reported condition: An AI service needs recurring certificate renewal, data refresh and model review but these tasks are not scheduled. Operational reliability must be measured after the initial deployment.