A bank's voice tests show high jitter while packet loss on the same path stays near zero, and the calls are breaking. What is the path problem?
Select an answer to reveal the explanation.
Short Explanation
A phone call falls apart when the gaps between words keep changing, even if no words are dropped. You are looking at jitter on the voice path, because loss on that path is near zero and the calls still break. A browser fault, a DNS-only problem, or a wireless ticket does not match that evidence.
Full Explanation
Voice quality collapses when the spacing between packets keeps changing, even when almost none of those packets are lost. The bank's tests show high jitter with loss near zero on the same path, and the calls break in that window, so the damaged metric is jitter. Jitter on the voice path, while loss on that same path stays near zero, is the finding the tests support. A browser rendering fault inside the trading application would affect how a page draws. It does not explain voice tests whose loss is already near zero and whose jitter is high. A DNS-only fault that never touches the voice path itself would fail name lookup and would not be the metric moving on a path the voice test is already using. A wireless problem on the branch office access points would be a local radio issue. The evidence given is jitter on the voice path, which is a path-quality finding rather than a wireless ticket by itself. Exam caveat: high jitter with loss near zero is a path finding, and it is not a browser rendering fault, a DNS-only fault, or a wireless ticket. Operational check: compare jitter and loss on the same voice test over several intervals and confirm jitter tracks the broken calls while loss stays near zero.