Months after deploying a recommendation model, an organisation learns that one of the third-party datasets used in training was collected without a valid lawful basis and must be removed. Which data governance capability most directly enables the team to identify every downstream model and feature that was derived from that dataset?
- AA data retention schedule that specifies how long each category of training data is kept before deletion
- BA consent management platform that records the permissions each data subject has granted for processing
- CData lineage records that trace each dataset forward through transformations into the features and model versions derived from it Correct
- DA model registry that stores the performance metrics and approval status of each deployed model version
Why A is wrong: A retention schedule is tempting because it governs deletion timelines, but it states when data should be removed rather than tracing which models and features were built from a specific dataset, so it cannot identify the affected downstream artefacts.
Why B is wrong: Consent management is relevant to lawful basis and is tempting given the problem arose from collection, but it tracks individual permissions rather than the flow of data into derived models, so it does not reveal what was trained on the dataset.
Why C is correct: Lineage records the path data takes through the pipeline, so following the affected dataset forward reveals every feature, training run and model version derived from it, which is exactly what the team needs to scope the remediation.
Why D is wrong: A model registry is tempting because it inventories deployed models, but it catalogues models and their metrics without linking them to the specific upstream datasets used, so by itself it cannot trace which models depend on the tainted source.