Data mesh (Zhamak Dehghani) is a response to the bottlenecks of centralized data teams. Instead of one central team owning a monolithic warehouse/lake, ownership is decentralized to the domain teams who understand the data best. It rests on four principles: domain ownership, data as a product, a self-serve data platform, and federated computational governance. The shift is as much organizational as technical — moving from a central data team that becomes a bottleneck to domain-aligned ownership at scale.
2 / 5
What does "data as a product" mean in data mesh?
Data as a product means each domain treats the data it publishes as a first-class product serving internal consumers. A good data product is discoverable (findable in a catalog), addressable, trustworthy (with quality SLAs and freshness guarantees), self-describing (documented schema and semantics), and interoperable (standardized formats). It has a product owner accountable for its quality and roadmap. This reframes data from a neglected exhaust of operations into something teams deliberately design, document, and maintain for their consumers.
3 / 5
What is federated computational governance in data mesh?
Federated computational governance resolves the tension between domain autonomy and organization-wide consistency. A federation of domain representatives defines global policies — privacy, security, interoperability standards, naming conventions — while domains retain autonomy over their own data products. Crucially, governance is computational: rules are encoded into the platform and enforced automatically (policy-as-code, automated quality checks, access controls) rather than relying on manual review boards. This lets governance scale without becoming the bottleneck that data mesh exists to eliminate.
4 / 5
What is a data contract in modern data engineering?
A data contract formalizes the interface between a data producer and its consumers, much like an API contract. It specifies the schema, field semantics, allowed values, freshness/quality SLAs, and ownership. Critically, it is enforced: CI checks validate that a producer's change does not violate the contract, catching breaking changes (a dropped column, a type change) before they silently break downstream pipelines and dashboards. Data contracts are a key enabler of data-as-a-product, giving consumers stable guarantees and producers clear expectations.
5 / 5
What is a data SLO (or data SLA) for a data product?
A data SLO applies reliability-engineering thinking to data products. Just as a service has latency/availability SLOs, a data product commits to measurable guarantees: freshness (how recent the data is), completeness (no missing partitions), accuracy/validity (rows pass quality checks), and availability. Consumers can depend on these guarantees, and breaches trigger alerts and accountability. This makes data quality a tracked, owned commitment rather than a vague hope — essential for treating data as a trustworthy product.
What does the "Data Mesh Principles" vocabulary exercise cover?
This exercise tests real IT vocabulary related to data mesh principles through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.