High-cardinality metric overloads backend
Your metrics/monitoring backend is overloaded and slow, and you trace it to a recent change that added a high-cardinality label (like user id or request id) to a metric. How do you respond?
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 20 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.