Answer-first summary for fast verification
Answer: Configure a Hive metastore in Amazon EMR. Migrate the existing on-premises Hive metastore into Amazon EMR. Use AWS Glue Data Catalog to store the company's data catalog as an external data catalog.
Option B is CORRECT because it involves configuring a Hive metastore in Amazon EMR and migrating the existing on-premises Hive metastore into Amazon EMR. Then, using AWS Glue Data Catalog to store the company's data catalog as an external data catalog provides a serverless and cost-effective solution. AWS Glue Data Catalog integrates well with Amazon EMR and other AWS services, ensuring the data catalog is managed in a scalable and cost-efficient manner.
Author: Ritesh Yadav
Ultimate access to all questions.
Question 46/60
A company is planning to migrate on-premises Apache Hadoop clusters to Amazon EMR. The company also needs to migrate a data catalog into a persistent storage solution.
The company currently stores the data catalog in an on-premises Apache Hive metastore on the Hadoop clusters. The company requires a serverless solution to migrate the data catalog.
Which solution will meet these requirements MOST cost-effectively?
A
Use AWS Database Migration Service (AWS DMS) to migrate the Hive metastore into Amazon S3. Configure AWS Glue Data Catalog to scan Amazon S3 to produce the data catalog.
B
Configure a Hive metastore in Amazon EMR. Migrate the existing on-premises Hive metastore into Amazon EMR. Use AWS Glue Data Catalog to store the company's data catalog as an external data catalog.
C
Configure an external Hive metastore in Amazon EMR. Migrate the existing on-premises Hive metastore into Amazon EMR. Use Amazon Aurora MySQL to store the company's data catalog.
D
Configure a new Hive metastore in Amazon EMR. Migrate the existing on-premises Hive metastore into Amazon EMR. Use the new metastore as the company's data catalog.
No comments yet.