The answer is to check for a trunk mismatch such as native VLAN inconsistency or other trunk-parameter problems. Even after confirming the allowed VLAN list is correct, a trunk can still fail if the native VLAN differs on each end, because control traffic like CDP and DTP, as well as untagged frames, rely on that common VLAN. On the CCNA 200-301 v2 exam, this tests your disciplined troubleshooting methodology: you must verify trunk health beyond just the allowed list, avoiding the trap of jumping to routing or STP issues prematurely. A common memory tip is "allowed list is not a health check"—the trunk encapsulation and native VLAN must match for the link to pass traffic reliably. Remember the mnemonic "NATIVE" for Native VLAN, Allowed list, Trunk mode, Interface status, VLAN existence, Encapsulation—check these in order when a trunk fails.
CCNA Switching and Network Access Practice Question
This 200-301 practice question tests your understanding of switching and network access. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. A key principle to apply: a trunk link carries traffic for multiple VLANs by tagging frames with VLAN identifiers to maintain VLAN separation across switches.. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Two switches are connected by a trunk. VLAN 50 exists on both switches, but traffic still fails across the link. The allowed VLAN list is correct. Which additional item should be checked next?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Check for a trunk mismatch such as native VLAN inconsistency or other trunk-parameter problems.
After confirming that the VLAN exists on both switches and is allowed on the trunk, another important item to verify is whether the trunk itself is actually operational with the expected encapsulation and whether there is a native VLAN or other trunk inconsistency. In plain language, just because the VLAN is listed does not guarantee the trunk is healthy in every relevant way. Trunking problems can still occur because of broader configuration mismatches.
This question is about disciplined troubleshooting. Once the obvious allowed-list issue is ruled out, the next step is to keep checking other trunk-related characteristics rather than jumping immediately to unrelated routing or service features. The correct answer is the one that stays grounded in trunk-specific verification.
Key principle: A trunk link carries traffic for multiple VLANs by tagging frames with VLAN identifiers to maintain VLAN separation across switches.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Check for a trunk mismatch such as native VLAN inconsistency or other trunk-parameter problems.
Why this is correct
This is correct because VLAN permission alone does not guarantee the trunk is healthy end to end.
Related concept
A trunk link carries traffic for multiple VLANs by tagging frames with VLAN identifiers to maintain VLAN separation across switches.
✗
Reset OSPF process IDs on both switches.
Why it's wrong here
This is wrong because OSPF process IDs are unrelated to a Layer 2 trunk issue.
When this WOULD be correct
In a question where OSPF routing issues are explicitly mentioned, such as 'OSPF routes are not being advertised between two switches,' resetting OSPF process IDs could be a valid troubleshooting step to refresh the routing tables and re-establish adjacency.
✗
Add ip helper-address under every access interface.
Why it's wrong here
This is wrong because DHCP relay does not solve a trunk transport problem.
When this WOULD be correct
In a question about configuring a router to support DHCP relay for multiple VLANs, where the scenario specifies that clients in different VLANs are unable to receive IP addresses, the option to add ip helper-address would be correct.
✗
Disable the MAC address table.
Why it's wrong here
This is wrong because MAC table operation is fundamental to switching and not the right next troubleshooting step.
When this WOULD be correct
In a question where the focus is on troubleshooting Layer 2 issues related to excessive MAC address table entries causing performance degradation, disabling the MAC address table temporarily could be a valid step to reset the switch's learning process and alleviate the issue.
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.
✓Check for a trunk mismatch such as native VLAN inconsistency or other trunk-parameter problems.Correct answer▾
Why this is correct
This is correct because VLAN permission alone does not guarantee the trunk is healthy end to end.
✗Reset OSPF process IDs on both switches.Wrong answer — click to see why▾
Why this is wrong here
Resetting OSPF process IDs does not address VLAN traffic issues over a trunk link, as OSPF is a routing protocol and unrelated to Layer 2 VLAN configurations.
★ When this WOULD be the correct answer
In a question where OSPF routing issues are explicitly mentioned, such as 'OSPF routes are not being advertised between two switches,' resetting OSPF process IDs could be a valid troubleshooting step to refresh the routing tables and re-establish adjacency.
Why candidates choose this
Candidates may confuse Layer 2 VLAN issues with Layer 3 routing problems, leading them to believe that OSPF configuration could impact VLAN traffic, especially if they have encountered similar scenarios in their studies.
✗Add ip helper-address under every access interface.Wrong answer — click to see why▾
Why this is wrong here
Adding an ip helper-address is irrelevant to VLAN traffic issues across a trunk link, as this command is used for forwarding DHCP requests, not for resolving VLAN connectivity problems.
★ When this WOULD be the correct answer
In a question about configuring a router to support DHCP relay for multiple VLANs, where the scenario specifies that clients in different VLANs are unable to receive IP addresses, the option to add ip helper-address would be correct.
Why candidates choose this
Candidates may choose this option due to a misunderstanding of how VLANs and DHCP interact, thinking that helper addresses could somehow assist with VLAN traffic issues.
✗Disable the MAC address table.Wrong answer — click to see why▾
Why this is wrong here
Disabling the MAC address table would not resolve VLAN traffic issues across a trunk link, as it pertains to Layer 2 forwarding and would disrupt normal switch operations, leading to further connectivity problems.
★ When this WOULD be the correct answer
In a question where the focus is on troubleshooting Layer 2 issues related to excessive MAC address table entries causing performance degradation, disabling the MAC address table temporarily could be a valid step to reset the switch's learning process and alleviate the issue.
Why candidates choose this
Candidates may choose this option due to a misunderstanding of how MAC address tables function, thinking that clearing the table might resolve connectivity issues without considering the specific VLAN configuration and trunking parameters.
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?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
Don't jump to unrelated issues like spanning tree or IP configuration when the problem is clearly trunk-related.
Detailed technical explanation
How to think about this question
A trunk link in Cisco networking is a Layer 2 connection between switches that carries traffic for multiple VLANs simultaneously. It uses tagging protocols like IEEE 802.1Q to insert VLAN identifiers into Ethernet frames, enabling switches to segregate and forward traffic correctly across VLAN boundaries. The native VLAN is a special VLAN whose frames are sent untagged on the trunk; both ends of the trunk must agree on the native VLAN to avoid misinterpretation of untagged frames.
When troubleshooting VLAN traffic failures on a trunk, verifying that the VLAN exists and is allowed is necessary but not sufficient. The trunk must be operational with matching encapsulation types (e.g., 802.1Q) and consistent native VLAN settings on both switches. A mismatch in native VLAN or trunk parameters can cause frames to be dropped or misrouted, even if the VLAN is permitted. This layered verification approach ensures the trunk is healthy end to end before considering unrelated issues.
A common exam trap is to jump to Layer 3 or service-related configurations such as OSPF process IDs or DHCP relay settings when VLAN traffic fails on a trunk. These do not affect Layer 2 trunk operation. Another mistake is disabling the MAC address table, which is fundamental to switching and would cause broader network disruption. The practical takeaway is to focus troubleshooting on trunk-specific parameters like native VLAN and encapsulation consistency before exploring other layers or features.
KKey Concepts to Remember
A trunk link carries traffic for multiple VLANs by tagging frames with VLAN identifiers to maintain VLAN separation across switches.
The native VLAN on a trunk must match on both ends to prevent untagged frames from being misclassified or dropped.
Trunk encapsulation types such as IEEE 802.1Q must be consistent on both switches to ensure proper VLAN tagging and frame forwarding.
Allowed VLAN lists on trunks control which VLANs can traverse the link but do not guarantee trunk operational status or consistency.
A trunk mismatch, including native VLAN inconsistency or encapsulation differences, can cause VLAN traffic to fail despite correct VLAN configuration.
Layer 2 protocols like VLAN tagging and trunk negotiation operate independently from Layer 3 routing protocols such as OSPF.
MAC address tables are essential for switching decisions but disabling them disrupts normal frame forwarding and is not a troubleshooting step for trunk issues.
DHCP relay configuration (ip helper-address) affects Layer 3 services and does not resolve Layer 2 trunk connectivity problems.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
A trunk link carries traffic for multiple VLANs by tagging frames with VLAN identifiers to maintain VLAN separation across switches.
Real-world example
How this comes up in practice
A network engineer at a university connects two campus buildings via a fibre link. Both routers run OSPF, but no adjacency forms — even though both routers can ping each other. The engineer finds one router is in area 0 and the other in area 1. OSPF adjacency requires matching area numbers, hello/dead timers, and network type. IP reachability alone is not enough.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this 200-301 question in full detail.
Review a trunk link carries traffic for multiple VLANs by tagging frames with VLAN identifiers to maintain VLAN separation across switches., then practise related 200-301 questions on the same topic to reinforce the concept.
Switching and Network Access — This question tests Switching and Network Access — A trunk link carries traffic for multiple VLANs by tagging frames with VLAN identifiers to maintain VLAN separation across switches..
What is the correct answer to this question?
The correct answer is: Check for a trunk mismatch such as native VLAN inconsistency or other trunk-parameter problems. — After confirming that the VLAN exists on both switches and is allowed on the trunk, another important item to verify is whether the trunk itself is actually operational with the expected encapsulation and whether there is a native VLAN or other trunk inconsistency. In plain language, just because the VLAN is listed does not guarantee the trunk is healthy in every relevant way. Trunking problems can still occur because of broader configuration mismatches.
This question is about disciplined troubleshooting. Once the obvious allowed-list issue is ruled out, the next step is to keep checking other trunk-related characteristics rather than jumping immediately to unrelated routing or service features. The correct answer is the one that stays grounded in trunk-specific verification.
What should I do if I get this 200-301 question wrong?
Review a trunk link carries traffic for multiple VLANs by tagging frames with VLAN identifiers to maintain VLAN separation across switches., then practise related 200-301 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
A trunk link carries traffic for multiple VLANs by tagging frames with VLAN identifiers to maintain VLAN separation across switches.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.