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

Question

Options

• AUse AWS Database Migration Service (AWS DMS) to migrate the Hive metastore into Amazon
• BConfigure a Hive metastore in Amazon EMR. Migrate the existing on-premises Hive metastore
• CConfigure an external Hive metastore in Amazon EMR. Migrate the existing on-premises Hive
• DConfigure a new Hive metastore in Amazon EMR. Migrate the existing on-premises Hive

• A
  10% (6)
• B
  84% (53)
• C
  5% (3)
• D
  2% (1)

Explanation

https://aws.amazon.com/blogs/big-data/migrate-and-deploy-your-apache-hive-metastore-on- Migrating the Hive metastore into Amazon EMR and using AWS Glue Data Catalog as an external catalog provides a balance between leveraging the scalable and managed services of AWS (like EMR and Glue Data Catalog) and ensuring a smooth transition from the on-premises setup. This approach leverages the serverless nature of AWS Glue Data Catalog, minimizing operational overhead and potentially reducing costs compared to managing database servers.

No community discussion yet for this question.