Storage tiering and lifecycle
Design the storage-tiering and lifecycle system for a media archive holding 50PB of assets (raw camera footage, masters, derivatives) with wildly varying access patterns: some assets are hammered, most are touched once and then cold for years, and a few cold ones occasionally need to come back fast for a re-edit. Storage cost is the dominant concern, but a retrieval that takes hours when an editor needs it now is a product failure. Design the tiers, the placement/migration policy, and how you handle retrieval-latency expectations.
What a strong answer looks like
Clarify scale and constraints first. Propose a clean component breakdown, then go deep on the hard parts (data model, bottlenecks, consistency, failure modes) and name the trade-offs you are making.
Clarify4:30 left
Estimate4:30 planned
Design13:30 planned
Deep dive10:30 planned
Failure7:00 planned
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.