- A
They allow multiple VLANs to share one physical inter-switch link while preserving VLAN identity
This is correct because trunking allows multiple VLANs to traverse a single physical link with tagging.
- B
They force every host port to become a routed port
Why wrong: This is wrong because trunks are about carrying multiple VLANs, not converting all host ports into routed interfaces.
- C
They eliminate the need for VLAN tagging
Why wrong: This is wrong because trunking commonly depends on tagging precisely so multiple VLANs can be distinguished.
- D
They replace the need for IP addressing on switches
Why wrong: This is wrong because trunks are a Layer 2 transport concept and do not remove the need for IP addressing where required.
CCNA Switching and Network Access Practice Question
This 200-301 practice question tests your understanding of switching and network access. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: a trunk link allows multiple VLANs to share a single physical inter-switch connection by tagging frames with VLAN identifiers.. 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.
Which statement best explains why trunks are needed between switches in a multi-VLAN environment?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"best"Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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
They allow multiple VLANs to share one physical inter-switch link while preserving VLAN identity
Trunks are needed because they allow traffic from multiple VLANs to cross a single physical link between switches. In plain language, instead of using one cable per VLAN between switches, a trunk can carry many VLANs at once while preserving their identity through tagging. That makes the design much more scalable and practical in real networks. Without trunking, only one VLAN’s traffic could normally use a simple access link at a time. In larger environments, that would quickly become messy and wasteful. CCNA questions often focus on this basic reason for trunks: efficient transport of multiple logically separate VLANs over one physical inter-switch connection.
Key principle: A trunk link allows multiple VLANs to share a single physical inter-switch connection by tagging frames with VLAN identifiers.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
They allow multiple VLANs to share one physical inter-switch link while preserving VLAN identity
Why this is correct
This is correct because trunking allows multiple VLANs to traverse a single physical link with tagging.
Clue confirmation
The clue word "best" in the question point toward this answer.
- ✗
They force every host port to become a routed port
Why it's wrong here
This is wrong because trunks are about carrying multiple VLANs, not converting all host ports into routed interfaces.
When this WOULD be correct
In a scenario where the question asks about the configuration of a network where all ports must operate in routed mode for inter-VLAN routing, option B could be correct. For example, if the question specifies a network design requiring all ports to be routed for specific routing protocols, this option would apply.
- ✗
They eliminate the need for VLAN tagging
Why it's wrong here
This is wrong because trunking commonly depends on tagging precisely so multiple VLANs can be distinguished.
When this WOULD be correct
In a question focused on a simplified network setup where VLANs are not implemented or where all devices are on the same broadcast domain, a statement about eliminating VLAN tagging could be correct, as there would be no need for tagging in such a scenario.
- ✗
They replace the need for IP addressing on switches
Why it's wrong here
This is wrong because trunks are a Layer 2 transport concept and do not remove the need for IP addressing where required.
When this WOULD be correct
In a question specifically about Layer 2 switches in a network that does not require routing, one might ask if trunks can replace the need for IP addressing in a purely Layer 2 environment. In this context, if the question implies that the switches are only used for VLAN segregation without any Layer 3 functions, this option could be considered correct.
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.
✓They allow multiple VLANs to share one physical inter-switch link while preserving VLAN identityCorrect answer▾
Why this is correct
This is correct because trunking allows multiple VLANs to traverse a single physical link with tagging.
✗They force every host port to become a routed portWrong answer — click to see why▾
Why this is wrong here
Option B is incorrect because trunks do not force every host port to become a routed port; instead, they allow multiple VLANs to traverse a single link while keeping VLANs separate. Host ports can still remain in access mode without being routed ports.
★ When this WOULD be the correct answer
In a scenario where the question asks about the configuration of a network where all ports must operate in routed mode for inter-VLAN routing, option B could be correct. For example, if the question specifies a network design requiring all ports to be routed for specific routing protocols, this option would apply.
Why candidates choose this
Candidates may find this option tempting because they might confuse the concept of VLANs with routing, thinking that all ports must be routed to facilitate VLAN communication, leading to a misunderstanding of trunking versus access ports.
✗They eliminate the need for VLAN taggingWrong answer — click to see why▾
Why this is wrong here
This option is wrong because VLAN tagging is essential for distinguishing traffic from different VLANs on the same trunk link, and trunks do not eliminate the need for tagging; they actually rely on it to function correctly.
★ When this WOULD be the correct answer
In a question focused on a simplified network setup where VLANs are not implemented or where all devices are on the same broadcast domain, a statement about eliminating VLAN tagging could be correct, as there would be no need for tagging in such a scenario.
Why candidates choose this
Candidates may be tempted by this option due to a misunderstanding of VLAN functionality, thinking that trunks simplify the network by removing complexity, rather than recognizing that they actually introduce the necessity for tagging to manage multiple VLANs.
✗They replace the need for IP addressing on switchesWrong answer — click to see why▾
Why this is wrong here
This option is incorrect because trunks do not eliminate the need for IP addressing on switches; switches still require IP addresses for management and routing purposes, regardless of trunking.
★ When this WOULD be the correct answer
In a question specifically about Layer 2 switches in a network that does not require routing, one might ask if trunks can replace the need for IP addressing in a purely Layer 2 environment. In this context, if the question implies that the switches are only used for VLAN segregation without any Layer 3 functions, this option could be considered correct.
Why candidates choose this
Candidates may find this option tempting because they might confuse the role of trunks with the overall management of switches, mistakenly believing that VLANs can operate without any IP configuration.
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
A common exam trap is selecting answers that confuse trunk ports with routed ports or suggest trunks eliminate VLAN tagging. Some candidates mistakenly believe trunks convert all host ports into routed interfaces or that VLAN tagging is unnecessary on trunks. In reality, trunk ports remain Layer 2 interfaces and rely on VLAN tagging (802.1Q) to distinguish traffic from different VLANs. Misreading this can cause candidates to pick incorrect options that mention routed ports or claim trunks remove the need for tagging, which contradicts fundamental VLAN trunking principles.
Detailed technical explanation
How to think about this question
In a multi-VLAN environment, switches segment network traffic into separate broadcast domains called VLANs to improve security and reduce congestion. Each VLAN acts like a distinct logical network, isolating traffic from other VLANs. However, when multiple switches are involved, VLAN traffic must traverse links between switches while maintaining VLAN separation. This is where trunk links come into play, allowing multiple VLANs to share a single physical connection by tagging frames with VLAN identifiers using protocols like IEEE 802.1Q. The decision to use trunks stems from the need to efficiently carry traffic from multiple VLANs over one inter-switch link without losing VLAN identity. Trunking tags each frame with a VLAN ID, enabling the receiving switch to correctly forward the frame to the appropriate VLAN. Without trunks, each VLAN would require a dedicated physical link between switches, which is impractical and wasteful in larger networks. Cisco switches use 802.1Q as the standard trunking protocol, and understanding this is critical for CCNA candidates. A common exam trap is confusing trunk links with routed ports or thinking trunks eliminate VLAN tagging. Trunks do not convert switch ports into Layer 3 routed interfaces; they operate at Layer 2 and rely on tagging to distinguish VLAN traffic. Misunderstanding this can lead to selecting incorrect answers that mention routed ports or no tagging. Practically, trunks enable scalable VLAN deployment across multiple switches, preserving VLAN separation while minimizing cabling complexity.
KKey Concepts to Remember
- A trunk link allows multiple VLANs to share a single physical inter-switch connection by tagging frames with VLAN identifiers.
- Cisco switches use IEEE 802.1Q as the standard protocol to tag VLAN traffic on trunk links.
- Without trunking, each VLAN would require a separate physical link between switches, which is inefficient and impractical.
- Trunk ports operate at Layer 2 and do not convert switch ports into routed (Layer 3) interfaces.
- VLAN tagging on trunks preserves VLAN identity, enabling switches to forward frames to the correct VLAN across shared links.
- Trunking improves network scalability by reducing the number of physical cables needed to support multiple VLANs between switches.
- Misunderstanding trunking can lead to confusing it with routed ports or assuming VLAN tagging is unnecessary on trunks.
- In Cisco networks, trunk ports are configured explicitly to carry multiple VLANs, unlike access ports which carry only one VLAN.
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 allows multiple VLANs to share a single physical inter-switch connection by tagging frames with VLAN identifiers.
Real-world example
How this comes up in practice
A help-desk technician troubleshoots why a newly connected PC cannot reach shared printers on the same floor. The cable is good, the switch port is active, but the PC is in VLAN 20 and the printers are in VLAN 10. The uplink trunk only allows VLAN 10. A trunk being up does not mean every VLAN crosses it.
What to study next
Got this wrong? Here's your next step.
Review a trunk link allows multiple VLANs to share a single physical inter-switch connection by tagging frames with VLAN identifiers., then practise related 200-301 questions on the same topic to reinforce the concept.
- →
Switching and Network Access — study guide chapter
Learn the concepts, then practise the questions
- →
Switching and Network Access practice questions
Targeted practice on this topic area only
- →
All 200-301 questions
1,819 questions across all exam domains
- →
CCNA 200-301 v2 study guide
Full concept coverage aligned to exam objectives
- →
200-301 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related 200-301 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Network Infrastructure and Connectivity practice questions
Practise 200-301 questions linked to Network Infrastructure and Connectivity.
Switching and Network Access practice questions
Practise 200-301 questions linked to Switching and Network Access.
IP Routing practice questions
Practise 200-301 questions linked to IP Routing.
Network Services and Security practice questions
Practise 200-301 questions linked to Network Services and Security.
AI and Network Operations practice questions
Practise 200-301 questions linked to AI and Network Operations.
CCNA subnetting practice questions
Practise IPv4 subnetting, CIDR, masks, host ranges and subnet selection.
CCNA OSPF practice questions
Practise OSPF neighbours, router IDs, metrics, areas and routing-table interpretation.
CCNA VLAN practice questions
Practise VLANs, access ports, trunks, allowed VLANs and switching scenarios.
CCNA STP practice questions
Practise spanning tree, root bridge election, port roles and STP troubleshooting.
CCNA EtherChannel practice questions
Practise LACP, PAgP, port-channel behaviour and bundle requirements.
CCNA ACL practice questions
Practise standard and extended ACLs, permit/deny logic and traffic filtering.
CCNA NAT practice questions
Practise static NAT, dynamic NAT, PAT and inside/outside address translation.
Practice this exam
Start a free 200-301 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this 200-301 question test?
Switching and Network Access — This question tests Switching and Network Access — A trunk link allows multiple VLANs to share a single physical inter-switch connection by tagging frames with VLAN identifiers..
What is the correct answer to this question?
The correct answer is: They allow multiple VLANs to share one physical inter-switch link while preserving VLAN identity — Trunks are needed because they allow traffic from multiple VLANs to cross a single physical link between switches. In plain language, instead of using one cable per VLAN between switches, a trunk can carry many VLANs at once while preserving their identity through tagging. That makes the design much more scalable and practical in real networks. Without trunking, only one VLAN’s traffic could normally use a simple access link at a time. In larger environments, that would quickly become messy and wasteful. CCNA questions often focus on this basic reason for trunks: efficient transport of multiple logically separate VLANs over one physical inter-switch connection.
What should I do if I get this 200-301 question wrong?
Review a trunk link allows multiple VLANs to share a single physical inter-switch connection by tagging frames with VLAN identifiers., then practise related 200-301 questions on the same topic to reinforce the concept.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
A trunk link allows multiple VLANs to share a single physical inter-switch connection by tagging frames with VLAN identifiers.
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 →
Keep practising
More 200-301 practice questions
- A switchport connected to another switch should carry multiple VLANs, but it was manually configured as an access port.…
- What problem is HSRP designed to solve?
- Which TWO statements correctly describe the causes or implications of CRC errors, runts, giants, or output errors as see…
- You are connected to R1. Configure IPv4 and IPv6 addressing on R1's interfaces and verify reachability to R2. The curren…
- Which TWO statements accurately describe how AI/ML concepts are applied to network operations in modern enterprise netwo…
- Which TWO switch port configurations are required when connecting a Cisco IP phone and a desktop PC to a single access p…
Last reviewed: May 17, 2026
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.