Question 120
At fictional Ironvale Learning Services, a Snowflake data and AI engineering team is conducting a multi-tenant knowledge assistant improvement while preserving enterprise data boundaries and a reviewable audit trail. The separately composed technical incident is: A knowledge assistant sends Snowflake Cortex requests from a browser using a powerful static database credential embedded in client-side JavaScript, exposing unrestricted access to anyone inspecting the app. 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
Automate client-secret scanning, scoped credential issuance, role reviews and emergency rotation drills for integration identities. API interfaces are transport mechanisms, not substitutes for credential confidentiality, role scoping and an auditable service identity.
Incorrect Answers
This response concerns Model-selection latency and reliability tradeoffs, which is different from the stated failure. A knowledge assistant sends Snowflake Cortex requests from a browser using a powerful static database credential embedded in client-side JavaScript, exposing unrestricted access to anyone inspecting the app.
Agent permissions and external tool boundaries is insufficient to demonstrate this result: Security tests show no server secrets in the delivered client assets and confirm unauthorized API calls cannot execute or access protected datasets.
Grounded employee policy assistant architecture is not the cause of the reported failure: A knowledge assistant sends Snowflake Cortex requests from a browser using a powerful static database credential embedded in client-side JavaScript, exposing unrestricted access to anyone inspecting the app.