Question 380
While validating a Snowflake workload, engineers observe: A reporting user must see a customer identifier but must not receive permission to view the raw identity document number. Which explanation best accounts for the observed behavior?
Explanation
Correct Answer
The described symptoms indicate that unrestricted base-table access can expose sensitive fields beyond the reporting need. The appropriate resolution is: Expose an approved restricted projection or masking policy with suitable role privileges. Confirm with: The reporter retrieves permitted identifiers but cannot read the protected identity value.
Incorrect Answers
Grants on existing objects do not automatically apply to future created tables. “Configure suitable FUTURE grants at the intended scope while reviewing existing permissions separately” would address that alternative cause, not the condition in this question: unrestricted base-table access can expose sensitive fields beyond the reporting need.
“Request the intended grant from the authorized schema owner or grant administrator” responds to this separate finding: grant control in a managed access schema is centralized rather than always delegated to object owners. This question instead needs “Expose an approved restricted projection or masking policy with suitable role privileges”, so the alternative does not meet the stated condition.
Data-access privileges do not automatically confer object OWNERSHIP. “Route ownership changes through an authorized owner or properly approved administrative workflow” applies to that separate problem. The observed case is a reporting user must see a customer identifier but must not receive permission to view the raw identity document number; choosing this alternative would address the wrong failure mode.