A data analyst runs a large number of data manipulation language (DML) queries by using Amazon Athena with the JDBC driver. Recently, a query failed after It ran for 30 minutes. The query returned…

Question

Options

• ASplit the query into smaller queries to search smaller subsets of data.
• BIn the settings for Athena, adjust the DML query timeout limit
• CIn the Service Quotas console, request an increase for the DML query timeout
• DSave the tables as compressed .csv files

• A
  4% (1)
• B
  4% (1)
• C
  77% (20)
• D
  15% (4)

Explanation

Amazon Athena has a default DML query timeout quota of 30 minutes. This is a service quota that can be increased through the AWS Service Quotas console by submitting a quota increase request. Since the data analyst does not need results immediately but needs a long-term solution for queries that run longer than 30 minutes, requesting a quota increase is the correct approach. Option A (splitting queries) is a workaround, not a long-term solution, and may not always be feasible. Option B is incorrect because there is no user-configurable DML timeout setting within the Athena console itself - this limit is a service quota, not a per-account setting. Option D (compressing CSV files) improves scan performance but does not address timeout limits.

No community discussion yet for this question.