COF-C03 Account Management and 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.

• ✓

  Masking policy

  Why this is correct

  A masking policy is a schema-level object that can be applied to a column to dynamically mask its data based on the user's role. You can define a policy that returns '****' for all roles except 'COMPLIANCE_OFFICER'. This precisely meets the requirement of column-level masking for unauthorized users.

• ✗

  Object tagging

  Why it's wrong here

  Object tagging is used to assign metadata to objects for governance and tracking, but it does not mask data. Tags can be used in conjunction with masking policies, but alone they do not enforce any data protection. This option does not provide the required masking behavior.

• ✗

  Secure view

  Why it's wrong here

  Secure views hide the view definition and can be used to restrict access to underlying data, but they do not provide column-level masking based on roles. They are typically used to prevent exposure of the query logic, not to dynamically mask data values for specific roles.

• ✗

  Row access policy

  Why it's wrong here

  Row access policies filter rows based on conditions, such as user role. They do not mask column values; they restrict which rows are visible. In this scenario, the requirement is to mask a specific column's values, not to filter rows.