A hotel chain's internet link fills with volumetric noise, and loss hits every flow on that link. What does the pattern indicate?
Select an answer to reveal the explanation.
Short Explanation
When a flash flood fills every lane, repainting the lane arrows is not the story of the water. You read volumetric noise that fills the hotel link and drops every flow as a distributed denial-of-service flood. Ordinary growth that needs bandwidth, a marking error, or one guest laptop does not match indiscriminate loss from a flood of noise.
Full Explanation
Volumetric noise that fills the link, with loss on every flow, is a distributed denial-of-service flood occupying the hotel's internet capacity. The damage is indiscriminate because the link itself is full of attack traffic, not because one application or one guest misbehaved. Treating the full link as ordinary growth and jumping to a bigger circuit mistakes an attack for steady demand. Capacity might be discussed later as a mitigation, but the evidence to name first is the flood of noise. Treating the loss as a quality-of-service marking error assumes a policy is punishing every class the same way. A marking error does not generate volumetric noise that fills the link. Blaming one guest laptop cannot explain noise that fills the circuit and loss that hits every flow. One endpoint is not a volumetric source on that scale, and the pattern is not confined to that guest's session. Contain the flood and separate it from normal guest traffic before resizing the circuit or rewriting classes. Exam caveat: indiscriminate loss plus a link full of volumetric noise is a denial-of-service reading, not a routine bandwidth or marking ticket. Operational check: show the link filled by the noise and the loss spread across flows, then compare a quiet period on the same link.