The most cost-effective way to ensure Athena queries only scan necessary data is to partition the S3 bucket by account ID, region, and date, and then use those partitions in Athena. This works because Athena’s partition pruning automatically limits data scanning to only the relevant subdirectories when your query includes filters on those partition keys, directly reducing the amount of data read and thus the cost, since Athena charges per byte scanned. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your understanding of cost optimization through data organization rather than compression or file format changes—a common trap is to suggest converting to Parquet or using columnar storage, which helps but is secondary to partitioning for cost reduction. Remember the memory tip: “Partition first, format second” to prioritize pruning over compression when minimizing scan volume.
SAP-C02 Practice Question: Design Solutions for Organizational Complexity
This SAP-C02 practice question tests your understanding of design solutions for organizational complexity. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company has a central logging account that receives VPC Flow Logs, CloudTrail logs, and AWS Config logs from all accounts in the organization. The logs are stored in S3 buckets. The security team wants to analyze these logs using Amazon Athena. What is the MOST cost-effective way to ensure that the Athena queries only scan the necessary data?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Partition the data by account ID, region, and date in the S3 bucket, and use partitions in Athena.
Partitioning the S3 data by account ID, region, and date allows Athena to use partition pruning, which limits the amount of data scanned to only the relevant partitions based on query filters. This directly reduces query cost because Athena charges per amount of data scanned, and partitioning is the most effective way to minimize scanned data without additional compression or indexing overhead.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Partition the data by account ID, region, and date in the S3 bucket, and use partitions in Athena.
Why this is correct
Partition pruning ensures Athena scans only relevant partitions.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use S3 object-level compression (e.g., gzip) to reduce data volume.
Why it's wrong here
Compression reduces storage but does not reduce the amount of data scanned if partitions are not used.
✗
Create AWS Glue partition indexes on the table.
Why it's wrong here
Partition indexes are for faster partition retrieval, not for limiting scan size.
✗
Create separate Athena tables for each account and region.
Why it's wrong here
This increases maintenance and query complexity.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse performance optimization (e.g., compression, indexes) with cost optimization (reducing data scanned), and they may overlook that partition pruning is the primary mechanism to minimize Athena query costs, not just speed up queries.
Detailed technical explanation
How to think about this question
Athena uses Hive-style partitioning where S3 keys follow a pattern like `account=123/region=us-east-1/date=2025-01-01/`. When a query includes `WHERE account_id = '123' AND region = 'us-east-1'`, Athena reads only the objects under that prefix, leveraging the Presto/Hive partition pruning mechanism. This is far more cost-effective than compression alone because compression reduces bytes per object but not the number of objects scanned; partition pruning can eliminate entire directories of data.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Design Solutions for Organizational Complexity — This question tests Design Solutions for Organizational Complexity — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Partition the data by account ID, region, and date in the S3 bucket, and use partitions in Athena. — Partitioning the S3 data by account ID, region, and date allows Athena to use partition pruning, which limits the amount of data scanned to only the relevant partitions based on query filters. This directly reduces query cost because Athena charges per amount of data scanned, and partitioning is the most effective way to minimize scanned data without additional compression or indexing overhead.
What should I do if I get this SAP-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SAP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAP-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.