Jeff’s Note #
Unlike generic exam dumps, ADH analyzes this scenario through the lens of a Real-World Lead Developer.
For DVA-C02 candidates, the confusion often lies in quick retrieval vs. archival cost optimization for object storage. In production, this is about knowing exactly which S3 storage class supports millisecond retrievals while minimizing costs over long retention periods. Let’s drill down.
The Certification Drill (Simulated Question) #
Scenario #
A dynamic media startup named PixelStream is deploying a video processing application on Amazon EC2 instances. The application generates large video clip files (several GBs daily). These files are infrequently accessed but must be available to users within minutes whenever requested during the first 12 months of storage. PixelStream is required to retain these files for 7 years due to compliance reasons.
The Requirement: #
Determine the most cost-effective, operationally simple solution to store these generated files so that initial 12-month retrievals are near-instantaneous, while ensuring long-term archival for 7 years.
The Options #
- A) Store files in an Amazon S3 bucket using the S3 Glacier Instant Retrieval storage class. Use an S3 Lifecycle policy to transition the files to S3 Glacier Deep Archive after 1 year.
- B) Store files in an Amazon S3 bucket using the S3 Standard storage class. Use an S3 Lifecycle policy to transition the files to S3 Glacier Flexible Retrieval after 1 year.
- C) Store the files on an Amazon Elastic Block Store (EBS) volume. Use Amazon Data Lifecycle Manager (DLM) to create snapshots and store them in S3.
- D) Store the files on an Amazon Elastic File System (EFS) mount. Enable EFS lifecycle management to transition files to EFS Standard-Infrequent Access (Standard-IA) after 1 year.
Google adsense #
leave a comment:
Correct Answer #
A
Quick Insight: The Developer Imperative #
The fastest retrieval within minutes after upload combined with very low access frequency fits the S3 Glacier Instant Retrieval tier perfectly for year 1. Transitioning to Glacier Deep Archive after that minimizes cost over the remaining 6 years. Other options either have slower retrievals, higher costs, or are operationally complex.
Content Locked: The Expert Analysis #
You’ve identified the answer. But do you know the implementation details that separate a Junior from a Senior?
The Expert’s Analysis #
Correct Answer #
Option A
The Winning Logic #
Storing files initially in S3 Glacier Instant Retrieval meets the critical requirement of near-immediate file availability (milliseconds retrievals) during the first year, despite infrequent access. After 1 year, lifecycle transitioning to S3 Glacier Deep Archive ensures minimal long-term storage costs for the remaining 6 years, balancing compliance and cost-effectiveness.
- S3 Glacier Instant Retrieval is designed for rarely accessed data that still requires immediate retrieval. Its retrieval times are typically milliseconds, which fits the “available within minutes” constraint without incurring the longer multi-hour delays of Glacier Flexible Retrieval or Deep Archive.
- The lifecycle policy automates transitioning data to cheaper but slower storage after 1 year, meeting retention and cost goals.
- EBS volumes (Option C) and EFS (Option D) are generally far more expensive at scale for long-term archival and do not offer integrated lifecycle policies to Glacier tiers.
- S3 Standard (Option B) keeps data readily available but at significantly higher cost during year 1, and Glacier Flexible Retrieval does not provide instant or millisecond retrieval, instead offering minutes to hours, risking user experience degradation.
The Technical Blueprint #
# Example lifecycle policy JSON to transition objects after 1 year
aws s3api put-bucket-lifecycle-configuration --bucket pixelstream-videos \
--lifecycle-configuration '{
"Rules": [
{
"ID": "GlacierInstantThenDeepArchive",
"Filter": {},
"Status": "Enabled",
"Transitions": [
{
"Days": 0,
"StorageClass": "GLACIER_INSTANT_RETRIEVAL"
},
{
"Days": 365,
"StorageClass": "DEEP_ARCHIVE"
}
],
"NoncurrentVersionTransitions": [],
"AbortIncompleteMultipartUpload": {
"DaysAfterInitiation": 7
}
}
]
}'
The Comparative Analysis #
| Option | API Complexity | Performance | Use Case |
|---|---|---|---|
| A | Medium (Lifecycle policies + Glacier Instant Retrieval API) | Millisecond retrievals in year 1 + minimal cost year 2-7 | Ideal for archival with occasional fast access early on |
| B | Low (Standard + Lifecycle) | Millisecond retrieval year 1, minutes-hours retrieval year 2-7 | Higher cost, slower retrieval after transition |
| C | High (EBS + DLM snapshots) | Instant access, high cost and complexity | Unsuitable for long-term archival at scale |
| D | Medium (EFS + lifecycle) | Instant access year 1, infrequent access tier reduces cost moderately | Expensive, not optimized for archival of large infrequently accessed data |
Real-World Application (Practitioner Insight) #
Exam Rule #
“For the exam, always pick S3 Glacier Instant Retrieval when you see a requirement for rarely accessed data needing immediate availability.”
Real World #
“In real production environments, we might add caching layers or indexing services on top if user requests demand complex search or partial retrievals—but for pure file storage with access time constraints, the above remains optimal.”
(CTA) Stop Guessing, Start Mastering #
Disclaimer
This is a study note based on simulated scenarios for the DVA-C02 exam.