Question 190
At a branch introducing an IP telephony access layer, a Junos specialist investigates this scenario: A technician plugs a phone into the wrong switch port and cannot identify its actual neighbor from cabling records. The solution should not give workstation traffic untrusted voice privileges. What risk must the implementation avoid?
Explanation
Correct Answer
For a branch introducing an IP telephony access layer, the relevant safeguard is: Do not expose sensitive topology details on untrusted external facing interfaces without policy. It matters while implementing: Enable supported LLDP on authorized interfaces and inspect neighbor information. The fault involves: Link Layer Discovery Protocol advertises local chassis and port information to directly attached compatible devices. The required acceptance result remains: show lldp neighbors identifies the intended adjacent device and receiving port.
Incorrect Answers
PoE availability depends on available switch power budget and each attached device's negotiated consumption. The appropriate correction for the reported case is: Do not expose sensitive topology details on untrusted external facing interfaces without policy.
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: Link Layer Discovery Protocol advertises local chassis and port information to directly attached compatible devices.
An Ethernet phone can bridge tagged voice traffic and untagged workstation traffic with appropriate VLAN behavior. Its verification is distinct from the reported condition: A technician plugs a phone into the wrong switch port and cannot identify its actual neighbor from cabling records. The solution should not give workstation traffic untrusted voice privileges.