S3 Intelligent-Tiering Default vs Deep Archive for Millisecond Retrieval
A company stores petabytes of data in thousands of Amazon S3 buckets in the S3 Standard storage class. The data supports analytics workloads that have unpredictable and variable data access patterns. The company does not access some data for months. However, the company must be able to retrieve all data within milliseconds. The company needs to optimize S3 storage costs. Which solution will meet these requirements with the LEAST operational overhead?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests the specific retrieval latency guarantees of S3 Intelligent-Tiering tiers; the common trap is selecting Deep Archive for lower cost without realizing it violates the millisecond retrieval requirement.
This page analyzes how to optimize S3 storage costs while maintaining millisecond retrieval times, establishing that the default access tier of S3 Intelligent-Tiering is the correct solution compared to Deep Archive.
Many learners select Option C (Deep Archive) because it offers the lowest storage cost, failing to recognize that Deep Archive retrieval takes hours and does not meet the 'milliseconds' constraint.
Community Discussion (12 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option D is the correct answer because S3 Intelligent-Tiering with the default access tier automatically moves data to an "Archive Instant Access" tier after 90 days of no access. This tier provides millisecond retrieval times at a significantly lower cost than S3 Standard, satisfying both the cost optimization and performance requirements with zero operational overhead.Why the Other Options Are Wrong
Option C activates the Deep Archive Access tier, which is designed for long-term archival where retrieval can take 12 hours or more, directly violating the millisecond retrieval requirement. Options A and B involve manual lifecycle policies or standard-IA/Glacier configurations, which introduce operational overhead and may not guarantee the same level of automation or performance consistency as Intelligent-Tiering's default behavior.Community Comment Notes
Community consensus heavily favored Option D, with many users noting that while Deep Archive is cheaper, it fails the latency test. As user GiorgioGss noted, "Although C is more cost-effective... must be able to retrieve all data within milliseconds will go with D." Another user, rpwags, emphasized that "Glacier Deep Archive... typically takes 12 hours or more," confirming why C is incorrect despite its popularity among those prioritizing cost over speed.Official Reference
Exam Strategy
Always prioritize the explicit performance constraints (like 'milliseconds') over pure cost savings when choosing between storage classes. If a question demands instant access, eliminate any Glacier or Deep Archive options immediately, even if they seem more cost-effective.
Frequently Asked Questions
Why is S3 Intelligent-Tiering Deep Archive wrong for this question?
Deep Archive requires 12+ hours for retrieval, violating the millisecond requirement. Only the default tier's Archive Instant Access tier supports instant retrieval.
Does S3 Intelligent-Tiering have operational overhead?
No, it is fully automated. It monitors access patterns and moves objects between tiers without any manual intervention or lifecycle policy management.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →