Masking policies can be applied to which of the following Snowflake objects? (Choose two.)
Masking policies can be applied to which of the following Snowflake objects? (Choose two.)
Masking policies in Snowflake can be applied to a table and a materialized view. This is because masking policies are designed to protect sensitive data at the column level, and these columns can exist within tables and materialized views. By setting a masking policy on a table or materialized view column, sensitive data such as personally identifiable information can be protected from unauthorized access.
A&C I think
Creates a new masking policy in the current/specified schema or replaces an existing masking policy. After creating a masking policy, apply the masking policy to a column in a table using an ALTER TABLE … ALTER COLUMN command or a view using an ALTER VIEW command. https://docs.snowflake.com/en/sql-reference/sql/create-masking-policy.html#normal-masking-policy
AC are correct
applied to a table or view
Correct
A&C obviously
In Snowflake, masking policies are schema-level objects, which means a database and schema must exist in Snowflake before a masking policy can be applied to a column. Currently, Snowflake supports using Dynamic Data Masking on tables and views.
Table and Mat view can be applied with masking policies, https://docs.snowflake.com/en/user-guide/security-column-intro#label-security-column-intro-mv:~:text=Snowflake%20allows%20setting,materialized%20view%20columns.
A&C Use the ALTER VIEW command to set/unset a masking policy, row access policy, or tag on/from a materialized view.
A and C, for materialized views they are not allowed to be created on columns that has a masking policy. But you can apply a masking policy on materialized views.
https://docs.snowflake.com/en/user-guide/security-column-intro.html#apply-a-conditional-masking-policy-on-a-column
https://docs.snowflake.com/en/user-guide/security-column-intro.html#label-security-column-limitations Masking policy can be applied on Mat view columns as well
It's on schema, so table or stream, since they're within schema