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

Amazon BDS-C00 Exam - Topic 9 Question 96 Discussion

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

A company has several teams of analytics. Each team of analysts has their own cluster. The teams need to run SQL queries using Hive, Spark-SQL and Presto with Amazon EMR. The company needs to enable a centralized metadata layer to expose the Amazon S3 objects as tables to the analysts.

Which approach meets the requirement for a centralized metadata layer?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Felicitas
3 months ago
D seems interesting, but not sure if it meets all requirements.
upvoted 0 times
...
Novella
3 months ago
Wait, can we really use DynamoDB for this? Sounds odd.
upvoted 0 times
...
Jody
3 months ago
I thought B could work too, but maybe not as well as A.
upvoted 0 times
...
Stephen
4 months ago
Totally agree, A makes the most sense here!
upvoted 0 times
...
Lawana
4 months ago
A is the best choice for a centralized metadata layer.
upvoted 0 times
...
Rodney
4 months ago
I vaguely remember something about naming schemes and partition discovery in S3, but I’m not confident if that’s the right approach for a centralized metadata layer.
upvoted 0 times
...
Judy
4 months ago
I feel like s3distcp was mentioned in our study sessions, but I’m uncertain about how the outputManifest option fits into this scenario.
upvoted 0 times
...
Brock
4 months ago
I think option B sounds familiar; changing the Hive Metastore to RDS was something we practiced, but I can't recall if it was the best choice for centralization.
upvoted 0 times
...
Micah
5 months ago
I remember we discussed using EMRFS for consistent views, but I'm not entirely sure how it integrates with DynamoDB for metadata.
upvoted 0 times
...
Janet
5 months ago
I'm leaning towards Option D with the automatic partition discovery from S3. That seems like it would be the most scalable and flexible approach for exposing the S3 objects as tables.
upvoted 0 times
...
Mona
5 months ago
Option A with the EMRFS consistent view and a common DynamoDB table sounds like a good fit. That would provide a consistent way for the different teams to access the metadata across their clusters.
upvoted 0 times
...
Stanton
5 months ago
Hmm, I'm a bit confused by the different options here. I'll need to think through the pros and cons of each approach to determine which one is the most suitable for a centralized metadata layer.
upvoted 0 times
...
Leota
5 months ago
This seems like a straightforward question about setting up a centralized metadata layer. I think the key is to find the approach that best meets the requirement of exposing the Amazon S3 objects as tables to the analysts.
upvoted 0 times
...
Felicidad
5 months ago
Okay, I remember learning about this in class. I believe the key is that ISO 26000 is a guidance standard, not a certification standard like ISO 9001 or 14001. So the answer is C.
upvoted 0 times
...
Idella
5 months ago
I'm leaning towards unit testing as the most effective option. Thorough unit testing can catch a lot of defects early in the development process before they propagate further. The other testing approaches are important too, but unit testing is really the foundation.
upvoted 0 times
...
Tien
9 months ago
Ah, the age-old battle of centralized metadata versus distributed metadata. It's like trying to herd cats - you just never know which way they're going to go.
upvoted 0 times
...
Art
9 months ago
You know, if they really want to get creative, they could try creating a centralized metadata layer using interpretive dance and semaphore flags. That would definitely be a unique approach!
upvoted 0 times
Rima
8 months ago
Yeah, I think that option would provide the necessary centralized metadata layer while still being practical and efficient.
upvoted 0 times
...
Denae
8 months ago
I think option A) EMRFS consistent view with a common Amazon DynamoDB table would be the best approach for a centralized metadata layer.
upvoted 0 times
...
Shaun
9 months ago
I agree, it's definitely a unique approach, but I think we should stick to more traditional methods for this task.
upvoted 0 times
...
Jose
9 months ago
That's an interesting idea, but I don't think interpretive dance and semaphore flags would work for creating a centralized metadata layer.
upvoted 0 times
...
...
Carissa
9 months ago
The naming scheme support with automatic partition discovery from Amazon S3 sounds like a convenient solution, but I'm not sure if it would offer the same level of control and consistency as the EMRFS approach.
upvoted 0 times
...
Shawnee
10 months ago
s3distcp with the outputManifest option to generate RDS DDL seems like an interesting approach, but I'm not sure if it would provide the same level of centralization as the EMRFS consistent view.
upvoted 0 times
Coral
9 months ago
C) s3distcp with the outputManifest option to generate RDS DDL
upvoted 0 times
...
Jeanice
9 months ago
B) Bootstrap action to change the Hive Metastore to an Amazon RDS database
upvoted 0 times
...
Gerald
9 months ago
A) EMRFS consistent view with a common Amazon DynamoDB table
upvoted 0 times
...
...
Marva
10 months ago
Bootstrapping the Hive Metastore to an Amazon RDS database could also work, but it might add more complexity to the setup and maintenance.
upvoted 0 times
Lai
8 months ago
D) naming scheme support with automatic partition discovery from Amazon S3
upvoted 0 times
...
Lacresha
9 months ago
B) Bootstrap action to change the Hive Metastore to an Amazon RDS database
upvoted 0 times
...
Myra
9 months ago
A) EMRFS consistent view with a common Amazon DynamoDB table
upvoted 0 times
...
...
Barrie
10 months ago
The use of EMRFS consistent view with a common Amazon DynamoDB table seems like a straightforward approach to meet the requirement for a centralized metadata layer. It should provide a consistent view of the Amazon S3 objects across the different teams.
upvoted 0 times
Willis
9 months ago
I agree, it would make it easier for all teams to access the data
upvoted 0 times
...
Isreal
9 months ago
That sounds like a good solution for centralized metadata
upvoted 0 times
...
Arthur
10 months ago
A) EMRFS consistent view with a common Amazon DynamoDB table
upvoted 0 times
...
...
Barrett
11 months ago
But wouldn't using a common DynamoDB table provide a more centralized metadata layer for the analysts to access?
upvoted 0 times
...
Melissia
11 months ago
I disagree, I believe option D) naming scheme support with automatic partition discovery from Amazon S3 is more efficient.
upvoted 0 times
...
Barrett
11 months ago
I think option A) EMRFS consistent view with a common Amazon DynamoDB table is the best approach.
upvoted 0 times
...

Save Cancel