How Does AWS Glue Data Catalog Centralize Hive Metadata for EMR and Athena?
Short answer
C Use the AWS Glue Data Catalog as the managed, Hive-compatible central metadata repository for EMR and Athena, minimizing custom development.
Question
Key Takeaways
The test is recognizing a shared, managed Hive-compatible catalog for Athena and EMR; the trap is picking a self-managed Hive metastore on EMR or RDS because it sounds closer to the existing Hive setup.
The AWS Glue Data Catalog is the managed, Hive-compatible central metadata repository that both Amazon EMR and Athena can use. This page establishes why option C minimizes development effort when importing Hive table metadata into a shared catalog.
Common mistake: Many learners choose a Hive metastore on an EMR cluster (B) since the source metadata is Apache Hive, but that still requires managing a separate metastore and does not provide Athena's native shared-catalog path.
Expert Analysis
Why the Answer Is Correct
The AWS Glue Data Catalog is a managed, Hive-compatible metadata repository that Amazon Athena uses natively and Amazon EMR can be configured to use as its metastore. That means table schemas and properties exposed to EMR/Hive workloads can also be discovered by Athena without building a custom catalog service. Importing existing Hive metadata into the Glue Data Catalog can be handled through managed crawlers or standard metastore migration approaches, which keeps development effort low. The central repository remains shared and serverless rather than tied to a single EMR cluster. This directly satisfies the "least development effort" constraint.
Why the Other Options Are Wrong
A is wrong because Apache Ranger is primarily an authorization, auditing, and policy tool for Hadoop ecosystems; it does not serve as the central table metadata repository for Athena. B is wrong because a Hive metastore on an EMR cluster is cluster-bound infrastructure that must be managed, and it does not give Athena the same native shared catalog experience. D is wrong because running a metastore on Amazon RDS for MySQL shifts operational and integration work to the data engineer, increasing effort compared with the managed Glue Data Catalog. None of these provides the same straightforward EMR-plus-Athena catalog integration.
Community Comment Notes
The community consensus strongly favors the AWS Glue Data Catalog: every recorded vote selects C, and vic614 simply notes "Data Catalog." rralucard_ links an AWS Big Data blog and argues that Glue is designed as a "central metadata repository" that integrates with EMR and Athena. Felix_G likewise emphasizes that option C "requires the least development effort" for the shared repository requirement. These comments align with the exam's emphasis on managed AWS integration rather than self-managed metastores.
Official Reference
- https://docs.aws.amazon.com/glue/latest/dg/catalog-and-crawler.html
- https://docs.aws.amazon.com/athena/latest/ug/data-sources-glue.html
These links open the official vendor documentation in a new tab.
Exam Strategy
When Athena appears with EMR and a central Hive-compatible catalog, eliminate self-managed Hive/RDS metastores and look for the managed shared catalog. The phrase "LEAST development effort" is the signal for AWS Glue Data Catalog.
Frequently Asked Questions
Why is a Hive metastore on an EMR cluster not the least-effort choice?
Does Apache Ranger replace the AWS Glue Data Catalog as the metadata repository?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 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 3
-
rralucard_ 👍 6 Answered Chttps://aws.amazon.com/blogs/big-data/metadata-classification-lineage-and-discovery-using-apache-atlas-on-amazon-emr/ Option C, using the AWS Glue Data Catalog, is the best solution to meet the requirements with the least development effort. The AWS Glue Data Catalog is designed to be a central metadata repository that can integrate with various AWS services including EMR and Athena, providing a managed and scalable solution for metadata management with built-in Hive compatibility.
-
Felix_G 👍 2Option C, using the AWS Glue Data Catalog, requires the least development effort to meet the requirements for a central metadata repository accessed from EMR and Athena.
-
vic614 👍 1 Answered CData Catalog.
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 →