2.0 Switching and Network Access
VLANs Practice Questions
VLAN creation, trunking, and access port assignment.
CCNA v2.0 objectives 2.1, 2.1.b · objective map
Author-reviewed by LabFabric · 6 September 2026 · Report a content issue
One solved question, so you can see how these are marked
Which command displays a condensed view of VLAN membership and their status on a Catalyst switch?
show vlan brief
show vlan brief lists each VLAN ID, name, status, and the access ports assigned to it in a compact table, unlike show vlan which prints far more detail per VLAN.
Every question in the set below is marked like this. The answers stay hidden until you pick one.
Find related practice in the CCNA pathAll 19 VLANs questions in this set
Answers and explanations appear when you work through the set above.
On a freshly reset Catalyst switch, which VLANs already exist in the VLAN database before any configuration is entered?
- Only VLAN 1
- VLAN 1 plus reserved legacy-media VLANs 1002 to 1005
- VLANs 1 through 10
- No VLANs exist until vlan database is initialized
Which two commands, entered in the correct order under interface configuration mode, place a switchport into VLAN 20 as an access port?
- switchport mode trunk, then switchport trunk allowed vlan 20
- switchport mode access, then switchport access vlan 20
- switchport access vlan 20, then no switchport trunk
- vlan 20, then switchport mode access
Both ends of a connected switch link are set to dynamic auto, with DTP enabled. Why does the link remain in access mode?
- The link is already trunking normally
- Neither dynamic-auto port initiates trunk negotiation
- The link has a VLAN mismatch that must be fixed with switchport trunk allowed vlan
- The port is administratively shut down
Which command explicitly forces a switch interface into trunking mode regardless of what the neighboring device negotiates?
- switchport mode dynamic desirable
- switchport nonegotiate
- switchport mode trunk
- switchport trunk encapsulation dot1q
On a switch that supports multiple trunk encapsulation types, which command must sometimes run before switchport mode trunk will succeed?
- switchport trunk native vlan 1 on the interface
- switchport trunk encapsulation dot1q
- switchport voice vlan
- spanning-tree portfast trunk
Why would an administrator change a trunk's native VLAN away from VLAN 1 to an unused VLAN such as 199?
- Increase available bandwidth by freeing the bandwidth reserved for VLAN 1 control traffic
- Reduce VLAN-hopping risk and separate untagged traffic from VLAN 1
- Because VLAN 1 cannot carry tagged frames
- To allow more than one native VLAN per trunk
With native-VLAN tagging disabled, what risk does a native-VLAN mismatch introduce on an 802.1Q trunk?
- Both ends negotiate a common native VLAN automatically
- The link refuses to come up at all
- Untagged frames can enter different VLANs at the two ends
- Only the lower numbered native VLAN is used by both sides
Which command restricts a trunk so that only VLANs 10, 20, and 199 are permitted to cross it?
- switchport trunk allowed vlan 10,20,199
- switchport access vlan 10,20,199
- vlan filter 10,20,199
- switchport trunk native vlan 10,20,199 on both ends
In the router-on-a-stick model, what must be configured on a router subinterface so it can process 802.1Q tagged frames for a specific VLAN?
- switchport trunk encapsulation dot1q
- encapsulation dot1q <vlan-id>
- ip address <vlan-id> secondary
- channel-group <vlan-id> mode active
A router-on-a-stick design uses one physical interface with two subinterfaces, f0/0.10 and f0/0.20. What must the connected switchport be configured as?
- An access port in VLAN 10
- An access port in VLAN 20
- A trunk allowing both VLANs 10 and 20
- An access EtherChannel using VLAN 10
Which inter-VLAN routing design avoids using any router hardware entirely, instead routing directly on the switch?
- Router-on-a-stick using per-VLAN subinterfaces
- Separate router interfaces for each VLAN
- A Layer 3 switch with ip routing and VLAN SVIs
- One access port shared by every VLAN
A multilayer switch has correctly addressed SVIs that are administratively shut down, and global IPv4 routing is disabled. Which commands address these two configuration faults?
- Global ip routing; no shutdown on each SVI
- switchport mode trunk on the SVIs
- vtp mode transparent, and ip default-gateway
- spanning-tree mode rapid-pvst and ip routing
Both PCs can reach their correctly configured SVI gateways, but not each other across VLANs. ACLs permit the traffic and the switch configuration shows no ip routing. Which change addresses the demonstrated forwarding fault?
- The VLANs need matching names
- Enable global IPv4 routing with ip routing
- The PCs need static ARP entries
- The switch needs a configured loopback interface
What does the command interface range fastethernet0/1 - 3 let an administrator do?
- Automatically bundle interfaces 1 through 3 as an EtherChannel
- Apply configuration to interfaces 1 through 3 simultaneously
- Create one VLAN spanning three separate switches
- Assign three different IP addresses to one interface
Which VLAN feature carries phone traffic on the same physical access port as data traffic, but keeps it in a separate VLAN from the PC?
- Private VLAN
- Voice VLAN
- Native VLAN
- Management VLAN
An engineer deletes VLAN 20 from a switch while several ports are still assigned to it in access mode. What happens to those ports?
- Move to VLAN 1 automatically and resume forwarding with the default access configuration
- Keep membership but stop forwarding until VLAN restoration or reassignment
- They are automatically shut down permanently
- They become trunk ports
What command shows the operational trunking encapsulation and administrative/operational mode for a single interface in detail?
- show interfaces trunk
- show interface <name> switchport
- show vlan id 1
- show spanning-tree interface <name> detail
Two switches are connected with a trunk, but show interfaces trunk on one of them lists no VLANs under 'Vlans allowed and active in management domain'. What is the most likely cause?
- The trunk is down at Layer 1
- No allowed VLAN is present and active in the local VLAN database
- A missing management IP address prevents the switch from activating any allowed trunk VLANs
- STP is blocking the trunk
Why might a network designer choose separate physical router interfaces per VLAN instead of router-on-a-stick, despite it using more hardware?
- Physical interfaces support more VLANs because subinterfaces are limited to two per router
- Avoid trunking and 802.1Q tagging for operational simplicity
- It is required whenever more than two VLANs exist
- Subinterfaces cannot carry an IP address