Cache invalidation via CDC
Design a cache-invalidation system driven by change-data-capture for a read-heavy product catalog: a multi-region edge cache serves ~2M reads/sec, the source of truth is a primary database, and a price or availability change must invalidate/refresh the relevant cached entries everywhere within a couple seconds. Requirements: no entry stays stale indefinitely, an invalidation storm (bulk price update on 1M SKUs) must not stampede the database, and regions must converge. Walk through capture, propagation, and the failure modes.
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.