New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Amazon BDS-C00 Exam - Topic 5 Question 124 Discussion

Actual exam question for Amazon's BDS-C00 exam
Question #: 124
Topic #: 5
[All BDS-C00 Questions]

An organization is currently using an Amazon EMR long-running cluster with the latest Amazon EMR release for analytic jobs and is storing data as external tables on Amazon S3.

The company needs to launch multiple transient EMR clusters to access the same tables concurrently, but the metadata about the Amazon S3 external tables are defined and stored on the long-running cluster.

Which solution will expose the Hive metastore with the LEAST operational effort?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Malika at Nov 22, 2025, 07:07 AM

Limited Time Offer

25%

Off

Get Premium BDS-C00 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Penney
5 hours ago
D seems like the easiest option for managing metadata.
upvoted 0 times
...
Mel
5 days ago
Hive metastore? More like Hive headache, amirite?
upvoted 0 times
...
Dorsey
11 days ago
A) DynamoDB? Really? Isn't that overkill for a Hive metastore?
upvoted 0 times
...
Dominque
16 days ago
D) AWS Glue Data Catalog is the way to go. Managed metastore FTW!
upvoted 0 times
...
Lizbeth
21 days ago
C) Using Apache Derby on an EC2 instance? That's a bit old-school, don't you think?
upvoted 0 times
...
Chantell
26 days ago
I vaguely remember that using RDS for the Hive metastore was mentioned in a case study, but I thought it required more operational effort.
upvoted 0 times
...
Chanel
1 month ago
I feel like exporting to DynamoDB could work, but it seems like it might involve more setup than just using Glue.
upvoted 0 times
...
Shawnta
1 month ago
I think option D sounds familiar from our practice questions, but I can't recall the details about Glue's integration with EMR.
upvoted 0 times
...
Audrie
1 month ago
I remember we discussed using AWS Glue for managing metadata, but I'm not sure if it's the best option here.
upvoted 0 times
...
Melissia
2 months ago
I'm a bit unsure about the differences between the DynamoDB, RDS, and Derby options. I'll need to research those in more detail to determine which one is truly the least operationally intensive.
upvoted 0 times
...
Terina
2 months ago
I'm feeling pretty confident about this one. I think the AWS Glue Data Catalog solution is the way to go, as it seems the most seamless integration with the existing setup.
upvoted 0 times
...
Shaun
2 months ago
Okay, I think I have a strategy. I'll focus on understanding the pros and cons of each metastore option and how they integrate with the existing long-running EMR cluster and S3 data.
upvoted 0 times
...
Jeannine
2 months ago
Agreed! Glue Data Catalog is serverless too. Less hassle.
upvoted 0 times
...
Joseph
2 months ago
B) Storing the metastore on Amazon RDS makes sense for a more robust and scalable solution.
upvoted 0 times
...
Maryrose
2 months ago
D) Seems like the easiest option to expose the Hive metastore with minimal effort.
upvoted 0 times
...
Vicki
3 months ago
I think option D is the best. AWS Glue is easy to set up.
upvoted 0 times
...
Shawnee
3 months ago
Hmm, I'm a bit confused about the different metastore options. I'll need to review the details of each solution to determine which one has the least operational effort.
upvoted 0 times
...
Kami
3 months ago
This looks like a tricky question. I'll need to carefully consider the options and think through the operational effort required for each.
upvoted 0 times
Caitlin
3 months ago
True, but Glue seems to integrate well with EMR.
upvoted 0 times
...
...

Save Cancel