When considering row access policies and Dynamic Data Masking in Snowflake, how do they influence data visibility and security?

Question

Options

• AGrant unrestricted access to all data
• BLimit data access based on user roles
• COnly apply to certain data types
• DDynamically mask sensitive data for specific users

• B
  93% (13)
• C
  7% (1)

Explanation

Row access policies and Dynamic Data Masking (DDM) work together in Snowflake to enforce data security by limiting what users can see based on their roles (B) and masking sensitive values for specific users (D) - two complementary controls that operate at different layers: row filtering and column-level obfuscation.

Why A is wrong: Both features exist specifically to restrict access, not grant it - they are security enforcement mechanisms, the opposite of unrestricted access.

Why C is wrong: Row access policies apply to entire rows regardless of data type, and DDM masking policies can be applied broadly across column types; neither is limited to "certain data types" only.

Memory tip: Think of the two correct answers as a security sandwich - row access policies filter the rows you can see (B = "who gets which rows"), while Dynamic Data Masking controls what you see within those rows (D = "who sees real vs. masked values"). Together they cover both dimensions of data visibility: which data and how much of it.

No community discussion yet for this question.