What governance artifacts should accompany a Clarity data model?

• A. Data dictionary
• B. ERD
• C. Mapping specs, lineage diagrams, data quality rules, version history, and data stewardship roles
• D. System architecture diagrams

Answer: (C)

The main idea here is what governance artifacts are needed alongside a Clarity data model to ensure trust, traceability, and accountability. The strongest set includes mapping specs that document how data moves from source systems into the Clarity model, lineage diagrams that show where data originates and how it gets transformed, data quality rules that define validations and quality expectations, version history to track changes to the model over time, and clearly defined data stewardship roles that assign responsibility for data assets. Together, these elements provide the governance scaffolding needed to understand data flow, enforce quality, manage changes, and assign accountability.

A data dictionary, while essential metadata about data elements, doesn’t by itself show data movement or governance processes. An ERD outlines the structural relationships in the data model but lacks governance artifacts. System architecture diagrams depict technical components and infrastructure, not the governance framework around data quality, lineage, and stewardship.