SOA-C02 Cost and Performance Optimization Practice Question
A SysOps administrator notices that the monthly bill for Amazon S3 has increased significantly. The company uses S3 for storing application logs and user uploads. The logs are accessed rarely but must be retained for 3 years. User uploads are accessed frequently for the first 30 days, then rarely after. Which S3 lifecycle policy will optimize storage costs?
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
✓
Transition logs to S3 Glacier Deep Archive after 30 days, and transition user uploads to S3 Standard-IA after 30 days, then to Glacier Deep Archive after 90 days.
This lifecycle policy optimizes costs by transitioning logs (rarely accessed but need retention) directly to S3 Glacier Deep Archive after 30 days, and for user uploads (frequently accessed for the first 30 days, then rarely), transition to S3 Standard-IA after 30 days, then to Glacier Deep Archive after 90 days. Option B is wrong because it transitions user uploads (initially frequent access) to Glacier Deep Archive too early, causing retrieval costs. Option C is wrong because logs should be archived, but deleting user uploads after 1 year may be premature. Option D is wrong because it transitions logs to Standard-IA, which is not cost-effective for long-term retention, and user uploads to One Zone-IA, which lacks durability.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Transition logs to S3 Glacier Deep Archive after 30 days, and transition user uploads to S3 Standard-IA after 30 days, then to Glacier Deep Archive after 90 days.
Why this is correct
This is correct because logs are typically append-only and rarely accessed after the first 30 days, making S3 Glacier Deep Archive the lowest-cost storage class while satisfying the 3-year retention requirement. User uploads, however, are frequently accessed in the month after upload, so S3 Standard-IA after 30 days reduces cost without sacrificing retrieval performance; then transitioning to Glacier Deep Archive after 90 days aligns with the access drop-off and keeps lifecycle costs minimal.
- ✗
Transition user uploads to S3 Glacier Deep Archive after 30 days, and transition logs to S3 Glacier after 90 days.
Why it's wrong here
This is wrong because transitioning user uploads to S3 Glacier Deep Archive after only 30 days ignores that users may still need frequent access after the first month—Deep Archive retrieval can take up to 12 hours, so it is not suitable for data that might be accessed on demand. Additionally, placing logs into S3 Glacier after 90 days is suboptimal because Glacier is more expensive than Glacier Deep Archive and logs should be archived to the cheapest tier earlier, not delayed to 90 days, to maximize cost savings while still meeting retention.
- ✗
Move logs to S3 Glacier Deep Archive after 30 days, and delete user uploads after 1 year.
Why it's wrong here
This is wrong because deleting user uploads after 1 year would destroy data that has no stated expiration or retention limit—there is no justification for permanent deletion, and doing so could violate compliance or customer-expectation requirements. While transitioning logs to S3 Glacier Deep Archive after 30 days is a sound cost-saving action, the lifecycle policy is invalid as a whole because the user uploads part deletes data prematurely instead of moving it to cheaper storage tiers.
- ✗
Transition logs to S3 Standard-IA after 30 days, and transition user uploads to S3 One Zone-IA after 30 days.
Why it's wrong here
This is wrong because moving logs to S3 Standard-IA after 30 days does not achieve the maximum cost reduction—logs are rarely read after being written, so sending them directly to Glacier Deep Archive after 30 days would cut storage costs far more than Standard-IA, which is meant for infrequent but immediate access. S3 One Zone-IA is also inappropriate for user uploads because it stores data in a single Availability Zone, offering only 99.5% durability versus the 99.999999999% of standard classes; if that AZ fails, the user uploads are permanently lost, which is not acceptable for customer data.
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 SOA-C02 question from scratch — 247 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 SOA-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 SOA-C02 exam.