Question 420
During operational handoff for this problem: A team wants to trigger governance checks whenever a Snowflake model registry artifact changes but relies on manual emails. Which guardrail should be included?
Explanation
Correct Answer
Audit registry versions and deployment history at every release. This reduces recurrence of: Model registry governance links artifact identity to deployment approvals and monitoring. The verification should demonstrate: A new model version cannot bypass the documented validation and approval gate.
Incorrect Answers
Pin availability checks to target regions in AI application deployment reviews. That safeguard is aimed at ANOTHER risk: A team treats Snowflake's managed AI inference as having exactly the same regional availability for every model. It is less targeted than the control for: Model registry governance links artifact identity to deployment approvals and monitoring.
Classify data and review function availability and charges before rollout. That safeguard is aimed at ANOTHER risk: A department wants sentiment analysis in SQL but proposes shipping every customer comment to an ungoverned third-party endpoint. It is less targeted than the control for: Model registry governance links artifact identity to deployment approvals and monitoring.
Classify query types before attributing all platform requests to warehouse credits. That safeguard is aimed at ANOTHER risk: An application requires a low-latency metadata operation, but operations assumes every SQL statement must start a warehouse. It is less targeted than the control for: Model registry governance links artifact identity to deployment approvals and monitoring.