Practice data mesh domain ownership vocabulary: end-to-end ownership, ownership transfer, domain boundaries, accountability, and SLA ownership.
0 / 5 completed
1 / 5
A data mesh principle states 'The team owns the data product end-to-end.' What does end-to-end ownership include?
End-to-end data product ownership means the domain team is responsible for the entire lifecycle — not just the pipeline. They own quality, freshness, schema versioning, documentation, consumer support, and the SLA. This is analogous to a software team owning their microservice end-to-end.
2 / 5
A project plan mentions 'data product ownership transfer.' When does this occur and what must be transferred?
Data product ownership transfer is a formal process — the receiving team must understand the data product's full context: how it's built, what SLAs are committed to, who the consumers are, what the operational procedures are, and what technical debt exists. Incomplete transfers lead to SLA breaches.
3 / 5
Your domain design doc says 'The domain boundary defines what data belongs to this team.' How is a data mesh domain boundary typically defined?
In data mesh, domain boundaries follow the business domain model — just like in domain-driven design. The Orders domain team owns order data; the Customer domain team owns customer data. Boundaries are defined by business capabilities, not by technical infrastructure or organizational structure.
4 / 5
A governance review asks 'Who is accountable for the data product SLA?' In data mesh, who owns the SLA?
In data mesh, SLA accountability belongs to the producing domain team — not a central data engineering team. This decentralized accountability is what incentivizes domain teams to prioritize data quality and pipeline reliability, treating their data product as a real product.
5 / 5
A data mesh design review flags 'a data product that spans multiple domain boundaries.' Why is this a problem?
When a data product spans domain boundaries, ownership becomes ambiguous — multiple teams share accountability but none feels fully responsible. This leads to finger-pointing when SLAs breach, slower schema evolution, and unclear consumer support. Data mesh principles favor clear, single-domain ownership.