Question 330
The data governance board is asked to authorize this configuration: An internal application role needs model invocation but not data-owner privileges. Which technical approach should be preferred for this described workload?
Explanation
Correct Answer
“Grant only the needed Cortex invocation permissions to the serving role and test access with that role” is supported by this requirement: An internal application role needs model invocation but not data-owner privileges. Cortex inference access relies on Snowflake role privileges rather than textual policy reminders. Verify it using authorized invocation succeeds while negative tests for unapproved roles and datasets remain denied.
Incorrect Answers
“Use ACCOUNTADMIN as the runtime role for every model call to avoid grants” would not meet the requirement that an internal application role needs model invocation but not data-owner privileges. Cortex inference access relies on Snowflake role privileges rather than textual policy reminders. The more reliable approach is to grant only the needed Cortex invocation permissions to the serving role and test access with that role.
“Put a plain-language instruction in the prompt and call that an RBAC policy” would not meet the requirement that an internal application role needs model invocation but not data-owner privileges. Cortex inference access relies on Snowflake role privileges rather than textual policy reminders. The more reliable approach is to grant only the needed Cortex invocation permissions to the serving role and test access with that role.
“Assume ordinary USAGE on a warehouse automatically grants access to every model” would not meet the requirement that an internal application role needs model invocation but not data-owner privileges. Cortex inference access relies on Snowflake role privileges rather than textual policy reminders. The more reliable approach is to grant only the needed Cortex invocation permissions to the serving role and test access with that role.