Question 1
After a release, average API latency changes from 220 ms to 230 ms. The median changes from 120 ms to 125 ms, but checkout p95 latency changes from 400 ms to 2.8 seconds. Error rate is unchanged. What is the most defensible next action?
Treat the average as decisive and close the incident because overall latency barely changed.
Scale the database immediately because a tail-latency increase usually indicates database saturation under load.
Inspect slow checkout traces and correlated logs to identify where high- latency requests spend time.
Roll back every service immediately because an increase in p95 means the release slowed most requests.