
Answer-first summary for fast verification
Answer: Create an S3 bucket lifecycle policy to move files from S3 Standard to S3 Standard-Infrequent Access (S3 Standard-IA) 30 days from object creation. Delete the files 4 years after object creation.
## Explanation **Correct Answer: C** **Key Requirements Analysis:** 1. **Immediate accessibility always required** - This eliminates S3 Glacier options (A and D) because Glacier has retrieval times ranging from minutes to hours, not immediate. 2. **Files frequently accessed in first 30 days, rarely accessed after** - This suggests infrequent access storage after 30 days. 3. **Files stored for 4 years before deletion** - Long-term storage requirement. 4. **Files are 5 MB each** - Small objects. 5. **Most cost-effective solution** - Need to balance cost with accessibility requirements. **Option Analysis:** **A (S3 Standard → S3 Glacier):** ❌ - Glacier doesn't provide immediate accessibility (retrieval times: Expedited = 1-5 minutes, Standard = 3-5 hours, Bulk = 5-12 hours) - Violates the "immediate accessibility is always required" requirement **B (S3 Standard → S3 One Zone-IA):** ❌ - S3 One Zone-IA stores data in only one Availability Zone - While cheaper than S3 Standard-IA, it has lower durability (99.999999999% vs 99.999999999% for Standard-IA) - For critical business data that's "not easy to reproduce," the single AZ storage poses higher risk - The cost savings may not justify the risk for critical data **C (S3 Standard → S3 Standard-IA):** ✅ - Provides immediate accessibility (same as S3 Standard) - Lower storage costs than S3 Standard after 30 days - Maintains high durability across multiple AZs - No retrieval fees (unlike Glacier) - Perfect for rarely accessed but immediately available data **D (S3 Standard → S3 Standard-IA → S3 Glacier):** ❌ - Moving to Glacier after 4 years doesn't make sense since files are deleted after 4 years - The question says "stored for 4 years before they can be deleted" - not stored longer - Adding Glacier transition adds unnecessary complexity with no benefit - Still violates immediate accessibility if moved to Glacier **Cost Considerations:** - S3 Standard-IA is designed for long-lived, infrequently accessed data that requires immediate availability - For 5 MB files, the minimum storage charge (128KB per object) applies, making Standard-IA more cost-effective than Standard for infrequently accessed objects - No retrieval fees unlike Glacier, which would be expensive if files are occasionally accessed **Best Practice:** For data that requires immediate accessibility but is infrequently accessed, S3 Standard-IA is the appropriate choice. The lifecycle policy automatically transitions objects after 30 days, optimizing costs while maintaining accessibility.
Ultimate access to all questions.
No comments yet.
Author: LeetQuiz Editorial Team
A company has an application that generates a large number of files, each approximately 5 MB in size. The files are stored in Amazon S3. Company policy requires the files to be stored for 4 years before they can be deleted. Immediate accessibility is always required as the files contain critical business data that is not easy to reproduce. The files are frequently accessed in the first 30 days of the object creation but are rarely accessed after the first 30 days.
Which storage solution is MOST cost-effective?
A
Create an S3 bucket lifecycle policy to move files from S3 Standard to S3 Glacier 30 days from object creation. Delete the files 4 years after object creation.
B
Create an S3 bucket lifecycle policy to move files from S3 Standard to S3 One Zone-Infrequent Access (S3 One Zone-IA) 30 days from object creation. Delete the files 4 years after object creation.
C
Create an S3 bucket lifecycle policy to move files from S3 Standard to S3 Standard-Infrequent Access (S3 Standard-IA) 30 days from object creation. Delete the files 4 years after object creation.
D
Create an S3 bucket lifecycle policy to move files from S3 Standard to S3 Standard-Infrequent Access (S3 Standard-IA) 30 days from object creation. Move the files to S3 Glacier 4 years after object creation.