You manage a large S3 bucket with mixed access patterns. You want to optimize costs by automatically moving files to cheaper storage classes but keep frequently accessed files in STANDARD. Which lifecycle rule setup best achieves this?
ATransition objects to STANDARD_IA after 30 days and to GLACIER after 90 days, with a filter excluding files accessed in last 30 days.
BTransition all objects to GLACIER immediately after upload to save costs.
CDelete objects after 30 days to save storage costs.
DKeep all objects in STANDARD storage class to ensure fastest access.
Step-by-Step Solution
Solution:
Step 1: Understand access patterns and cost goals
Frequently accessed files should stay in STANDARD. Less accessed files should move to cheaper classes like STANDARD_IA and GLACIER.
Step 2: Evaluate lifecycle rule options
Transition objects to STANDARD_IA after 30 days and to GLACIER after 90 days, with a filter excluding files accessed in last 30 days. uses transitions with a filter to exclude recently accessed files, optimizing costs while keeping frequent files fast. Transition all objects to GLACIER immediately after upload to save costs. moves all files immediately to GLACIER, causing slow access. Delete objects after 30 days to save storage costs. deletes files, which may lose data. Keep all objects in STANDARD storage class to ensure fastest access. keeps all files in STANDARD, not optimizing costs.
Final Answer:
Transition objects to STANDARD_IA after 30 days and to GLACIER after 90 days, with a filter excluding files accessed in last 30 days. -> Option A
Quick Check:
Use transitions with filters to balance cost and access = C [OK]
Quick Trick:Use filters to exclude recent files from transitions [OK]
Common Mistakes:
Moving all files to GLACIER immediately
Deleting files instead of transitioning
Keeping all files in expensive STANDARD class
Master "Cost Optimization" in AWS
9 interactive learning modes - each teaches the same concept differently
