Users of a newly deployed VoIP solution report multiple instances of dropped or garbled calls. Thirty users connect to the primary site via a site-to-site VPN, and the primary site supplies a dial…

Question

Options

• ADisable Layer 2 encryption on the site-to-site VPNs throughout the company
• BProvision new firewalls at all sites to enable QoS management of VoIP traffic
• CEnable point-to-point tunneling for all VoIP traffic at the new site
• DConfigure QoS settings to support the larger bandwidth available
• EPrioritize ICMP and TCP traffic over UDP traffic using QoS

• A
  8% (5)
• B
  2% (1)
• C
  2% (1)
• D
  83% (49)
• E
  5% (3)

Explanation

The core problem is a configuration mismatch: the network engineer copied settings from a 2-user, low-bandwidth DSL site and applied them to a 30-user site with significantly more bandwidth. The QoS (Quality of Service) settings from the small site are not tuned for the larger site's traffic volume, causing VoIP packets to be dropped or delayed. Option D - configuring QoS settings to support the larger bandwidth - directly addresses this root cause by properly prioritizing VoIP (UDP) traffic at appropriate thresholds for the actual bandwidth. Option A (disabling L2 encryption) introduces a security risk and does not address QoS. Option B (new firewalls) is expensive and unnecessary since the existing equipment can handle QoS. Option C (point-to-point tunneling) adds overhead and does not fix prioritization. Option E is backwards - VoIP uses UDP and should be prioritized over TCP/ICMP, not the other way around.

No community discussion yet for this question.