Database rejects connections after scaling
After scaling a service from 10 to 50 instances to handle growth, the database started rejecting connections ('too many connections') even though per-instance load went down. What happened?
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.