DNS TTL too long
During an incident you need to fail traffic over by changing DNS, but the records have a very long TTL, so clients keep hitting the broken endpoint for hours. How do you handle it now and in the future?
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.