A bank's path tests are dropped in one QoS queue while traffic in the other classes on the same circuit still passes. What should the analyst call the fault?
Select an answer to reveal the explanation.
Short Explanation
One clogged toll lane is not a reason to blame the teller window. You call the fault the QoS class that is dropping the test traffic, because other classes on the circuit still pass. The teller browser, DNS alone, or the branch wireless network would blame a layer the queue data does not show.
Full Explanation
Path tests are dropped in one QoS queue while traffic in the other classes on the same circuit still passes, so the fault is the QoS class that is dropping the test traffic. Those other classes still passing is what localizes the drops to that class. The browser on the teller workstation can make a banking page feel slow, but a browser does not drop one class inside a QoS queue while other classes pass, and the measurement is on the path test rather than on page rendering. DNS only does not fit a class-specific drop: the tests are already in a queue and being discarded there, which is past name lookup, and a name fault would not spare every other class on the circuit. The branch wireless network is an easy ticket in a branch, yet the drops follow one traffic class on the circuit, so a wireless ticket ignores the queue evidence and sends the work to the wrong place. On the exam, the drops belong to the QoS class that is discarding the test traffic, because the other classes on the circuit still pass. In production, compare drop counters or path results for the affected class with a class that still passes on the same circuit, and work the queue that is discarding the test traffic.