Data governance requires precise, formal language. These exercises cover the collocations data engineers, analytics engineers, and compliance teams use when defining ownership, enforcing quality, and managing data lineage.
0 / 5 completed
1 / 5
The data council was established to ___ for each critical dataset in the warehouse.
Define data ownership is the standard data governance collocation for formally establishing who is responsible for a dataset. 'Define' implies creating a clear, documented accountability model. 'Assign' focuses on allocation; 'set' and 'create' are less precise in governance contexts.
2 / 5
The analytics engineering team introduced dbt tests and Great Expectations checks to ___ across all pipelines.
Enforce data quality is the standard data governance collocation for systematically applying quality rules and constraints using automated checks. 'Enforce' implies automated, non-negotiable standards. 'Ensure' and 'maintain' are also common; 'improve' describes the outcome rather than the mechanism.
3 / 5
The data team was tasked with using Datahub to ___ so analysts could discover and understand datasets.
Build a data catalog is the standard data governance collocation for constructing a searchable metadata repository. 'Build' conveys the engineering investment required to create a functional catalog with ingestion pipelines and UI. 'Create' is also used; 'make' is informal; 'develop' is acceptable but less common.
4 / 5
The compliance team required the platform to ___ from source systems to the reporting layer.
Manage data lineage is the data governance collocation for overseeing the end-to-end tracking of data as it flows through systems. 'Manage' implies both capturing and maintaining lineage information. 'Track' emphasises monitoring; 'record' and 'document' imply one-time capture rather than ongoing management.
5 / 5
Role-based access controls were implemented to ___ to sensitive customer records across all data platforms.
Govern access is the formal data governance collocation for applying policy-driven oversight to who can view or modify data. 'Govern' implies a structured, policy-based framework rather than ad-hoc controls. 'Control' and 'manage' are close alternatives; 'restrict' implies only limiting, not the full governance lifecycle.