Question 880
At North Library, an IDF trunk carries voice VLAN 310 but its upstream interface mistakenly permits only data VLAN 110. Which observation most directly isolates the likely cause before any change?
Explanation
Correct Answer
For North Library, the decisive mechanism is 802.1Q VLAN tagging. 802.1Q tagging preserves logical broadcast-domain identity over shared Ethernet links. Inspect per-port tag membership and tagged packet captures at the failing VLAN boundary is the most direct way to isolate this particular failure before making a change.
Incorrect Answers
This is relevant to Ethernet negotiation and duplex, where 802.3 physical link negotiation precedes Layer 2 and Layer 3 service validation In the North Library case, Those observations could be normal while the stated fault persists. The specific mechanism is 802.1Q tagging preserves logical broadcast-domain identity over shared Ethernet links
This is relevant to LLDP topology and discovery, where lLDP supplies adjacent-device identity without proving end-to-end routing or authentication In the North Library case, Those observations could be normal while the stated fault persists. The specific mechanism is 802.1Q tagging preserves logical broadcast-domain identity over shared Ethernet links
This is relevant to PoE power negotiation, where 802.3af at and bt power classes and the switch budget constrain device operation In the North Library case, Those observations could be normal while the stated fault persists. The specific mechanism is 802.1Q tagging preserves logical broadcast-domain identity over shared Ethernet links