A sharp rise in a service's request volume is observed while latency and errors stay flat. What does this indicate?
Select an answer to reveal the explanation.
Short Explanation
You see traffic up and the service coping—for now. Watch saturation next, because it tells you whether the headroom lasts.
Full Explanation
The correct answer is the demand-increase-and-watch-saturation answer. Traffic measures demand rather than health directly. Rising demand with stable latency and errors means the service is keeping up, and saturation is the signal that reveals how much headroom remains before it stops doing so.
The failure-since-traffic-spike-is-error answer is incorrect because increased demand is not a failure; it becomes one only when the service cannot serve it.
The nothing-actionable-because-only-latency-and-errors-describe-health answer is incorrect because traffic is one of the four signals and provides essential context - the same latency reading means something different under double the load.
The dashboards-need-to-be-rebuilt answer is incorrect because axis scaling is a presentation matter, not a finding.
For the exam, read traffic as demand and interpret the other signals in light of it.