CPU pinned after deploy
One service is pinning CPU at 100% on every instance, and it started right after a deploy. You suspect a hot loop or pathological code path. 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.