Data Product Design — Vocabulary and Language
Learn vocabulary for designing and describing Data Mesh data products.
0 / 25 completed
1 / 25
What is a 'data product' in Data Mesh?
A data product is a domain-owned, self-contained unit with: data assets, code to produce them, infrastructure, output ports (APIs, files, streams), and quality SLAs — treated like a software product.
2 / 25
What is an 'output port' of a data product?
An output port is the data product's consumer-facing interface: a SQL table, a REST API, a Kafka topic, or a file share. The contract between the data product and consumers is defined at the output port.
3 / 25
What is a 'data product specification' (or data product contract)?
A data product specification defines: the data product's owner, schema of each output port, SLAs (freshness, availability), quality expectations, and access control — enabling consumers to evaluate and use the product.
4 / 25
What does 'data product SLA' refer to in Data Mesh?
A data product SLA is the team's commitment to consumers about data quality characteristics: freshness (how recent is the data?), availability (uptime of output ports), completeness, and accuracy.
5 / 25
What is 'discoverability' of a data product?
Discoverability means potential consumers can find the data product in a catalogue, understand its schema and purpose, and evaluate its suitability — without needing to ask the domain team directly.
6 / 25
During a code review of the new `UserProfileService`, Sarah mentions needing to 'normalize' the data before presenting it in the API response. Mark replies: 'Sounds good! Should we use a standard transformation pipeline like the one for Customer Data?'
Which of the following best describes what Sarah *actually* means?
Sarah's use of 'normalize' refers to standardizing the structure and format of the data – typically ensuring consistent data types (e.g., string vs. integer) and formats (dates, addresses). This is crucial for downstream systems to easily consume and interpret the data without requiring complex transformations. Mark's suggestion of a pipeline focuses on ETL, which isn't necessarily what Sarah intended in this context.
7 / 25
During a code review of the new `UserProfileService`, David suggests adding a 'data quality rule' to ensure all email addresses are validated before they're stored. Emily responds: 'That's a good idea! We should implement it as a validation step within the service itself.'
Which of the following best describes what Emily *actually* means?
Emily is advocating for integrating data quality checks directly within the `UserProfileService`. This approach aligns with building resilient data products by ensuring immediate validation at the point of entry. The other options represent more complex or decoupled solutions that might introduce unnecessary latency or operational overhead – a core principle to avoid in Data Product Design.
8 / 25
Mark and David are discussing improvements to the new `OrderProcessingService`. Mark says, 'We need to ensure all order data is consistently formatted before it's sent to the fulfillment system.' David replies, 'I can create a mapping layer that handles those transformations on-the-fly.' Which of the following best describes what David *actually* means?
David is referring to a common design pattern: applying transformations close to the source of truth (the `OrderProcessingService`) rather than creating a separate, isolated layer. This approach promotes reusability, reduces dependencies, and simplifies maintenance – aligning with principles of loosely coupled systems architecture often discussed in software development. Option A describes a manual process which is generally undesirable; option C accurately reflects a component-based solution for dynamic transformation within the service itself.9 / 25
Mark and David are discussing the design of a new API for a product recommendation engine. Mark says, 'We need to ensure that user preferences – things like past purchases, browsing history, and demographic data – are consistently represented across all our internal services before they're used to generate recommendations.' David replies: 'I can create a unified schema layer that handles the transformation of these diverse data sources into a common format for consumption by the recommendation algorithms.'
Which of the following best describes what David *actually* means?David is advocating for a transformation layer – often referred to as an ETL (Extract, Transform, Load) process. This involves taking diverse and potentially inconsistent data sources (user preferences in various formats across different services) and converting them into a standardized format suitable for the recommendation engine. He's not suggesting creating isolated silos or duplicating data; rather, he's proposing a central mechanism for data harmonization.
10 / 25
During a standup update, Alex reports that the team is working on 'standardizing' the format of user event logs. He explains they're aiming for consistent timestamps and event types across all services. Ben asks, 'So, what are you actually doing – creating a centralized logging system or just cleaning up the existing logs?' Alex replies, 'We're building a transformation layer to convert everything into a common JSON format before sending it to the analytics pipeline.' Which of the following best describes what Alex *actually* means?
Alex isn't just 'cleaning up' logs; he's establishing a consistent data structure. The term 'standardizing' implies a systematic transformation process – creating a transformation layer to convert disparate log formats into a unified JSON format before ingestion is the key technical action being described. This prepares the data for downstream analytics, addressing the underlying issue of inconsistent event logging.
11 / 25
During a code review of the new `UserProfileService`, Sarah mentions needing to 'normalize' the data before presenting it in the API response. Mark replies: 'Sounds good! Should we use a standard transformation pipeline like the one for Customer Data?'
Which of the following best describes what Sarah *actually* means?
Sarah's use of 'normalize' refers to standardizing the structure and format of the data – typically ensuring consistent data types (e.g., string vs. integer) and formats (dates, addresses). This is crucial for downstream systems to easily consume and interpret the data without requiring complex transformations. Mark's suggestion of a pipeline focuses on ETL, which isn't necessarily what Sarah intended in this context.
12 / 25
During a code review of the new `UserProfileService`, David suggests adding a 'data quality rule' to ensure all email addresses are validated before they're stored. Emily responds: 'That's a good idea! We should implement it as a validation step within the service itself.'
Which of the following best describes what Emily *actually* means?
Emily is advocating for integrating data quality checks directly within the `UserProfileService`. This approach aligns with building resilient data products by ensuring immediate validation at the point of entry. The other options represent more complex or decoupled solutions that might introduce unnecessary latency or operational overhead – a core principle to avoid in Data Product Design.
13 / 25
Mark and David are discussing improvements to the new `OrderProcessingService`. Mark says, 'We need to ensure all order data is consistently formatted before it's sent to the fulfillment system.' David replies, 'I can create a mapping layer that handles those transformations on-the-fly.' Which of the following best describes what David *actually* means?
David is referring to a common design pattern: applying transformations close to the source of truth (the `OrderProcessingService`) rather than creating a separate, isolated layer. This approach promotes reusability, reduces dependencies, and simplifies maintenance – aligning with principles of loosely coupled systems architecture often discussed in software development. Option A describes a manual process which is generally undesirable; option C accurately reflects a component-based solution for dynamic transformation within the service itself.14 / 25
Mark and David are discussing the design of a new API for a product recommendation engine. Mark says, 'We need to ensure that user preferences – things like past purchases, browsing history, and demographic data – are consistently represented across all our internal services before they're used to generate recommendations.' David replies: 'I can create a unified schema layer that handles the transformation of these diverse data sources into a common format for consumption by the recommendation algorithms.'
Which of the following best describes what David *actually* means?David is advocating for a transformation layer – often referred to as an ETL (Extract, Transform, Load) process. This involves taking diverse and potentially inconsistent data sources (user preferences in various formats across different services) and converting them into a standardized format suitable for the recommendation engine. He's not suggesting creating isolated silos or duplicating data; rather, he's proposing a central mechanism for data harmonization.
15 / 25
During a standup update, Alex reports that the team is working on 'standardizing' the format of user event logs. He explains they're aiming for consistent timestamps and event types across all services. Ben asks, 'So, what are you actually doing – creating a centralized logging system or just cleaning up the existing logs?' Alex replies, 'We're building a transformation layer to convert everything into a common JSON format before sending it to the analytics pipeline.' Which of the following best describes what Alex *actually* means?
Alex isn't just 'cleaning up' logs; he's establishing a consistent data structure. The term 'standardizing' implies a systematic transformation process – creating a transformation layer to convert disparate log formats into a unified JSON format before ingestion is the key technical action being described. This prepares the data for downstream analytics, addressing the underlying issue of inconsistent event logging.
16 / 25
During a code review of the new `UserProfileService`, Sarah mentions needing to 'normalize' the data before presenting it in the API response. Mark replies: 'Sounds good! Should we use a standard transformation pipeline like the one for Customer Data?'
Which of the following best describes what Sarah *actually* means?
Sarah's use of 'normalize' refers to standardizing the structure and format of the data – typically ensuring consistent data types (e.g., string vs. integer) and formats (dates, addresses). This is crucial for downstream systems to easily consume and interpret the data without requiring complex transformations. Mark's suggestion of a pipeline focuses on ETL, which isn't necessarily what Sarah intended in this context.
17 / 25
During a code review of the new `UserProfileService`, David suggests adding a 'data quality rule' to ensure all email addresses are validated before they're stored. Emily responds: 'That's a good idea! We should implement it as a validation step within the service itself.'
Which of the following best describes what Emily *actually* means?
Emily is advocating for integrating data quality checks directly within the `UserProfileService`. This approach aligns with building resilient data products by ensuring immediate validation at the point of entry. The other options represent more complex or decoupled solutions that might introduce unnecessary latency or operational overhead – a core principle to avoid in Data Product Design.
18 / 25
Mark and David are discussing improvements to the new `OrderProcessingService`. Mark says, 'We need to ensure all order data is consistently formatted before it's sent to the fulfillment system.' David replies, 'I can create a mapping layer that handles those transformations on-the-fly.' Which of the following best describes what David *actually* means?
David is referring to a common design pattern: applying transformations close to the source of truth (the `OrderProcessingService`) rather than creating a separate, isolated layer. This approach promotes reusability, reduces dependencies, and simplifies maintenance – aligning with principles of loosely coupled systems architecture often discussed in software development. Option A describes a manual process which is generally undesirable; option C accurately reflects a component-based solution for dynamic transformation within the service itself.19 / 25
Mark and David are discussing the design of a new API for a product recommendation engine. Mark says, 'We need to ensure that user preferences – things like past purchases, browsing history, and demographic data – are consistently represented across all our internal services before they're used to generate recommendations.' David replies: 'I can create a unified schema layer that handles the transformation of these diverse data sources into a common format for consumption by the recommendation algorithms.'
Which of the following best describes what David *actually* means?David is advocating for a transformation layer – often referred to as an ETL (Extract, Transform, Load) process. This involves taking diverse and potentially inconsistent data sources (user preferences in various formats across different services) and converting them into a standardized format suitable for the recommendation engine. He's not suggesting creating isolated silos or duplicating data; rather, he's proposing a central mechanism for data harmonization.
20 / 25
During a standup update, Alex reports that the team is working on 'standardizing' the format of user event logs. He explains they're aiming for consistent timestamps and event types across all services. Ben asks, 'So, what are you actually doing – creating a centralized logging system or just cleaning up the existing logs?' Alex replies, 'We're building a transformation layer to convert everything into a common JSON format before sending it to the analytics pipeline.' Which of the following best describes what Alex *actually* means?
Alex isn't just 'cleaning up' logs; he's establishing a consistent data structure. The term 'standardizing' implies a systematic transformation process – creating a transformation layer to convert disparate log formats into a unified JSON format before ingestion is the key technical action being described. This prepares the data for downstream analytics, addressing the underlying issue of inconsistent event logging.
21 / 25
During a code review of the new `UserProfileService`, Sarah mentions needing to 'normalize' the data before presenting it in the API response. Mark replies: 'Sounds good! Should we use a standard transformation pipeline like the one for Customer Data?'
Which of the following best describes what Sarah *actually* means?
Sarah's use of 'normalize' refers to standardizing the structure and format of the data – typically ensuring consistent data types (e.g., string vs. integer) and formats (dates, addresses). This is crucial for downstream systems to easily consume and interpret the data without requiring complex transformations. Mark's suggestion of a pipeline focuses on ETL, which isn't necessarily what Sarah intended in this context.
22 / 25
During a code review of the new `UserProfileService`, David suggests adding a 'data quality rule' to ensure all email addresses are validated before they're stored. Emily responds: 'That's a good idea! We should implement it as a validation step within the service itself.'
Which of the following best describes what Emily *actually* means?
Emily is advocating for integrating data quality checks directly within the `UserProfileService`. This approach aligns with building resilient data products by ensuring immediate validation at the point of entry. The other options represent more complex or decoupled solutions that might introduce unnecessary latency or operational overhead – a core principle to avoid in Data Product Design.
23 / 25
Mark and David are discussing improvements to the new `OrderProcessingService`. Mark says, 'We need to ensure all order data is consistently formatted before it's sent to the fulfillment system.' David replies, 'I can create a mapping layer that handles those transformations on-the-fly.' Which of the following best describes what David *actually* means?
David is referring to a common design pattern: applying transformations close to the source of truth (the `OrderProcessingService`) rather than creating a separate, isolated layer. This approach promotes reusability, reduces dependencies, and simplifies maintenance – aligning with principles of loosely coupled systems architecture often discussed in software development. Option A describes a manual process which is generally undesirable; option C accurately reflects a component-based solution for dynamic transformation within the service itself.24 / 25
Mark and David are discussing the design of a new API for a product recommendation engine. Mark says, 'We need to ensure that user preferences – things like past purchases, browsing history, and demographic data – are consistently represented across all our internal services before they're used to generate recommendations.' David replies: 'I can create a unified schema layer that handles the transformation of these diverse data sources into a common format for consumption by the recommendation algorithms.'
Which of the following best describes what David *actually* means?David is advocating for a transformation layer – often referred to as an ETL (Extract, Transform, Load) process. This involves taking diverse and potentially inconsistent data sources (user preferences in various formats across different services) and converting them into a standardized format suitable for the recommendation engine. He's not suggesting creating isolated silos or duplicating data; rather, he's proposing a central mechanism for data harmonization.
25 / 25
During a standup update, Alex reports that the team is working on 'standardizing' the format of user event logs. He explains they're aiming for consistent timestamps and event types across all services. Ben asks, 'So, what are you actually doing – creating a centralized logging system or just cleaning up the existing logs?' Alex replies, 'We're building a transformation layer to convert everything into a common JSON format before sending it to the analytics pipeline.' Which of the following best describes what Alex *actually* means?
Alex isn't just 'cleaning up' logs; he's establishing a consistent data structure. The term 'standardizing' implies a systematic transformation process – creating a transformation layer to convert disparate log formats into a unified JSON format before ingestion is the key technical action being described. This prepares the data for downstream analytics, addressing the underlying issue of inconsistent event logging.
Frequently Asked Questions
What does the "Data Product Design — Vocabulary and Language" exercise practise?
Learn vocabulary for designing and describing Data Mesh data products.
How many questions are in this exercise?
This exercise has 25 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 Mesh Architecture 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 Product Design — Vocabulary and Language" part of a larger series?
Yes — it's one exercise in the Data Mesh Architecture 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 Mesh Architecture category page for related exercises, or browse the main Exercises hub for other IT English topics.