A company's data analyst needs to ensure that queries executed in Amazon Athena cannot scan more than a prescribed amount of data for cost control purposes. Queries that exceed the prescribed…

Question

Options

• AConfigure Athena to invoke an AWS Lambda function that terminates queries when the
• BFor each workgroup, set the control limit for each query to the prescribed threshold.
• CEnforce the prescribed threshold on all Amazon S3 bucket policies
• DFor each workgroup, set the workgroup-wide data usage control limit to the prescribed threshold.

• A
  11% (4)
• B
  81% (30)
• C
  3% (1)
• D
  5% (2)

Explanation

Amazon Athena workgroups provide a built-in per-query data usage control that automatically cancels any query that would scan more data than the configured threshold. Setting this limit per workgroup is the native, zero-code solution-no Lambda functions, no S3 bucket policies, and no external monitoring required. When a query exceeds the per-query limit, Athena cancels it immediately and returns an error to the user. Choice A (Lambda to terminate queries) would work but requires custom code to monitor query state and invoke the StopQueryExecution API, adding unnecessary complexity. Choice D describes a workgroup-wide aggregate limit (total bytes scanned across all queries in a period), which is not the same as a per-query cancellation threshold. Choice C (S3 bucket policies) controls access, not query data volume.

No community discussion yet for this question.