A masking policy cannot be set on a view if a materialized view is created from that view.

• A. True
• B. False
• C. Not specified
• D. Only when the view is encrypted

Answer: (A)

Masking policies are evaluated at query time, while a materialized view stores precomputed results. When a materialized view is created, Snowflake writes out the exact data produced by the defining query and keeps that stored until refresh. Those stored results don’t go through masking policy logic again on access, so the intended protection would not be guaranteed for data returned from the materialized view. If a masking policy were allowed on a view that serves as the source for a materialized view, the materialized data could expose values that the policy is meant to hide. To prevent this risk, Snowflake disallows applying a masking policy on a view if a materialized view is created from that view.