A data governance team is drafting a policy for handling personally identifiable information (PII). According to data governance best practices, which document should define the classification levels and handling procedures?
Trap 1: Data dictionary
A data dictionary documents technical metadata — field names, data types, formats and lineage — rather than mandating classification tiers or handling rules. It would be the correct artefact when cataloguing schema definitions, whereas policy-level classification belongs in a data classification policy or standard.
Trap 2: Data quality report
A data quality report measures accuracy, completeness and consistency of datasets; it defines no classification tiers or handling procedures, so it cannot govern PII. It tempts because quality reporting supports governance oversight, and it would be the right artefact when the requirement is monitoring data fitness rather than prescribing handling rules.
Trap 3: Data flow diagram
A data flow diagram maps where data moves between systems and processes; it records no classification tiers or handling rules, so it cannot serve as the governing policy. It is tempting because flow diagrams are genuinely useful for tracing PII propagation during a privacy impact assessment, but the classification scheme itself belongs in a data classification policy.
- A
Data dictionary
Why it fails: A data dictionary documents technical metadata — field names, data types, formats and lineage — rather than mandating classification tiers or handling rules. It would be the correct artefact when cataloguing schema definitions, whereas policy-level classification belongs in a data classification policy or standard.
- B
Data classification policy
A data classification policy defines the tiers of sensitivity and the handling rules for each, directly satisfying the stem's requirement for a document specifying PII classification levels and procedures. It governs how data is labelled and protected, unlike retention schedules or access-control standards, which address different governance concerns.
- C
Data quality report
Why it fails: A data quality report measures accuracy, completeness and consistency of datasets; it defines no classification tiers or handling procedures, so it cannot govern PII. It tempts because quality reporting supports governance oversight, and it would be the right artefact when the requirement is monitoring data fitness rather than prescribing handling rules.
- D
Data flow diagram
Why it fails: A data flow diagram maps where data moves between systems and processes; it records no classification tiers or handling rules, so it cannot serve as the governing policy. It is tempting because flow diagrams are genuinely useful for tracing PII propagation during a privacy impact assessment, but the classification scheme itself belongs in a data classification policy.