Object storage tiers and lifecycle automation
storage cost optimization.
tiers trade storage price for retrieval cost and latency; automate with lifecycle rules or intelligent tiering.
What's really being asked
The interviewer wants to see that you optimize storage cost against access patterns rather than dumping everything in one tier.
The full answer
Explain the fundamental trade-off: cheaper tiers cost less per gigabyte stored but more per gigabyte retrieved, and may add latency or minimum storage durations. Standard suits hot, frequently accessed data. Infrequent Access lowers storage cost for data read occasionally but charges more per retrieval. Archive tiers like Glacier are cheapest to store but can take minutes to hours to restore and carry retrieval fees and minimum retention periods. To automate, attach lifecycle rules that transition objects by age, for example move to Infrequent Access after thirty days and to Archive after ninety, and expire them later. When access is unpredictable, use an intelligent-tiering class that monitors each object and moves it automatically, so you avoid retrieval surprises. Always factor per-object transition costs and minimum-duration charges so tiering down does not cost more than it saves on small or short-lived objects.
The mistakes people make
Archiving data that is still read often, then paying steep retrieval fees and waiting on restores. Forgetting minimum-duration charges, where moving tiny objects to a colder tier costs more than it saves. Ignoring archive restore latency in a workflow that needs immediate access. Hand-moving objects instead of using lifecycle automation.
What usually comes next
When is intelligent tiering better than fixed lifecycle rules. What are the retrieval-time options for archive tiers. How do minimum-duration charges affect small objects. How do you measure access patterns to choose thresholds.
A concrete example
A logging platform keeps logs in Standard for thirty days for active debugging, transitions them to Infrequent Access for ninety days where audits occasionally read them, then moves them to an archive tier for seven-year compliance retention, and finally expires them. Lifecycle rules do this automatically, and because the team confirmed logs are rarely read after thirty days, the colder tiers cut storage cost sharply without painful retrieval surprises.
Interview question
What is the core trade-off when moving objects to a colder storage tier like Archive?
- a.Unlimited retrievals at no additional charge
- b.Lower storage cost but higher retrieval cost and slower accessCorrect
- c.Higher storage cost but instant retrieval from anywhere
- d.Lower durability in exchange for faster writes
Why? this is the answer
Colder tiers reduce per-gigabyte storage cost but charge more to retrieve and add latency or minimum durations. Durability is not reduced, and retrievals are never free in archive tiers.
Just read this? Test yourself on what you have been reading.
Read the original → docs.aws.amazon.com
- #object-storage
- #storage-tiers
- #lifecycle-policies
- #cost-optimization
- #intelligent-tiering
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles