Users on Switch1 assigned to a specific network segment are unable to communicate with users on Switch2 assigned to the same network segment. Both switches are connected via a properly configured trunk link. What is the most likely cause of this connectivity issue?
Spanning Tree Protocol is blocking the trunk port
The native VLAN on the trunk is misconfigured
The VLAN is not created on Switch2
The trunk link is configured to carry only the default VLAN
The most likely cause is that the Virtual Local Area Network (VLAN) has not been created on Switch2. VLANs are local to each switch, and simply assigning a port to a VLAN that doesn't exist in the switch's VLAN database won't suffice. Creating the VLAN on Switch2 ensures the switch can forward traffic for that VLAN. A misconfigured native VLAN might cause untagged traffic issues but wouldn't prevent communication on a specific VLAN. Spanning Tree Protocol blocking the trunk port would affect all traffic across the trunk, not just a single network segment. If the trunk link were configured to carry only the default VLAN, other VLANs would not be allowed across the trunk, but the question states the trunk is properly configured.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a VLAN and why is it important in networking?
Open an interactive chat with Bash
How do trunk links work in networking?
Open an interactive chat with Bash
What is the process to create a VLAN on a Cisco switch?
Open an interactive chat with Bash
Cisco CCNA 200-301
Network Access
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access