Practice federated governance vocabulary: global vs. local governance, computational policies, governance by design, federated data catalog, and platform vs. domain team roles.
0 / 5 completed
1 / 5
What does 'computational governance policies' mean in a data mesh context?
Computational governance policies are governance rules expressed as code and automatically enforced — for example, a policy that every data product must have a declared schema and owner, checked programmatically rather than manually.
2 / 5
A team says 'The platform team sets standards; domain teams execute.' What governance model does this describe?
This describes federated governance — the platform or central team defines global interoperability standards and policies, while individual domain teams are responsible for implementing those standards within their data products.
3 / 5
What is a 'federated data catalog' in data mesh?
A federated data catalog combines domain-owned metadata (each team publishes their own data product descriptions) with a unified discovery interface, so consumers can find data products across all domains without central control.
4 / 5
What is the difference between 'global governance' and 'local governance' in data mesh?
Global governance covers standards that enable interoperability across the mesh — like schema formats, security classifications, and SLA definitions. Local governance is each domain's responsibility — their data quality rules, transformation logic, and product-specific policies.
5 / 5
What does 'governance by design' mean?
'Governance by design' means governance is built into the platform and product standards from the start — rather than applied retroactively — so data products are compliant by default through the infrastructure and tooling they use.