Which statement is true regarding a row access policy on a materialized view, given no policy on the underlying table?

• A. Snowflake allows adding a row access policy to a materialized view only if the underlying table has a policy
• B. A materialized view has no constraints about underlying table policies
• C. Row access policies cannot be added to any materialized view
• D. Snowflake allows adding a row access policy to a materialized view provided that a row access policy is not set on the underlying table or view

Answer: (D)

Row-level access filtering can be applied to a materialized view, but Snowflake requires that there be no row access policy defined on the underlying source object (the base table or view) before you add one to the materialized view. This keeps the visibility rules predictable rather than stacking or conflicting filters from multiple policies. If the underlying table has no policy, you can attach a row access policy to the materialized view and that policy will govern which rows are returned when querying the MV. So, in a situation with no policy on the base table, adding a policy to the materialized view is allowed and makes the MV enforce the desired row-level access. The other statements don’t align with this behavior: you don’t need a policy on the base object to add one to the MV, there are constraints to consider, and it is indeed possible to apply a row access policy to a materialized view.