Question 340
At fictional Tangent Community Trust, a Snowflake data and AI engineering team is conducting a trusted self-service analytics redesign before any automated output can change customer or financial records. The separately composed technical incident is: A financial analytics account enables new hosted LLMs by default, but its governance policy requires specific model review and has no mechanism for enforcing a sanctioned list. Assume only these documented facts and use safe, authorized production-change procedures; exact current Snowflake feature syntax and region or account availability require current review. Which repeatable assurance or control is most relevant to preventing this situation?
Explanation
Writer-proposed answer: D (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
Review model access settings after platform updates and require approval before adding each new LLM to the sanctioned list. AI model governance requires enforceable controls and recorded approvals, not a spreadsheet of preferred models alone.
Incorrect Answers
This response concerns Overprivileged AI service account roles, which is different from the stated failure. A financial analytics account enables new hosted LLMs by default, but its governance policy requires specific model review and has no mechanism for enforcing a sanctioned list.
LLM observability without protected prompt leakage is insufficient to demonstrate this result: Automated policy tests show only sanctioned models execute in the relevant account and all denied calls produce auditable authorization results.
Semantic metadata access control mismatch is not the cause of the reported failure: A financial analytics account enables new hosted LLMs by default, but its governance policy requires specific model review and has no mechanism for enforcing a sanctioned list.