SAA-C03 Design Cost-Optimized Architectures Practice Question
A media processing workflow generates analytics files that are accessed unpredictably. Some files become hot again months later. The team wants automatic storage cost optimisation without retrieval delays. What should be used? The architecture review board prefers a managed AWS-native control.
⚠ Common exam trap
A common mix-up: candidates choose S3 Glacier Flexible Retrieval (Option C) thinking it is the cheapest for all files, but they overlook the retrieval delay requirement and the fact that files may become hot again, which Intelligent-Tiering handles seamlessly without any retrieval latency.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
S3 Intelligent-Tiering
S3 Intelligent-Tiering is the correct choice because it automatically moves objects between access tiers (frequent, infrequent, and archive instant retrieval) based on changing access patterns, without any retrieval delays for hot objects. This matches the unpredictable access pattern where files may become hot again months later, and it is a fully managed AWS-native solution that optimizes storage costs automatically.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
S3 Intelligent-Tiering
Why this is correct
S3 Intelligent-Tiering is the optimal choice because it automatically monitors access patterns per object and moves data to lower-cost tiers (Infrequent Access, Archive Instant Retrieval) while keeping retrieval latency in milliseconds. It charges a small monthly monitoring fee but avoids retrieval fees and does not require lifecycle rules or retrieval delays, making it ideal for analytics files that may be accessed hot, then cool, and occasionally need immediate access.
- ✗
Manual monthly review and object copying
Why it's wrong here
Manually reviewing objects monthly and copying them to a colder class cannot keep pace with variable or sporadic access patterns; analytics files may become hot again after a month, and the manual process leaves cost-saving opportunities on the table. It also introduces operational overhead, risks human error, and incurs extra PUT/COPY and GET costs with every manual move, all while lacking the continuous, automated monitoring that Intelligent-Tiering provides at a negligible cost.
- ✗
S3 Glacier Flexible Retrieval for all files
Why it's wrong here
S3 Glacier Flexible Retrieval has retrieval times measured in minutes to hours (Standard retrieval typically 3–5 hours), making it unsuitable for analytics files that may be needed immediately for ad-hoc queries or downstream processing. Additionally, applying Glacier to all files imposes a 90-day minimum storage duration; objects deleted or transitioned earlier incur a pro-rated early deletion charge, and the all-files approach is unnecessarily expensive for data with any hot access. Its retrieval complexity and latency make it wrong for this scenario.
- ✗
EFS One Zone for analytics files
Why it's wrong here
EFS One Zone is a POSIX file system, not an S3 storage class, and while it offers lifecycle management to an Infrequent Access tier, it is designed for file workloads with concurrent EC2 access, not for streaming or object-request analytics. Storing analytics files there would require a separate ingestion pipeline and incur single-AZ availability risk, plus EFS cost per GB is generally higher than S3 Intelligent-Tiering. Its lifecycle policies are file-age-based and cannot automatically optimize by access frequency the way S3 Intelligent-Tiering does.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
Courseiva writes every SAA-C03 question from scratch — 935 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAA-C03 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 SAA-C03 exam.