🕸️ Data Mesh Vocabulary
0 / 29 completed
1 / 29
Scenario: "The organisation is adopting a data mesh architecture." What is the core principle of data mesh?
Data mesh (Zhamak Dehghani) — 4 principles: Domain ownership, Data as a product, Self-serve data platform, Federated computational governance. vs. centralised lake: that model creates a bottleneck at the central data team.
Key vocab: domain ownership, data as a product, data mesh principles, decentralised data architecture.
Key vocab: domain ownership, data as a product, data mesh principles, decentralised data architecture.
2 / 29
Scenario: "The ecommerce domain is publishing a 'Customer Orders' data product." What makes something a data product vs. a database table?
Data product characteristics (Dehghani): discoverable (in catalog), addressable (stable endpoint), self-describing, trustworthy (quality SLA), interoperable.
Key vocab: data product, data product owner, consumer-grade data, data catalog registration.
Key vocab: data product, data product owner, consumer-grade data, data catalog registration.
3 / 29
Scenario: "The platform team provides self-serve data infrastructure." What does this mean in a data mesh context?
Self-serve platform enables domain autonomy at scale. A domain team can onboard a new data product without central team involvement. Platform abstracts infrastructure complexity.
Key vocab: self-serve data platform, domain autonomy, platform-enabled onboarding, data product templates.
Key vocab: self-serve data platform, domain autonomy, platform-enabled onboarding, data product templates.
4 / 29
Scenario: "The data mesh governance model is federated." What does federated computational governance mean?
Federated governance: global = interoperability standards; local = domain-specific business rules. "Computational": embedded in the platform (automated policy enforcement, not manual approval workflows).
Key vocab: federated governance, global standards vs. local policy, computational policy enforcement, governance without bottleneck.
Key vocab: federated governance, global standards vs. local policy, computational policy enforcement, governance without bottleneck.
5 / 29
Scenario: "Migration from centralised data warehouse to data mesh is in progress." What is the most common challenge?
Data mesh is primarily an organisational challenge, not technology. Requires: domain teams with data engineering skills, product mindset for data, new accountability model, change management for data quality culture.
Key vocab: organisational data ownership, data product thinking, cultural shift, operating model change.
Key vocab: organisational data ownership, data product thinking, cultural shift, operating model change.
6 / 29
Reviewer: 'I'm seeing a lot of raw event data flowing into this stream. It feels like we're just dumping everything in without much transformation or context. Should we consider building a domain-specific data product around these events, exposing it with clear schemas and documentation?'
Which of the following best reflects the Reviewer's concern regarding the current approach to event streaming within the Data Mesh?The reviewer's comment highlights the importance of building *data products* within a Data Mesh. A data product encapsulates domain-specific data and its associated metadata—schemas, documentation, quality metrics—making it discoverable and usable by other domains. Simply streaming raw events without this context creates silos and makes it difficult for downstream consumers to effectively utilize the data, which is precisely what a data mesh aims to avoid.
7 / 29
Reviewer: 'I'm seeing a lot of raw event data flowing into this stream. It feels like we're just dumping everything in without much transformation or context. Should we consider building a domain-specific data product around these events, exposing it with clear schemas and documentation?'
Which of the following best reflects the Reviewer's concern regarding the current approach to event streaming within the Data Mesh?The reviewer's comment highlights the importance of building *data products* within a Data Mesh. A data product encapsulates domain-specific data and its associated metadata—schemas, documentation, quality metrics—making it discoverable and usable by other domains. Simply streaming raw events without this context creates silos and makes it difficult for downstream consumers to effectively utilize the data, which is precisely what a data mesh aims to avoid.
8 / 29
Reviewer: 'I'm seeing a lot of raw event data flowing into this stream. It feels like we're just dumping everything in without much transformation or context. Should we consider building a domain-specific data product around these events, exposing it with clear schemas and documentation?'
Which of the following best reflects the Reviewer's concern regarding the current approach to event streaming within the Data Mesh?The reviewer's comment highlights the importance of building *data products* within a Data Mesh. A data product encapsulates domain-specific data and its associated metadata—schemas, documentation, quality metrics—making it discoverable and usable by other domains. Simply streaming raw events without this context creates silos and makes it difficult for downstream consumers to effectively utilize the data, which is precisely what a data mesh aims to avoid.
9 / 29
Reviewer: 'I'm seeing a lot of raw event data flowing into this stream. It feels like we're just dumping everything in without much transformation or context. Should we consider building a domain-specific data product around these events, exposing it with clear schemas and documentation?'
Which of the following best reflects the Reviewer's concern regarding the current approach to event streaming within the Data Mesh?The reviewer's comment highlights the importance of building *data products* within a Data Mesh. A data product encapsulates domain-specific data and its associated metadata—schemas, documentation, quality metrics—making it discoverable and usable by other domains. Simply streaming raw events without this context creates silos and makes it difficult for downstream consumers to effectively utilize the data, which is precisely what a data mesh aims to avoid.
10 / 29
Sarah (Platform Team): "Hey team, we've deployed the new data product catalog service. It allows teams to discover and consume domain-oriented datasets. However, I'm noticing a lot of queries are still hitting the old monolithic reporting database – is anyone actively using the catalog to build new reports?"This question tests understanding of data product consumption. The correct answer reflects the core purpose of a data product catalog – to *enable* teams to actively use domain-specific datasets instead of relying on legacy systems. Options A and C misinterpret the role; B incorrectly describes the shift, and D suggests maintaining outdated practices.
11 / 29
PR Description: "Updated API endpoint /v1/orders/{orderId} to return a JSON payload conforming to the new Data Product Specification v2.0. This includes enhanced fields for delivery tracking and order status, aligning with the 'Shipping' domain data product."This scenario focuses on PR descriptions. The correct answer highlights how an API update aligned with a data product – specifically, exposing domain-specific information. Options A and C are accurate interpretations of data mesh principles, while B is a mischaracterization and D suggests ignoring the context.
12 / 29
Slack Message: @John (Marketing): "Just to clarify, when we say 'data ownership' in the data mesh, it means Marketing team *owns* the raw customer event streams related to campaigns. They're responsible for transforming and exposing those as a data product."This question tests understanding of a critical concept. The correct answer accurately describes domain accountability within a data mesh. Options A and B misinterpret centralized control; C suggests a broader definition of ownership, and D is an inaccurate representation of delegation.
13 / 29
Code Review Comment: 'I'm reviewing this data pipeline. It pulls events from the 'User Activity' domain and writes them directly to a new table in the `analytics_db`. While functional, isn't it better to expose these as a *data product* with a well-defined schema, allowing other domains to consume them?"This scenario tests understanding of exposing raw event streams. The correct answer reflects the core principle of creating data products from raw events – promoting loose coupling and domain-specific access. Options A and B misunderstand the benefits; C describes a key benefit of data mesh, and D is an outdated warehousing approach.
14 / 29
Standup Update: 'Yesterday, we finished migrating the 'Product Catalog' domain to a data mesh. The biggest challenge was ensuring consistent schema evolution across all the newly created data products and managing dependencies between them – it's proving more complex than anticipated.'This question focuses on a realistic challenge. The correct answer accurately captures the core issue – managing schema evolution and dependencies across domains in a distributed environment. Options A, B, and D represent other potential issues but aren't the *primary* challenge highlighted in the standup update.
15 / 29
Sarah (Platform Team): "Hey team, we've deployed the new data product catalog service. It allows teams to discover and consume domain-oriented datasets. However, I'm noticing a lot of queries are still hitting the old monolithic reporting database – is anyone actively using the catalog to build new reports?"This question tests understanding of data product consumption. The correct answer reflects the core purpose of a data product catalog – to *enable* teams to actively use domain-specific datasets instead of relying on legacy systems. Options A and C misinterpret the role; B incorrectly describes the shift, and D suggests maintaining outdated practices.
16 / 29
PR Description: "Updated API endpoint /v1/orders/{orderId} to return a JSON payload conforming to the new Data Product Specification v2.0. This includes enhanced fields for delivery tracking and order status, aligning with the 'Shipping' domain data product."This scenario focuses on PR descriptions. The correct answer highlights how an API update aligned with a data product – specifically, exposing domain-specific information. Options A and C are accurate interpretations of data mesh principles, while B is a mischaracterization and D suggests ignoring the context.
17 / 29
Slack Message: @John (Marketing): "Just to clarify, when we say 'data ownership' in the data mesh, it means Marketing team *owns* the raw customer event streams related to campaigns. They're responsible for transforming and exposing those as a data product."This question tests understanding of a critical concept. The correct answer accurately describes domain accountability within a data mesh. Options A and B misinterpret centralized control; C suggests a broader definition of ownership, and D is an inaccurate representation of delegation.
18 / 29
Code Review Comment: 'I'm reviewing this data pipeline. It pulls events from the 'User Activity' domain and writes them directly to a new table in the `analytics_db`. While functional, isn't it better to expose these as a *data product* with a well-defined schema, allowing other domains to consume them?"This scenario tests understanding of exposing raw event streams. The correct answer reflects the core principle of creating data products from raw events – promoting loose coupling and domain-specific access. Options A and B misunderstand the benefits; C describes a key benefit of data mesh, and D is an outdated warehousing approach.
19 / 29
Standup Update: 'Yesterday, we finished migrating the 'Product Catalog' domain to a data mesh. The biggest challenge was ensuring consistent schema evolution across all the newly created data products and managing dependencies between them – it's proving more complex than anticipated.'This question focuses on a realistic challenge. The correct answer accurately captures the core issue – managing schema evolution and dependencies across domains in a distributed environment. Options A, B, and D represent other potential issues but aren't the *primary* challenge highlighted in the standup update.
20 / 29
Sarah (Platform Team): "Hey team, we've deployed the new data product catalog service. It allows teams to discover and consume domain-oriented datasets. However, I'm noticing a lot of queries are still hitting the old monolithic reporting database – is anyone actively using the catalog to build new reports?"This question tests understanding of data product consumption. The correct answer reflects the core purpose of a data product catalog – to *enable* teams to actively use domain-specific datasets instead of relying on legacy systems. Options A and C misinterpret the role; B incorrectly describes the shift, and D suggests maintaining outdated practices.
21 / 29
PR Description: "Updated API endpoint /v1/orders/{orderId} to return a JSON payload conforming to the new Data Product Specification v2.0. This includes enhanced fields for delivery tracking and order status, aligning with the 'Shipping' domain data product."This scenario focuses on PR descriptions. The correct answer highlights how an API update aligned with a data product – specifically, exposing domain-specific information. Options A and C are accurate interpretations of data mesh principles, while B is a mischaracterization and D suggests ignoring the context.
22 / 29
Slack Message: @John (Marketing): "Just to clarify, when we say 'data ownership' in the data mesh, it means Marketing team *owns* the raw customer event streams related to campaigns. They're responsible for transforming and exposing those as a data product."This question tests understanding of a critical concept. The correct answer accurately describes domain accountability within a data mesh. Options A and B misinterpret centralized control; C suggests a broader definition of ownership, and D is an inaccurate representation of delegation.
23 / 29
Code Review Comment: 'I'm reviewing this data pipeline. It pulls events from the 'User Activity' domain and writes them directly to a new table in the `analytics_db`. While functional, isn't it better to expose these as a *data product* with a well-defined schema, allowing other domains to consume them?"This scenario tests understanding of exposing raw event streams. The correct answer reflects the core principle of creating data products from raw events – promoting loose coupling and domain-specific access. Options A and B misunderstand the benefits; C describes a key benefit of data mesh, and D is an outdated warehousing approach.
24 / 29
Standup Update: 'Yesterday, we finished migrating the 'Product Catalog' domain to a data mesh. The biggest challenge was ensuring consistent schema evolution across all the newly created data products and managing dependencies between them – it's proving more complex than anticipated.'This question focuses on a realistic challenge. The correct answer accurately captures the core issue – managing schema evolution and dependencies across domains in a distributed environment. Options A, B, and D represent other potential issues but aren't the *primary* challenge highlighted in the standup update.
25 / 29
Sarah (Platform Team): "Hey team, we've deployed the new data product catalog service. It allows teams to discover and consume domain-oriented datasets. However, I'm noticing a lot of queries are still hitting the old monolithic reporting database – is anyone actively using the catalog to build new reports?"This question tests understanding of data product consumption. The correct answer reflects the core purpose of a data product catalog – to *enable* teams to actively use domain-specific datasets instead of relying on legacy systems. Options A and C misinterpret the role; B incorrectly describes the shift, and D suggests maintaining outdated practices.
26 / 29
PR Description: "Updated API endpoint /v1/orders/{orderId} to return a JSON payload conforming to the new Data Product Specification v2.0. This includes enhanced fields for delivery tracking and order status, aligning with the 'Shipping' domain data product."This scenario focuses on PR descriptions. The correct answer highlights how an API update aligned with a data product – specifically, exposing domain-specific information. Options A and C are accurate interpretations of data mesh principles, while B is a mischaracterization and D suggests ignoring the context.
27 / 29
Slack Message: @John (Marketing): "Just to clarify, when we say 'data ownership' in the data mesh, it means Marketing team *owns* the raw customer event streams related to campaigns. They're responsible for transforming and exposing those as a data product."This question tests understanding of a critical concept. The correct answer accurately describes domain accountability within a data mesh. Options A and B misinterpret centralized control; C suggests a broader definition of ownership, and D is an inaccurate representation of delegation.
28 / 29
Code Review Comment: 'I'm reviewing this data pipeline. It pulls events from the 'User Activity' domain and writes them directly to a new table in the `analytics_db`. While functional, isn't it better to expose these as a *data product* with a well-defined schema, allowing other domains to consume them?"This scenario tests understanding of exposing raw event streams. The correct answer reflects the core principle of creating data products from raw events – promoting loose coupling and domain-specific access. Options A and B misunderstand the benefits; C describes a key benefit of data mesh, and D is an outdated warehousing approach.
29 / 29
Standup Update: 'Yesterday, we finished migrating the 'Product Catalog' domain to a data mesh. The biggest challenge was ensuring consistent schema evolution across all the newly created data products and managing dependencies between them – it's proving more complex than anticipated.'This question focuses on a realistic challenge. The correct answer accurately captures the core issue – managing schema evolution and dependencies across domains in a distributed environment. Options A, B, and D represent other potential issues but aren't the *primary* challenge highlighted in the standup update.
Frequently Asked Questions
What does the "Data Mesh Vocabulary" exercise practise?
Practice data mesh principles: data product, domain ownership, self-serve infrastructure, and federated governance.
How many questions are in this exercise?
This exercise has 29 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Data Contracts category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Data Mesh Vocabulary" part of a larger series?
Yes — it's one exercise in the Data Contracts category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Data Contracts category page for related exercises, or browse the main Exercises hub for other IT English topics.