Cost-Effective Querying of Compressed Data for Audits
An insurance company stores transaction data that the company compressed with gzip. The company needs to query the transaction data for occasional audits. Which solution will meet this requirement in the MOST cost-effective way?
Community Votes
56% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The core concept tested is optimizing for 'occasional' access patterns by selecting a low-cost storage class (Glacier) that still supports direct querying capabilities, avoiding the higher per-query costs or egress fees associated with standard S3 services like Athena or S3 Select.
This question evaluates the most cost-effective solution for querying gzip-compressed transaction data stored in AWS, focusing on balancing storage costs with query performance and pricing. The correct approach leverages Amazon S3 Glacier Flexible Retrieval combined with Amazon S3 Glacier Select to minimize expenses for occasional audits.
Many learners choose Option B (S3 Standard with S3 Select) because they prioritize fast retrieval speeds over long-term storage costs, failing to recognize that 'occasional audits' justify the slower retrieval times of Glacier in exchange for significant savings.
Community Discussion (23 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option A is the correct answer because it addresses both the storage format (gzip) and the access pattern (occasional audits). Amazon S3 Glacier Flexible Retrieval provides the lowest storage cost among options that support querying. Amazon S3 Glacier Select allows you to filter data using SQL queries directly within the compressed files without retrieving the entire object first, which avoids high data retrieval and processing costs associated with services like Athena or full restores.Why the Other Options Are Wrong
Option B (S3 Standard) incurs significantly higher monthly storage costs compared to Glacier, making it less cost-effective for data that is rarely accessed. Option C (Athena on S3 Standard) adds query processing costs on top of standard storage fees, which is inefficient for occasional use cases. Option D is incorrect because Amazon Athena cannot natively query data stored in Glacier; it requires data to be in S3 Standard or compatible classes, and attempting to do so would incur massive retrieval fees or fail entirely.Community Comment Notes
Several community members, such as tgv and artworkad, correctly identified that Option A is more suitable than B or C due to cost constraints for infrequent access. User LR2023 highlighted that storing data in S3 Standard (Option B) is not cost-effective for this scenario, reinforcing the need for Glacier. While some users argued for speed (Option B), the question explicitly prioritizes 'MOST cost-effective', validating the choice of Glacier for archival-like audit data.Exam Strategy
When questions emphasize 'cost-effective' for data that is 'infrequently' or 'occasionally' accessed, always consider Amazon S3 Glacier Flexible Retrieval or Deep Archive. Ensure the service selected supports querying capabilities if the requirement involves analyzing the data without full restoration.
Frequently Asked Questions
Why is S3 Select not enough for cost-effectiveness?
S3 Select reduces data scanned during queries, but storing large volumes of historical audit data in S3 Standard incurs high monthly storage fees compared to Glacier.
Can Athena query gzip files in Glacier?
No, Athena operates on data in S3 Standard or similar tiers. It cannot directly query objects in Glacier without first restoring them, which defeats the purpose of cost optimization.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →