How Does AWS Glue Data Catalog Centralize Hive Metadata for EMR and Athena?

Answer Correct answer: C — Use the AWS Glue Data Catalog as the managed, Hive-compatible central metadata repository for EMR and Athena, minimizing custom development.

A data engineer needs to maintain a central metadata repository that users access through Amazon EMR and Amazon Athena queries. The repository needs to provide the schema and properties of many tables. Some of the metadata is stored in Apache Hive. The data engineer needs to import the metadata from Hive into the central metadata repository. Which solution will meet these requirements with the LEAST development effort?

  1. Use Amazon EMR and Apache Ranger.
  2. Use a Hive metastore on an EMR cluster.
  3. Use the AWS Glue Data Catalog. Correct Answer
  4. Use a metastore on an Amazon RDS for MySQL DB instance.

Community Votes

C
100%

100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

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.

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.

Community Discussion (3 comments)

rralucard_ 👍 6 Selected: C
https://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.
vic614 👍 1 Selected: C
Data Catalog.
Felix_G 👍 2
Option 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.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

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

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?

A Hive metastore on EMR is tied to cluster infrastructure and still needs migration and ongoing management, while EMR and Athena can both use the managed Glue Data Catalog.

Does Apache Ranger replace the AWS Glue Data Catalog as the metadata repository?

No. Ranger is for authorization, auditing, and policies in Hadoop environments; it does not provide Athena's central Hive-compatible table catalog.

More DEA-C01 FAQ →

Related Analysis

Practice All DEA-C01 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DEA-C01 Practice Test →

← Back to DEA-C01 Study Guide