SnowPro Advanced: Architect Practice Mode

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A1

  Option A: Here is the explanation: Use caution when inserting values from a source column that has a masking policy on the source column to a target column without a masking policy on the target column. Since a masking policy is set on the source column, a role that views unmasked column data can insert unmasked data into another column, where any role with sufficient privileges on the table or view can see the value.

• 1

  A. Unmasked data will be loaded in the new column. Here’s why: When a user with appropriate privileges to see unmasked data loads data from a column with a masking policy into another column without a masking policy, the data loaded into the new column will be unmasked. This is because the user's privileges allow them to access the original data without the masking applied. Since the new column does not have a masking policy, it will simply store the data as it was accessed by the user, which in this case is unmasked. Therefore, the new column will contain the unmasked data regardless of the masking policy on the original column, and no additional masking will be applied to the new column unless explicitly defined.

• 2

  C Use caution when inserting values from a source column that has a masking policy on the source column to a target column without a masking policy on the target column. Since a masking policy is set on the source column, a role that views unmasked column data can insert unmasked data into another column, where any role with sufficient privileges on the table or view can see the value. If a role that sees masked data in the source column inserts those values into a target column, the inserted values remain masked. https://docs.snowflake.com/en/user-guide/security-column-intro