200 status with error body
Your error-rate dashboards are green, but a feature is clearly broken for users. You discover a downstream service returns HTTP 200 with an error payload in the body instead of an error status. 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.