Data Mesh — Learn free

Self-check

Questions 1–10 of 10

1. What is Data Mesh?
Question 1A. A modern approach to data architecture and governance that emphasises decentralisation and domain-driven ownership of data productsB. A technique for combining data from several web sources into a single viewC. A centralised data warehouse managed by a monolithic data teamD. A disorganised datastore lacking master data, metadata and lineageE. A single database that serves both transactional and analytical workloads
2. Which four key principles does Data Mesh revolve around?
Question 2A. Accuracy, Completeness, Consistency and TimelinessB. Domain-Oriented Decentralisation, Data as a Product, Self-Service Data Infrastructure and Federated GovernanceC. Extraction, Transformation, Loading and VisualisationD. Confidentiality, Integrity, Availability and PrivacyE. Hubs, Links, Satellites and Reference tables
3. In Data Mesh, what does a domain refer to?
Question 3A. A physical database serverB. A cloud region where data is storedC. A specific business area or operational unit, such as marketing, sales or customer serviceD. A single table in the data warehouseE. A regulatory jurisdiction
4. Which of the following is NOT a requirement that Data Mesh places on each data product?
Question 4A. Be discoverable and self-descriptiveB. Have clearly defined APIs for easy accessC. Include documentation, versioning and quality metricsD. Be built and maintained by a central data engineering teamE. Be interoperable with other data products within and across domains
5. What does Federated Governance provide in a Data Mesh?
Question 5A. Complete freedom for each domain with no organisation-wide policiesB. A single central team that approves every data productC. Automatic deletion of short-lived datasetsD. A rule that each domain must use the same modelling techniqueE. Consistency, compliance and quality across the ecosystem by setting global policies that domains implement in contextually appropriate ways
6. Regardless of the modelling technique used, what is described as the hallmark of a data product in a Data Mesh?
Question 6A. InteroperabilityB. Normalisation to third normal formC. Being stored in a single central warehouseD. Being short-lived and purpose-specificE. Being built with dimensional modelling
7. Which types of data asset are given as examples of what is NOT part of a Data Mesh?
Question 7A. Dimensional models and Data Vault modelsB. Short-lived data sets and non-interoperable data assetsC. Data products owned by the marketing domainD. Data products with versioning and quality metricsE. Data pipelines and storage solutions
8. How many Data Meshes can an organisation have?
Question 8A. One per domainB. One per data productC. Only one per organisationD. One per cloud providerE. As many as there are business units
9. Which of the following is NOT listed as a benefit of Data Mesh?
Question 9A. ScalabilityB. Business alignmentC. Faster time to insightD. Lower initial costsE. Flexibility in technology choices
10. Which challenges are listed for implementing Data Mesh?
Question 10A. Data duplication, slow queries and vendor lock-inB. Lack of SQL support, HDFS dependency and row storageC. Missing master data, metadata and lineageD. Fan traps, chasm traps and deep join chainsE. Cultural shift, skill development, complex governance and initial costs