DAS-C01 · Question #177
A marketing company collects data from third-party providers and uses transient Amazon EMR clusters to process this data. The company wants to host an Apache Hive metastore that is persistent…
The correct answer is A. Use AWS Glue Data Catalog as the metastore. AWS Glue Data Catalog is the ideal managed Hive-compatible metastore. It is serverless, fully managed, persistent, highly available, and can be accessed simultaneously by Amazon EMR, Amazon Athena, Amazon Redshift Spectrum, and other AWS services across multiple accounts via…
Question
A marketing company collects data from third-party providers and uses transient Amazon EMR clusters to process this data. The company wants to host an Apache Hive metastore that is persistent, reliable, and can be accessed by EMR clusters and multiple AWS services and accounts simultaneously. The metastore must also be available at all times. Which solution meets these requirements with the LEAST operational overhead?
Options
- AUse AWS Glue Data Catalog as the metastore
- BUse an external Amazon EC2 instance running MySQL as the metastore
- CUse Amazon RDS for MySQL as the metastore
- DUse Amazon S3 as the metastore
How the community answered
(57 responses)- A91% (52)
- B2% (1)
- C5% (3)
- D2% (1)
Explanation
AWS Glue Data Catalog is the ideal managed Hive-compatible metastore. It is serverless, fully managed, persistent, highly available, and can be accessed simultaneously by Amazon EMR, Amazon Athena, Amazon Redshift Spectrum, and other AWS services across multiple accounts via AWS RAM (Resource Access Manager). It requires zero operational overhead. An EC2 instance running MySQL (B) and Amazon RDS for MySQL (C) both require you to manage availability, backups, scaling, and patching - significantly more operational overhead. Amazon S3 (D) is object storage and cannot function as a Hive metastore.
Topics
Community Discussion
No community discussion yet for this question.