Rollback blocked by migration
An incident calls for rolling back a bad deploy, but the rollback is slow or impossible — a database migration already ran, or the old version is incompatible with the new data. How do you handle it?
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.