CCNA Switching and Network Access Practice Question
A switchport on one side of a link is configured as a trunk, but the peer side is configured as an access port. The physical link is up, but VLAN traffic behaves unexpectedly. What is the most likely cause?
⚠ Common exam trap
Be cautious of assuming all VLAN issues are due to allowed lists or STP. Consider mode mismatches when the link is physically up but traffic is disrupted.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The two ends disagree on whether the link is a trunk or an access port.
The most likely cause is a switchport mode mismatch. In practical terms, one side expects the link to carry multiple VLANs with tagging behavior, while the other side treats it as a normal one-VLAN endpoint-style access connection. The physical interface can still come up, but the two ends do not agree on how the traffic should be handled. This is a classic Layer 2 troubleshooting pattern. The link may not be fully down, but the configuration disagreement causes logical forwarding problems.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The two ends disagree on whether the link is a trunk or an access port.
Why this is correct
A switchport in trunk mode encapsulates frames with 802.1Q tags and expects to receive tagged frames, while an access port transmits and receives only untagged frames in a single VLAN. When one end is a trunk and the other is an access port, the access port will drop tagged frames or treat them as invalid, and the trunk port may not accept the untagged frames sent by the access side. This role mismatch prevents proper VLAN segmentation and causes the link to fail at Layer 2.
- ✗
The switches must both use the same hostname.
Why it's wrong here
Hostnames are purely cosmetic identifiers used for device management and CLI prompts; they have no influence on the Data Link layer behavior of a switchport. The operational mode (access or trunk) is determined by the switchport mode configuration and DTP negotiation, not by the name assigned to the switch. Therefore, requiring identical hostnames would neither cause nor fix an inconsistency between the two ends of the link.
When this WOULD be correct
In a different scenario where a question asks about the importance of hostname consistency for management or monitoring purposes in a network, option B could be correct. For example, if the exam question focused on network management tools that rely on hostname resolution, having the same hostname could be crucial.
- ✗
The native VLAN must be set to 1 on both sides first.
Why it's wrong here
Setting the native VLAN to 1 on both sides would only ensure that untagged frames on a trunk are placed in the same VLAN, but it does not address the fact that one side expects 802.1Q-tagged frames while the other expects untagged frames. The native VLAN mismatch is a possible secondary fault, but the primary issue here is the trunk/access role disagreement. Unless both interfaces are configured as trunk, the native VLAN setting alone cannot make the link function correctly.
When this WOULD be correct
In a different question, if the scenario involved two switches configured as trunks but with different native VLANs, then specifying that the native VLAN must be set to 1 on both sides could be correct. This would be relevant if the question focused on ensuring consistent native VLAN settings for proper communication.
- ✗
The ports need OSPF enabled.
Why it's wrong here
OSPF is a Link State routing protocol that operates at Layer 3 and requires IP addresses and routing tables to exchange routes; it has absolutely no role in determining whether a switchport is an access or trunk port. Even if OSPF were enabled on both switches, it would not alter the switchport mode or the encapsulation of Ethernet frames on the link. The problem is strictly a Layer 2 configuration mismatch and can only be resolved by aligning the switchport modes.
When this WOULD be correct
In a different scenario where the question asks about routing protocols and their necessity for inter-VLAN communication, option D could be correct if the exam context involves enabling OSPF on interfaces to facilitate routing between VLANs across different switches.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.
✓The two ends disagree on whether the link is a trunk or an access port.Correct answer▾
Why this is correct
A switchport in trunk mode encapsulates frames with 802.1Q tags and expects to receive tagged frames, while an access port transmits and receives only untagged frames in a single VLAN. When one end is a trunk and the other is an access port, the access port will drop tagged frames or treat them as invalid, and the trunk port may not accept the untagged frames sent by the access side. This role mismatch prevents proper VLAN segmentation and causes the link to fail at Layer 2.
✗The switches must both use the same hostname.Wrong answer — click to see why▾
Why this is wrong here
OSPF is a Layer 3 routing protocol used for exchanging routes between routers, not for resolving Layer 2 switchport mismatches. This issue is purely about trunk/access configuration, which is unrelated to OSPF.
★ When this WOULD be the correct answer
In a different scenario where a question asks about the importance of hostname consistency for management or monitoring purposes in a network, option B could be correct. For example, if the exam question focused on network management tools that rely on hostname resolution, having the same hostname could be crucial.
Why candidates choose this
Students may confuse Layer 2 and Layer 3 concepts, thinking that enabling a routing protocol could fix connectivity issues. However, OSPF has no effect on VLAN tagging or trunk negotiation.
✗The native VLAN must be set to 1 on both sides first.Wrong answer — click to see why▾
Why this is wrong here
While native VLAN mismatch can cause issues on a trunk link, the primary problem here is that one side is configured as access, not trunk. Even if native VLAN is set to 1 on both sides, the access port will still not process tagged frames correctly.
★ When this WOULD be the correct answer
In a different question, if the scenario involved two switches configured as trunks but with different native VLANs, then specifying that the native VLAN must be set to 1 on both sides could be correct. This would be relevant if the question focused on ensuring consistent native VLAN settings for proper communication.
Why candidates choose this
Native VLAN is a common source of trunk problems, so test-takers may focus on that detail. However, the root cause is the trunk/access role mismatch, not the native VLAN value.
✗The ports need OSPF enabled.Wrong answer — click to see why▾
Why this is wrong here
Hostnames are purely for identification and have no impact on switchport operation or VLAN tagging. The trunk/access mismatch is a Layer 2 configuration issue independent of hostnames.
★ When this WOULD be the correct answer
In a different scenario where the question asks about routing protocols and their necessity for inter-VLAN communication, option D could be correct if the exam context involves enabling OSPF on interfaces to facilitate routing between VLANs across different switches.
Why candidates choose this
Some students might think that matching hostnames is required for switch interoperability, but this is incorrect. Hostnames are only used for CLI identification and logging.
Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Visual reference
Go deeper
Related to this question
Learn chapter
Interpreting Packet Capture Output for Layer 2/3 Troubleshooting
Key term
VLAN
A VLAN (Virtual Local Area Network) is a logical grouping of network devices that behave as if they are on the same physical network segment, regardless of their actual physical location.
Key term
VLAN
A VLAN logically segments a physical network into isolated broadcast domains without requiring separate physical switches.
About these practice questions
One of 1,389 original 200-301 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.