Regulators ask the city to prove what a reported KPI meant and which sources fed it on a specific past quarter. What metadata capability is required?
Select an answer to reveal the explanation.
Short Explanation
Auditors do not accept ‘trust me, we meant something else last spring.’ Keep historized definitions and lineage so you can show what the KPI meant and where it came from at that point in time. Live-only pages that overwrite the past fail the exam.
Full Explanation
Compliance and audit use cases require point-in-time metadata: retained historical definitions and lineage for reported KPIs. Overwriting live glossary pages destroys evidence of prior meaning. Verbal memory and dashboard screenshots without governed metadata records are insufficient. Historized metadata enables reproducible regulatory evidence.