DEA-C02 Data Governance Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Create separate secure views for every user role requiring masked access.

  Why it's wrong here

  Creating views for every role leads to a 'view explosion' problem, making maintenance difficult as schema changes occur. Security overhead increases significantly, and performance optimizations like query result caching may be less effective compared to native masking policies that apply directly to the base table column.

• ✓

  Apply a masking policy to the columns and grant the APPLY MASKING POLICY privilege.

  Why this is correct

  Applying a masking policy directly to columns provides a centralized way to enforce data governance. By granting the APPLY MASKING POLICY privilege to a governance role, you ensure that security policies are managed by the data security team rather than the database owners, following the principle of least privilege.

• ✗

  Use row-level security to filter rows containing PII data for authorized users.

  Why it's wrong here

  Row-level security restricts access to entire rows, not specific columns within a row. If an analyst requires access to sales figures but not the customer name, row-level security would hide the entire record, preventing the analyst from performing necessary aggregations on the sales metrics.

• ✗

  Physically transform the data during the ETL process and store it in a new table.

  Why it's wrong here

  Physical transformation creates data silos and increases storage costs. It also makes data recovery or ad-hoc analysis of raw data impossible for authorized personnel. Governance best practices favor keeping data in its original state while using Snowflake's native policy features to control access and visibility at runtime.