Which AWS Services Implement a Data Mesh with Centralized Governance?
Short answer
BE Use Amazon S3 for data storage and Amazon Athena for data analysis, with AWS Lake Formation providing centralized data governance and access control.
Question
Key Takeaways
The question tests whether you can map data mesh building blocks to storage, analytics, and centralized governance; the trap is choosing Glue DataBrew because it shares the Glue brand but is a data-preparation tool, not a governance layer.
A data mesh on AWS is built with Amazon S3 as the scalable storage layer, Athena for serverless analysis, and Lake Formation for centralized governance and access control. This page confirms why options B and E are correct and why DataBrew, Aurora, RDS, and EMR do not satisfy the stated requirements.
Common mistake: The most common wrong answer is C: AWS Glue DataBrew sounds governance-adjacent because it is in the Glue family, but it is a visual data-preparation service, while Lake Formation provides the centralized access control and governance the scenario requires.
Expert Analysis
Why the Answer Is Correct
A data mesh requires domain-oriented data storage, a query and analytics layer, and centralized governance and access control. Amazon S3 is the durable, scalable storage layer for a data lake, and Athena provides serverless query over S3, which fits the analysis requirement without provisioning a cluster. AWS Glue Data Catalog can catalog S3 data, while Lake Formation provides centralized permissions, fine-grained access control, and governance across the lake. Together B and E complete the architecture alongside Glue ETL.
Why the Other Options Are Wrong
A uses Aurora and a provisioned Redshift cluster; Aurora is relational and OLTP-oriented, and a provisioned Redshift cluster is not the serverless analytics layer described, while neither option addresses centralized governance. C wrongly casts Glue DataBrew as governance and access control; as alexua noted, "AWS Glue DataBrew is a visual data preparation tool" for cleaning and normalizing data. D uses RDS and EMR; RDS is relational and EMR is a big-data processing framework, but the pair still leaves centralized governance and access control unaddressed. B and E are the only pair that explicitly covers storage, analysis, and centralized governance in the scenario.
Community Comment Notes
Learners overwhelmingly landed on B and E, with milofficial summarizing the exam heuristic as "the keyword data mesh means S3, the keyword data governance means LakeFormation". alexua reinforced the elimination of DataBrew by describing it as visual data preparation rather than governance. ninomfr64 added a real-world caveat that DataZone or newer unified tooling may be used in practice, but for this exam scenario S3, Athena, and Lake Formation align with the stated services. The consensus is useful context, but the answer rests on the requirement mapping, not the vote count.
Official Reference
- https://docs.aws.amazon.com/lake-formation/latest/dg/what-is-lake-formation.html
- https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html
- https://docs.aws.amazon.com/athena/latest/ug/what-is.html
These links open the official vendor documentation in a new tab.
Exam Strategy
When a data mesh question pairs Glue with governance, separate the three asks: storage, analytics, and centralized permissions. S3 plus Athena plus Lake Formation is the canonical AWS data-lake trio; reject Glue DataBrew unless the stem explicitly mentions visual data preparation or cleaning.
Frequently Asked Questions
Why is AWS Glue DataBrew wrong for centralized governance?
Why are Aurora and Amazon RDS not the storage layer in this data mesh?
Community Votes
100% of anonymous learners picked answer BE. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 12 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 12
-
hsnin 👍 7The answer is B and E. The data mesh implementation uses Amazon S3 and Athena for data storage and analysis, and AWS Lake Formation for centralized data governance and access control. When combined with AWS Glue, you can efficiently manage your data.
-
milofficial 👍 4Textbook question, the keyword data mesh means S3, the keyword data governance means LakeFormation
-
Josa2 👍 3Sometimes I think a public community thread uses us to calibrate the right answers hehehe, by the goal statement and the services outlines and objectives there are no way the answer be different then B,E
-
TonyStark0122 👍 2BE Given the requirements for implementing a data mesh architecture with centralized data governance, data analysis, and data access control, the two better choices from the options provided would be: B. Use Amazon S3 for data storage. Use Amazon Athena for data analysis. E. Use AWS Lake Formation for centralized data governance and access control.
-
alexua 👍 2B and E . C - is not correct "AWS Glue DataBrew is a visual data preparation tool that makes it easier for data analysts and data scientists to clean and normalize data to prepare it for analytics and machine learning (ML)"
Show 7 more comments
-
pypelyncar 👍 1A: Cost-effective storage: Amazon S3 is a highly scalable and cost-effective object storage service perfect for storing large datasets commonly found in financial institutions. Centralized data lake: S3 acts as the central data lake where all data from different domains can reside in its raw or processed form. Easy data access: Athena provides a serverless interactive query service that allows data analysts to directly query data stored in S3 using standard SQL. This simplifies data exploration and analysis without managing servers. B: Data governance: Lake Formation helps establish data ownership, access control, and lineage for data products within the data mesh. It ensures data quality, security, and compliance with regulations. Fine-grained access control: Lake Formation allows you to define granular access policies for each data domain, ensuring only authorized users can access specific data sets. This aligns with the need for centralized control in a data mesh.
-
ninomfr64 👍 1S3 (storage) LakeFormation (governance) Athena (analytics) can be used to implement data mesh. In real life you would use DataZone or nowadays SageMaker Unified Studio
-
Shubham1989 👍 1S3 is best storage for data lake, and AWS lake formation is best for management.
-
nanaw770 👍 2BE are correct answer.
-
Fredrik1 👍 1Must be B and E
-
minhtien1707 👍 1i thing so
-
Alcee 👍 1B and E
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →