How to Store Each Team's Athena Results in Separate S3 Buckets?
A company is using Amazon S3 buckets to store datasets. The company has several teams that use Amazon Athena to run one-time queries against the datasets. A CloudOps engineer must implement a solution that stores each team's Athena query results in that team's individual S3 bucket. Which solution will meet this requirement?
Community Insight
The exam tests centralized enforcement of Athena query result locations; the trap is assuming each user can simply set an S3 result path while sharing the primary workgroup.
Amazon Athena workgroups define a per-workgroup query result location, so creating one workgroup per team routes each team's output to its own S3 bucket. The page confirms option A and explains why client-side result settings and Glue databases do not enforce that isolation.
Many candidates pick C, believing teams can set individual S3 result locations inside the primary workgroup, but that relies on client-side settings and does not guarantee per-team separation.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Athena workgroups are the native mechanism for separating query execution settings, including the query result output location. A workgroup can enforce its result location so every query run in it writes to the team's designated S3 bucket. This gives centralized control and avoids depending on users to configure their clients correctly. Because the requirement is to store each team's results in that team's individual bucket, one workgroup per team with its own result location meets it directly.Why the Other Options Are Wrong
Option B is wrong because AWS Glue Data Catalog databases organize tables and metadata; they do not control where Athena writes query results. Option C is wrong because sharing the primary workgroup and asking users to set result locations is client-side configuration that workgroup enforcement can override and that does not guarantee isolation. Option D is wrong because Glue security configurations control encryption and access for ETL jobs, not Athena query output paths.Community Comment Notes
Bad_Mat states that the answer is A and describes "individual Athena workgroups that have separate S3 query result locations", which aligns with the AWS workgroup design. The comment is concise but points to the correct centralized control rather than per-query client settings. No commenter argued for the Glue database or security-configuration options.Official Reference
Exam Strategy
When an Athena question asks for team-specific result storage, look for workgroups with distinct result locations because workgroup settings are enforced server-side. Eliminate options that rely on users changing client-side settings or on Glue metadata objects, which do not govern query output.
Frequently Asked Questions
Why is sharing the primary Athena workgroup with per-query result locations wrong?
The primary workgroup is shared, and a user-set result location is a client-side setting that workgroup enforcement can override, so per-team isolation is not guaranteed.
Do AWS Glue Data Catalog databases control Athena query result storage?
No. Glue databases organize table metadata for Athena; the query result S3 path is configured on the Athena workgroup, not on the Glue database.
Related Analysis
Practice All SOA-C03 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SOA-C03 Practice Test →