In Snowflake's data security framework, how does column-level security contribute to the protection of sensitive information? (Select TWO).

Question

Options

• AImplementation of column-level security will optimize query performance.
• BColumn-level security supports encryption of the entire database.
• CColumn-level security ensures that only the table owner can access the data.
• DColumn-level security limits access to specific columns within a table based on user privileges
• EColumn-level security allows the application of a masking policy to a column within a table or view.

• A
  3% (1)
• B
  3% (1)
• D
  95% (37)

Explanation

Snowflake's column-level security works in two complementary ways: (1) It enforces privilege-based access control at the column level, meaning users without the appropriate privileges are denied access to specific columns containing sensitive data (e.g., SSNs, credit card numbers) - this is option D. (2) Dynamic Data Masking allows a masking policy to be applied directly to a column in a table or view, so different users see different representations of the data based on their role (e.g., masked '*--1234' vs. full SSN) - this is option E. Option A is incorrect; column-level security does not optimize performance. Option B is wrong because Snowflake handles encryption separately at rest and in transit. Option C is incorrect because column restrictions apply to any role, not just the table owner.

No community discussion yet for this question.