Question 40
At fictional Tangent Community Trust, a Snowflake data and AI engineering team is conducting a trusted self-service analytics redesign while preserving enterprise data boundaries and a reviewable audit trail. The separately composed technical incident is: A proof-of-concept LLM application uses the same Snowflake role, data stage and API secrets in development and production, so test users can view live customer records while testing prompts. 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
Require environment-specific service identities, secret rotation, synthetic test data and a documented preproduction access-control validation. Environment isolation and controlled promotion reduce the blast radius of Gen AI experimentation without sacrificing testability.
Incorrect Answers
This response concerns SQL and REST authentication boundary, which is different from the stated failure. A proof-of-concept LLM application uses the same Snowflake role, data stage and API secrets in development and production, so test users can view live customer records while testing prompts.
Prompt injection in retrieved business content is insufficient to demonstrate this result: Audit logs and negative tests confirm no development identity can reach production secrets or confidential rows, while approved release artifacts are reproducible.
Grounded employee policy assistant architecture is not the cause of the reported failure: A proof-of-concept LLM application uses the same Snowflake role, data stage and API secrets in development and production, so test users can view live customer records while testing prompts.