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.

• ✓

  The Table-level tag value overrides the Schema-level tag value.

  Why this is correct

  Snowflake follows a 'bottom-up' precedence rule for object tagging. A tag explicitly applied to a lower-level object, such as a table, will always take precedence over the same tag inherited from a higher-level container like a schema or database, allowing for specific overrides of general governance policies.

• ✗

  The Schema-level tag value overrides the Table-level tag value.

  Why it's wrong here

  Higher-level tags do not override lower-level tags in Snowflake's governance model. If this were the case, it would be impossible to define specific exceptions for individual tables within a schema, significantly limiting the flexibility of the tagging system for complex data environments with varying levels of sensitivity.

• ✗

  Snowflake returns an error due to a conflict in the tag lineage.

  Why it's wrong here

  Tag conflicts do not result in errors; instead, Snowflake uses a deterministic inheritance model to resolve which value applies. This design ensures that administrative actions, like applying a schema-level tag, do not inadvertently break existing workflows or queries that rely on the metadata associated with individual tables.

• ✗

  Both tag values are combined into a comma-separated string for the Table.

  Why it's wrong here

  Snowflake does not aggregate or concatenate tag values through the inheritance chain. Each object can only have one active value for a specific tag at any given time, which simplifies the auditing process and ensures that security policies based on those tags have a single, clear input.