Amazon Exam DAS-C01 Topic 7 Question 89 Discussion

Actual exam question for Amazon's DAS-C01 exam

Question #: 89
Topic #: 7

A company is using an AWS Lambda function to run Amazon Athena queries against a cross-account AWS Glue Data Catalog. A query returns the following error:

HIVE METASTORE ERROR

The error message states that the response payload size exceeds the maximum allowed payload size. The queried table is already partitioned, and the data is stored in an

Amazon S3 bucket in the Apache Hive partition format.

Which solution will resolve this error?

AModify the Lambda function to upload the query response payload as an object into the S3 bucket. Include an S3 object presigned URL as the payload in the Lambda function response.

BRun the MSCK REPAIR TABLE command on the queried table.

CCreate a separate folder in the S3 bucket. Move the data files that need to be queried into that folder. Create an AWS Glue crawler that points to the folder instead of the S3 bucket.

DCheck the schema of the queried table for any characters that Athena does not support. Replace any unsupported characters with characters that Athena supports.

Show Suggested Answer

Suggested Answer: A

by Elke at Apr 13, 2024, 09:39 AM

Limited Time Offer

25%

Off

Get Premium DAS-C01 Questions as Interactive Web-Based Practice Test or PDF

Comments

Submit Cancel

Junita

4 hours ago

Haha, I love how specific this question is! It's like someone at AWS is just trying to trip us up. 'HIVE METASTORE ERROR' – what is this, a crossword puzzle? Anyway, my money's on option A. Sticking the response in S3 and using a pre-signed URL seems like a nice, clean solution. Although, I do wonder if that would introduce any performance issues or other complications. Hmm, decisions, decisions...

upvoted 0 times

...

Doug

8 hours ago

Yeah, I agree. Payload size limits can be tricky, especially when dealing with large datasets. I wonder if we can optimize the query to return less data, or maybe partition the data in a different way.

upvoted 0 times

...

Dominga

1 days ago

Hmm, this is an interesting question. The error message suggests that the response payload size from the Athena query is exceeding the maximum allowed size. That could be a real problem, especially if this is a production workload.

upvoted 0 times

...

Latosha

1 days ago

You know, I was actually just reading about this kind of issue the other day. I think option D might be the way to go – checking for any unsupported characters in the schema and replacing them. Athena can be a bit picky about that stuff, and it could be the root cause of the problem. Although, I have to admit, I'm a little worried about the 'HIVE METASTORE ERROR' part. That's a new one for me.

upvoted 0 times

...

Luis

2 days ago

Okay, so we've got a few options here. Option B, running the MSCK REPAIR TABLE command, seems like it could be worth a shot. Maybe there's some issue with the partitions that's causing the problem. But I'm also intrigued by option C, creating a separate folder and using a Glue crawler. That could be a way to work around the payload size issue too.

upvoted 0 times

...

Cherri

4 days ago

Hmm, it sounds like the table is already partitioned, so that's good. But the payload size issue is a real head-scratcher. I'm leaning towards option A, since uploading the response to S3 and returning a pre-signed URL seems like a clever way to work around the payload size limit. But I'd love to hear what the others think.

upvoted 0 times

...

Brandon

6 days ago

Whoa, this question seems pretty tricky! A 'HIVE METASTORE ERROR' due to a response payload size exceeding the maximum allowed? That's a pretty specific issue. I'm not sure I'd know where to start, but I'm definitely curious to see what the other candidates think.

upvoted 0 times

...