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 policies within each individual schema.

  Why it's wrong here

  Distributing policies across schemas makes centralized management, auditing, and updates nearly impossible. It leads to configuration drift and increases the risk that some sensitive data remains unprotected or that policies become inconsistent across different parts of the organization, violating core governance principles of uniformity and centralized control.

• ✓

  Deploy policies to a centralized database and schema.

  Why this is correct

  Centralizing governance objects enables a single source of truth for security policies. This simplifies the management of privileges and makes auditing significantly easier, as all policies are located in one place. It also allows for clear separation of duties between the security team and the data engineering team.

• ✗

  Use a single shared role for all policy management.

  Why it's wrong here

  Using a single shared role violates the principle of least privilege. Different team members should have distinct levels of access. Furthermore, relying on a single role for all activities creates a single point of failure and makes it impossible to track individual actions within the security audit logs.

• ✗

  Manually recreate all policies in every environment.

  Why it's wrong here

  Manual recreation of policies is error-prone and highly inefficient in complex environments. It increases the likelihood of human error and makes it impossible to guarantee that all environments have the same security posture. Automated, centralized deployment is the standard for maintaining secure and compliant data platforms at scale.