Question 650
At a branch introducing an IP telephony access layer, a Junos specialist investigates this scenario: An IP phone and a computer share an access port but both are placed in the same data segment against policy. The solution should not give workstation traffic untrusted voice privileges. What requirement most specifically calls for this approach?
Explanation
Correct Answer
For a branch introducing an IP telephony access layer, this mechanism fits the requirement: Use dedicated voice VLANs to separate phone and workstation traffic on a shared port. The design is appropriate because: A voice VLAN permits supported tagged phone traffic to use a separate VLAN from ordinary untagged data traffic. In this scenario, the observed issue is: An IP phone and a computer share an access port but both are placed in the same data segment against policy. The corresponding implementation is: Configure the intended voice VLAN and data VLAN relationship on the shared access connection.
Incorrect Answers
Voice VLAN tagging and QoS classification must be mapped to the correct switch forwarding treatment. The appropriate correction for the reported case is: Configure the intended voice VLAN and data VLAN relationship on the shared access connection.
LLDP-MED network policy information can advertise voice VLAN and QoS settings to compatible phones. Fixing that different mechanism would not address the current root cause: a voice VLAN permits supported tagged phone traffic to use a separate VLAN from ordinary untagged data traffic.
Link Layer Discovery Protocol advertises local chassis and port information to directly attached compatible devices. Its verification is distinct from the reported condition: An IP phone and a computer share an access port but both are placed in the same data segment against policy. The solution should not give workstation traffic untrusted voice privileges.