Cache stampede on viral content
A celebrity tweets a link to your article page at 20:30. Within seconds, origin DB CPU saturates, p99 on the article endpoint goes from 50ms to 9s, and your Redis dashboard shows hit-rate collapsing from 98% to 40% with a burst of identical key MISSes. The CDN dashboard shows a sudden flood of requests for the exact same URL. Nothing was deployed today. The cache TTL for article HTML is 60 seconds. How do you triage this and stop the origin from melting?
What a strong answer looks like
Stop the bleeding first (mitigate), then form hypotheses from real signals. Separate root cause from symptom, communicate status as you go, and close with what prevents a repeat.
0:00 of about 40 min
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.