Question 1mediummultiple choice
Full question →mediummultiple choiceObjective-mapped
Exhibit
Switch port requirement: - IP phone and PC share one physical access connection - Voice and data must remain logically separate
A switchport connected to an IP phone and a PC must carry user traffic and voice traffic separately. Which feature is designed for that purpose on a Cisco access port?
Answer choices
Why each option matters
Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.
A
Best answer
Voice VLAN
This is correct because a voice VLAN is designed to separate voice traffic from user data on the same access port.
B
Distractor review
EtherChannel
This is wrong because EtherChannel bundles multiple links and is unrelated to phone/data separation on one edge port.
C
Distractor review
SPAN
This is wrong because SPAN is used for traffic monitoring and mirroring, not normal voice/data VLAN separation.
D
Distractor review
Native VLAN
This is wrong because native VLANs are a trunking concept and do not describe the intended phone-plus-PC access-port design.
Common exam trap
Common exam trap: answer the scenario, not the keyword
A frequent exam trap is selecting EtherChannel, SPAN, or native VLAN instead of voice VLAN. EtherChannel bundles multiple physical links for increased bandwidth but does not separate voice and data traffic on a single port. SPAN is used for traffic monitoring and does not affect VLAN separation or QoS. Native VLAN applies to trunk ports and is unrelated to voice/data separation on access ports. Misunderstanding these concepts leads to incorrect answers because only voice VLAN specifically supports simultaneous voice and data traffic separation on one access port.
Technical deep dive
How to think about this question
A voice VLAN is a specialized VLAN configured on a Cisco switch port to separate voice traffic from regular data traffic when both an IP phone and a PC share the same physical access port. The IP phone tags its voice packets with the voice VLAN ID, allowing the switch to prioritize and handle voice traffic differently from the PC's untagged data traffic. This separation enables better Quality of Service (QoS) and security policies tailored specifically for voice communications, which are sensitive to latency and jitter. When configuring a switchport for an IP phone and PC, the port operates as an access port for the data VLAN and simultaneously supports a voice VLAN for the IP phone. The phone typically tags its voice traffic with the voice VLAN, while the PC traffic remains untagged and assigned to the default access VLAN. Cisco switches recognize the voice VLAN tag and apply appropriate QoS policies, ensuring voice traffic receives priority over data traffic. This design is essential for maintaining call quality and network performance in converged networks. A common exam trap is confusing the voice VLAN feature with other unrelated technologies like EtherChannel, SPAN, or native VLANs. EtherChannel aggregates multiple physical links, SPAN is for traffic monitoring, and native VLANs relate to trunk ports, not access ports with voice/data separation. Practically, voice VLANs allow a single physical port to logically separate traffic types, which is critical in environments where IP phones and PCs share a connection, ensuring voice traffic is prioritized and managed correctly.
KKey Concepts to Remember
- A voice VLAN allows a Cisco switchport to carry both voice and data traffic separately by tagging voice packets from IP phones.
- Cisco switches prioritize voice VLAN traffic to ensure Quality of Service for latency-sensitive voice communications.
- An access port configured with a voice VLAN treats untagged PC traffic as data VLAN and tagged phone traffic as voice VLAN.
- EtherChannel bundles multiple physical links for bandwidth aggregation and does not separate voice and data traffic on one port.
- SPAN is a monitoring feature that mirrors traffic for analysis and does not provide voice/data traffic separation.
- Native VLAN is a trunking concept that defines untagged traffic on trunk ports and is unrelated to voice VLAN on access ports.
- Voice VLAN configuration enables logical separation of traffic types on a single physical port, improving network management and security.
- Proper voice VLAN setup is essential in converged networks to maintain call quality and avoid voice traffic degradation.
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.
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.
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.
CCNA DHCP practice questions
Practise DHCP scopes, relay, leases and troubleshooting.
CCNA show ip route practice questions
Practise routing-table output, longest-prefix match, AD and route selection.
CCNA show interfaces trunk practice questions
Practise trunk verification and VLAN forwarding across switches.
CCNA wireless security practice questions
Practise WLAN security, authentication and wireless architecture concepts.
CCNA IPv6 practice questions
Practise IPv6 addressing, routes, neighbour discovery and common IPv6 exam traps.
More questions from this exam
Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.
Question 1
A router learns the same prefix from both OSPF and EIGRP. Which route is installed by default?
Question 2
A router shows this output: R1#show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 10.1.1.2 1 FULL/DR 00:00:34 192.168.12.2 GigabitEthernet0/0 10.1.1.3 1 2WAY/DROTHER 00:00:39 192.168.12.3 GigabitEthernet0/0 Which statement is correct?
Question 3
What is the OSPF metric called?
Question 4
A non-root switch has two uplinks toward the root bridge. One path has a lower total STP cost than the other. What role will the lower-cost uplink have?
Question 5
A router interface applies this ACL inbound: 10 deny tcp any any eq 80 20 permit ip any any A user reports that web browsing to a server by IP address fails, but ping works. Which statement best explains the behavior?
Question 6
A router learns route 198.51.100.0/24 from OSPF with AD 110 and also has a static route to the same prefix configured with AD 150. Which route is installed?
FAQ
Questions learners often ask
What does this 200-301 question test?
A voice VLAN allows a Cisco switchport to carry both voice and data traffic separately by tagging voice packets from IP phones.
What is the correct answer to this question?
The correct answer is: Voice VLAN — The correct feature is a voice VLAN. In plain language, a voice VLAN lets the switch treat the IP phone’s traffic differently from the user PC’s traffic even though both devices may be connected through the same physical access port. The phone can tag voice traffic for the voice VLAN while the PC remains in the normal data access VLAN. This is a practical design because it keeps voice traffic logically separate, which helps with policy, QoS, and management. This is a classic CCNA switching concept because it shows that one physical edge port can still support more than one logical traffic type in a controlled way. A standard access VLAN by itself would not provide the same voice/data separation. EtherChannel, SPAN, and native VLAN concepts solve different problems. The best answer is the feature specifically built to support phones and workstations together on one access connection while keeping their traffic logically distinct.
What should I do if I get this 200-301 question wrong?
Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.
Discussion
Loading comments…
Sign in to join the discussion.