Edge cache tiering and purge
Design a content-delivery edge cache hierarchy for a global service serving static assets and large media: hundreds of edge POPs near users, a smaller tier of regional 'mid-tier' caches, and a small set of origins. Goal is a high offload ratio (most requests never reach origin), low latency, and the ability to purge content globally within seconds. How do you structure the cache tiers, route requests, and handle invalidation and origin protection?
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.
Clarify5:00 left
Estimate5:00 planned
Design15:00 planned
Deep dive12:00 planned
Failure8: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.