Question 120
During a Snowflake architecture review, the team finds: A data science role can SELECT existing reporting tables but not new tables added daily to the same schema. Which explanation best accounts for the observed behavior?
Explanation
Correct Answer
The described symptoms indicate that grants on existing objects do not automatically apply to future created tables. The appropriate resolution is: Configure suitable FUTURE grants at the intended scope while reviewing existing permissions separately. Confirm with: A newly created table receives the intended SELECT grant without giving access to unrelated schemas.
Incorrect Answers
Unrestricted base-table access can expose sensitive fields beyond the reporting need. “Expose an approved restricted projection or masking policy with suitable role privileges” would address that alternative cause, not the condition in this question: grants on existing objects do not automatically apply to future created tables.
“Check session secondary role activation and grant paths before changing object permissions” responds to this separate finding: snowflake can evaluate enabled secondary roles as well as the current primary role for authorized operations. This question instead needs “Configure suitable FUTURE grants at the intended scope while reviewing existing permissions separately”, so the alternative does not meet the stated condition.
Broad system administrator privileges exceed the developers' operational duties. “Create scoped custom roles with the required object and warehouse privileges rather than distributing ACCOUNTADMIN” applies to that separate problem. The observed case is a data science role can SELECT existing reporting tables but not new tables added daily to the same schema; choosing this alternative would address the wrong failure mode.