Question 230
A metric view's revenue measure depends on a column dropped from its source table. Which implementation choice BEST addresses the stated failure?
Explanation
Correct Answer
Update the metric definition and validate downstream consumption against revised schema. This is the most directly relevant remediation because governed metrics still depend on valid source columns and relationships. A concrete acceptance check is: Metric queries succeed after schema migration with reconciled totals. To reduce recurrence: Use catalog lineage to review metric impact before DDL.
Incorrect Answers
Unreconciled identifiers across layers cause inconsistent joins and counts. Here the important technical distinction is that governed metrics still depend on valid source columns and relationships.
Independent transaction protocols cannot be treated as one shared commit log. That consideration does not remove the current constraint: governed metrics still depend on valid source columns and relationships.
Mutable natural attributes are not safe immutable analytical identifiers. In this situation, governed metrics still depend on valid source columns and relationships.