An ecommerce company ingests a large set of clickstream data in JSON format and stores the data in Amazon S3. Business analysts from multiple product divisions need to use Amazon Athena to analyze…

Question

Options

• AUse a CREATE TABLE AS SELECT (CTAS) statement to create separate tables for each product
• BCreate an AWS account for each division Provide cross-account access to an AWS Glue Data
• CCreate an Athena workgroup for each division
• DCreate an AWS account for each division

• A
  10% (2)
• B
  10% (2)
• C
  75% (15)
• D
  5% (1)

Explanation

Amazon Athena workgroups are purpose-built for isolating and governing query usage by team, department, or application. Each workgroup can have its own data usage controls (e.g., per-query and per-workgroup data scanned limits), and Amazon CloudWatch metrics are automatically published per workgroup, allowing you to set CloudWatch Alarms that trigger when a division's scanned data exceeds its quota. This requires no custom infrastructure and has the least operational overhead. Option A (CTAS to create separate tables) doesn't provide usage monitoring or quota enforcement. Options B and D (separate AWS accounts per division) provide isolation but introduce significant operational overhead for account management and cross-account access setup, far exceeding what workgroups require.

No community discussion yet for this question.