nerdexam
Amazon

DEA-C01 · Question #199

A company has a data lake in Amazon S3. The company collects AWS CloudTrail logs for multiple applications. The company stores the logs in the data lake, catalogs the logs in AWS Glue, and…

The correct answer is A. Confirm that Athena is pointing to the correct Amazon S3 location. C. Use the MSCK REPAIR TABLE command. Option A (confirming the correct S3 location) is a fundamental first troubleshooting step - if Athena's table definition points to the wrong S3 prefix or bucket, no data will be returned. Option C (MSCK REPAIR TABLE) is critical because the logs are partitioned by year and…

Data Operations and Support

Question

A company has a data lake in Amazon S3. The company collects AWS CloudTrail logs for multiple applications. The company stores the logs in the data lake, catalogs the logs in AWS Glue, and partitions the logs based on the year. The company uses Amazon Athena to analyze the logs. Recently, customers reported that a query on one of the Athena tables did not return any data. A data engineer must resolve the issue. Which combination of troubleshooting steps should the data engineer take? (Choose two.)

Options

  • AConfirm that Athena is pointing to the correct Amazon S3 location.
  • BIncrease the query timeout duration.
  • CUse the MSCK REPAIR TABLE command.
  • DRestart Athena.
  • EDelete and recreate the problematic Athena table.

How the community answered

(43 responses)
  • A
    81% (35)
  • B
    2% (1)
  • D
    12% (5)
  • E
    5% (2)

Explanation

Option A (confirming the correct S3 location) is a fundamental first troubleshooting step - if Athena's table definition points to the wrong S3 prefix or bucket, no data will be returned. Option C (MSCK REPAIR TABLE) is critical because the logs are partitioned by year and stored in S3. When new partition directories are added to S3, the AWS Glue Data Catalog is not automatically updated. MSCK REPAIR TABLE scans the S3 path and registers any untracked partitions in the metastore, which is the most common cause of Athena tables returning no data for new data. Option B (increasing timeout) would not fix a 'no data returned' issue. Option D is invalid - Athena is a serverless service with no restart capability. Option E (deleting and recreating the table) is destructive and unnecessary.

Topics

#Amazon Athena#AWS Glue Data Catalog#Data Partitioning#Troubleshooting

Community Discussion

No community discussion yet for this question.

Full DEA-C01 Practice