Courseiva

CCNA VLAN Questions

75 of 221 questions · Page 1/3 · VLAN topic · Answers revealed

1
Multi-Selectmedium

A router is configured as a DHCP server for VLAN 20. Clients on the VLAN can reach the default gateway, but they do not receive leases. Which two configuration issues on the router would directly prevent successful address assignment?

Select 2 answers
A.The excluded-address range removes the entire usable subnet
B.The DHCP pool is missing a dns-server statement
C.The subinterface lacks an ip helper-address
D.There are no available addresses left in the defined pool
AnswersA, D

The network for VLAN 20 is 10.20.20.0/24, which has a usable host range of 10.20.20.1 through 10.20.20.254. An excluded-address command that covers this entire range removes all assignable addresses, leaving the DHCP pool scope effectively empty. This is why no clients can receive an IP address from the server.

Why this answer

The router can serve DHCP locally without an ip helper-address. The real problem is that the excluded-address range consumes every usable host address, leaving the pool with no assignable leases.

Exam trap

A common exam trap is to incorrectly assume that missing optional DHCP parameters, such as the dns-server statement, or the absence of an ip helper-address on the subinterface, will prevent clients from receiving leases. Candidates may also overlook the impact of the excluded-address command consuming the entire subnet range, mistakenly thinking the router’s DHCP service is functioning correctly because clients can ping the gateway. The real issue is that no IP addresses remain available to assign, which is a subtle but critical configuration error that directly causes DHCP lease failures.

Why the other options are wrong

B

Incorrect because the dns-server statement is optional; its absence does not prevent the DHCP server from assigning IP addresses to clients.

C

Incorrect because the ip helper-address command is only necessary when forwarding DHCP requests across subnets, not when the router itself is the DHCP server on the VLAN.

2
MCQhard

Refer to the exhibit. A trunk between SW1 and SW2 is configured on both ends, the link is up, but hosts in every VLAN on SW1 cannot reach their counterparts on SW2. The administrator runs 'show interfaces GigabitEthernet0/1 trunk' on both switches. What is the most likely cause?

A.The native VLAN is mismatched between SW1 and SW2.
B.One of the interfaces is configured as an access port instead of a trunk.
C.One of the interfaces is administratively shut down.
D.SW1 uses ISL encapsulation while SW2 uses 802.1Q, so the trunk encapsulations do not match.
AnswerD

The Encapsulation column shows isl on SW1 and 802.1q on SW2. ISL and 802.1Q frames are incompatible, so although both ports report trunking, no VLAN traffic is passed. Configure both ends with the same encapsulation.

Why this answer

The two ends use different trunk encapsulations: SW1 is configured for ISL (Encapsulation isl) and SW2 for IEEE 802.1Q (Encapsulation 802.1q). Both ports report 'trunking' because with mode on each side simply stops negotiating and sends frames in its own format, but ISL-encapsulated frames are not understood by a 802.1Q port and vice versa, so no VLAN traffic crosses the link. The fix is to configure the same encapsulation on both ends (for example 'switchport trunk encapsulation dot1q' on SW1).

Exam trap

A trunk that shows 'trunking' on both ends is not necessarily working. Always compare the Encapsulation column on both switches, not just the Status column.

Why the other options are wrong

A

Both switches list native VLAN 1. A native VLAN mismatch causes CDP/STP warnings and untagged-traffic leakage, not complete isolation of every VLAN.

B

The exhibit shows both ports in trunk mode 'on' and in the trunk table, so neither is an access port.

C

Both ports appear in the trunk table with Status trunking, so neither is shut down.

3
MCQmedium

A network administrator is configuring a new Cisco Catalyst switch and needs to ensure that the native VLAN for 802.1Q trunk port GigabitEthernet1/0/1 is VLAN 99, which is not the default. The administrator enters the command 'switchport trunk native vlan 99' on the interface. However, after applying the configuration, the administrator notices that untagged traffic from the native VLAN is not being forwarded correctly. What is the most likely cause of this issue?

A.VLAN 99 must be created in the VLAN database before it can be used as the native VLAN.
B.The native VLAN configuration requires the 'switchport mode trunk' command to be applied first.
C.The native VLAN must be configured on both ends of the trunk link, and the other end is still using the default native VLAN.
D.The command 'switchport trunk native vlan 99' is only valid on access ports, not on trunk ports.
AnswerC

For 802.1Q trunks, the native VLAN must match on both ends; otherwise, untagged traffic is interpreted differently, causing forwarding failures or VLAN mismatches. The other end likely still uses VLAN 1, so untagged frames are placed into VLAN 1 instead of VLAN 99, breaking connectivity for that VLAN.

Why this answer

The native VLAN on an 802.1Q trunk must be consistent on both ends. If one side uses VLAN 99 and the other uses VLAN 1, untagged frames are classified differently, leading to connectivity problems for devices in the native VLAN. Ensuring both switches use the same native VLAN resolves the issue.

Exam trap

The trap here is assuming that configuring the native VLAN on one side is sufficient, overlooking the requirement for matching native VLANs on both ends of a trunk.

4
MCQmedium

Two switches are connected by an 802.1Q trunk. CDP reports a native VLAN mismatch. Which issue is most likely to appear because of this?

A.Untagged traffic may be placed into different VLANs on each switch.
B.All tagged traffic on the trunk is dropped immediately.
C.STP is disabled on the trunk link.
D.The trunk automatically converts to an access port.
AnswerA

When two switches have different native VLANs configured on the same 802.1Q trunk, each switch treats untagged frames as belonging to its own locally configured native VLAN. The sending switch places untagged frames into its native VLAN, while the receiving switch places them into its own native VLAN, which may be a different VLAN number. This mismatch causes untagged broadcast, multicast, and unknown unicast traffic to be placed into different VLAN domains on each switch, creating a classic native VLAN mismatch symptom.

Why this answer

A native VLAN mismatch can cause untagged traffic sent on one side to be placed into a different VLAN on the other side. That leads to confusing connectivity issues and can also create security concerns. It does not automatically disable the trunk.

Exam trap

A common exam trap is to believe that a native VLAN mismatch causes the trunk link to shut down or block all traffic. In reality, only untagged traffic is affected, and tagged VLAN traffic continues to pass normally if allowed VLANs match. Another mistake is thinking the trunk automatically converts to an access port, which Cisco switches do not do.

Candidates may also overlook that STP remains enabled and functional despite the mismatch. Focusing only on trunk status without considering untagged traffic behavior leads to incorrect answers.

Why the other options are wrong

B

This is incorrect because tagged traffic on the trunk is not dropped due to a native VLAN mismatch; tagged frames continue to be forwarded normally if VLANs are allowed on both sides.

C

This option is wrong since a native VLAN mismatch does not disable Spanning Tree Protocol; STP continues to operate normally on the trunk link.

D

This is incorrect because Cisco switches do not automatically convert a trunk port to an access port due to a native VLAN mismatch; the trunk remains active.

5
PBQhard

You are connected to the console of a Catalyst 2960+ switch named SW2. Fa0/5 connects to an IP phone with a PC behind it, and Fa0/10 connects to an access point. Both ports are access ports (VLAN 50 on Fa0/5 for the PC, VLAN 100 on Fa0/10) but PoE has been disabled on them, so neither device powers up. Configure the switch so that the phone is powered and sends voice traffic in VLAN 150 (the PC stays in VLAN 50), and the access point is powered and stays in VLAN 100. Select the correct configuration and verification.

Network Topology
Fa0/5Fa0/10SW2IP PhoneAccess Point

Hints

  • •Use 'switchport voice vlan' to define the voice VLAN on an access port.
  • •Enable PoE on a port with 'power inline auto'.
  • •Verify voice VLAN with 'show interfaces switchport' and PoE with 'show power inline'.
A.On interface FastEthernet0/5: switchport voice vlan 150, power inline auto. On interface FastEthernet0/10: power inline auto. Verify with show interfaces switchport and show power inline.
B.On interface FastEthernet0/5: switchport voice vlan 150 (no PoE change). On interface FastEthernet0/10: power inline auto. Verify with show interfaces switchport and show power inline.
C.On interface FastEthernet0/5: switchport access vlan 150, power inline auto. On interface FastEthernet0/10: power inline auto. Verify with show interfaces switchport and show power inline.
D.On interface FastEthernet0/5: switchport voice vlan 150, power inline auto. On interface FastEthernet0/10: power inline never. Verify with show interfaces switchport and show power inline.
AnswerA
solution
! SW2
configure terminal
interface FastEthernet0/5
switchport voice vlan 150
power inline auto
interface FastEthernet0/10
power inline auto
end

Why this answer

Both ports have 'power inline never', so no PoE is delivered. Restore PoE with 'power inline auto' on both ports. The phone also needs the voice VLAN configured with 'switchport voice vlan 150' on Fa0/5; the data VLAN 50 for the PC and the access VLAN 100 on Fa0/10 are already configured and need no change.

Verify the voice VLAN with 'show interfaces fa0/5 switchport' and PoE with 'show power inline'.

Exam trap

Avoid adding unnecessary commands like setting the access VLAN on a port that already has it configured. Also, use the correct show command: show interfaces switchport for voice VLAN, not show vlan or show interfaces trunk.

Why the other options are wrong

B

The phone port is left with PoE disabled.

C

The access VLAN carries the PC's data; the voice VLAN needs switchport voice vlan.

D

The access point port must have PoE enabled with power inline auto.

6
MCQmedium

Two switches are connected by an 802.1Q trunk. Hosts in VLAN 30 cannot communicate across the link, but VLAN 10 works. What is the most likely cause?

A.VLAN 30 is missing from the allowed VLAN list on SW2
B.VLAN 10 must be removed for VLAN 30 to pass
C.The trunk should use ISL instead of 802.1Q
D.The port on SW1 should be changed to access mode
AnswerA

SW2's trunk port has an allowed VLAN list that includes only VLANs 10 and 20, so tagged frames for VLAN 30 are not forwarded from SW1 to SW2. The switchport trunk allowed vlan command acts as a filter, and VLAN 30 is excluded, causing the hosts in VLAN 30 to lose communication across the trunk. To fix the issue, the allowed list on SW2 must be updated to include VLAN 30.

Why this answer

When one VLAN works across a trunk but another does not, the most likely cause is that the failing VLAN is missing from the allowed VLAN list on one or both switches. This is often confirmed by a 'show interfaces trunk' command. Option B is incorrect because removing VLAN 10 would break an already working VLAN and does not address VLAN 30.

Option C is incorrect because both ISL and 802.1Q carry multiple VLANs; the issue is not the encapsulation protocol. Option D is incorrect because changing a trunk port to access mode would disable the trunk entirely, preventing all VLAN traffic.

Exam trap

Beware of confusing native VLAN issues with allowed VLAN list configurations. Native VLAN problems affect untagged traffic, not specific VLANs.

Why the other options are wrong

B

Removing VLAN 10 from the allowed list would break an already functioning VLAN and would not fix VLAN 30.

C

Both ISL and 802.1Q support multiple VLANs; the problem is not the trunking protocol but the allowed VLAN list.

D

Changing a trunk port to access mode would terminate the trunk, preventing all VLAN traffic across the link.

7
MCQhard

A switchport connected to another switch should carry VLANs 10, 20, and 30. The interface is operational, but only VLAN 10 works. VLANs 20 and 30 fail. Which explanation is most likely if the port was accidentally configured as an access port in VLAN 10?

A.The interface is carrying only VLAN 10 because an access port does not transport multiple VLANs like a trunk.
B.VLAN 20 and 30 require different IP subnet masks on the switches.
C.Every inter-switch link must use a routed port instead of a trunk.
D.STP blocks all VLANs except VLAN 10 by design.
AnswerA

An access port is configured to carry exactly one VLAN and frames on that link are untagged. A switch-to-switch link that needs to carry VLANs 10, 20, and 30 must be configured as a trunk using 802.1Q tagging, which preserves VLAN membership by inserting a VLAN ID header. Because the port is set to access mode in VLAN 10, it drops or ignores frames from other VLANs, explaining why only VLAN 10 works.

Why this answer

An access port is limited to a single VLAN, so only VLAN 10 traverses the link. Option B is incorrect: IP subnet masks are irrelevant on switchports that operate at Layer 2. Option C is incorrect: inter-switch links typically use trunk ports, not routed ports.

Option D is incorrect: STP does not block based on VLAN IDs; it blocks redundant paths, not specific VLANs.

Exam trap

Be careful not to confuse access port limitations with trunk configuration issues. Always verify the port mode when troubleshooting VLAN connectivity.

Why the other options are wrong

B

IP subnet masks are Layer 3 concepts and do not affect Layer 2 VLAN propagation across a switchport. The issue here is purely Layer 2, related to the switchport mode (access vs. trunk), not IP addressing. VLANs 20 and 30 would still fail regardless of subnet mask configuration.

C

Routed ports are Layer 3 interfaces used for routing between networks, not for carrying multiple VLANs. The standard method for carrying multiple VLANs between switches is to use a trunk port, which tags frames with VLAN IDs. A routed port would not solve the issue and would break Layer 2 connectivity.

D

STP (Spanning Tree Protocol) prevents loops by blocking redundant paths, but it does not selectively block specific VLANs based on their VLAN ID. If STP were blocking VLANs 20 and 30, it would be due to a misconfiguration like PVST+ inconsistencies, not by design. The scenario describes a simple access port misconfiguration, not an STP issue.

8
Multi-Selectmedium

A network technician is troubleshooting a Cisco switch that is not forwarding traffic on a VLAN. The technician suspects a VLAN configuration issue. Which two commands can be used to verify VLAN configuration and port membership? (Choose two.)

Select 2 answers
A.show ip interface brief
B.show interfaces switchport
C.show mac address-table
D.show running-config
E.show vlan brief
AnswersB, E

The show interfaces switchport command displays detailed switchport information for each interface, including administrative and operational mode, access VLAN, trunk VLANs, and whether the port is a member of a VLAN. It helps verify that a port is correctly assigned to the intended VLAN and is in the correct mode. This command is more detailed than show vlan brief and is useful for pinpointing misconfigurations.

Why this answer

To verify VLAN configuration and port membership on a Cisco switch, the most direct commands are show vlan brief and show interfaces switchport. The former provides a summary of VLANs and their associated ports, while the latter gives detailed per-interface switchport information, including access VLAN and trunk settings. Together, they allow a technician to confirm that VLANs exist and that ports are assigned correctly.

Exam trap

The trap here is selecting show mac address-table or show running-config, which can provide VLAN information but are not the primary commands for verifying VLAN configuration and port membership.

9
MCQhard

A switchport is configured as an access port in VLAN 10, but a user plugs in a small unmanaged switch and connects multiple devices behind it. Which security feature most directly limits that behavior at the switchport?

B.OSPF authentication
C.NetFlow
D.NTP
AnswerA

Port security is the correct answer because it operates directly at the switchport to restrict the number of and identity of MAC addresses allowed to send traffic. On an access port in VLAN 10, you can configure a maximum MAC address count and define allowed MACs, triggering protection actions like shutdown or restrict when a violation occurs. This functionality precisely limits endpoint behavior and secures the access layer.

Why this answer

Port security most directly limits that behavior because it can restrict how many MAC addresses are learned on the switchport. In practical terms, if the interface is supposed to support one endpoint but suddenly begins presenting multiple MAC addresses from a downstream mini-switch, port security can detect and react to that change.

This is a classic access-layer control question. VLAN assignment alone does not limit how many devices appear behind the port.

Exam trap

A frequent exam trap is assuming that VLAN assignment alone restricts the number of devices behind a switchport. VLANs only segregate traffic logically and do not prevent multiple MAC addresses from appearing on a port. Another common mistake is selecting unrelated options like OSPF authentication, which secures routing protocol exchanges but does not control Layer 2 access.

NetFlow and NTP are also unrelated to limiting connected devices. The key is recognizing that only port security directly limits how many MAC addresses can be learned on a port, thus controlling the number of connected devices.

Why the other options are wrong

B

OSPF authentication is unrelated to switchport security; it protects routing protocol exchanges but does not control physical or MAC-level access on a switchport.

C

NetFlow is a traffic monitoring tool that provides visibility into network flows but does not enforce any limits on the number of devices connected to a switchport.

D

NTP is used for time synchronization across network devices and does not provide any mechanism to restrict or control devices connected to a switchport.

10
Drag & Dropmedium

Drag and drop the commands into the correct order to configure the router subinterface for VLAN 10 in a router-on-a-stick design (the 802.1Q trunk to the switch is already in place). Select the correct sequence.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4
5Step 5
6Step 6
7Step 7

Why this order

A subinterface is created from global configuration mode (configure terminal, then interface GigabitEthernet0/0.10). The encapsulation dot1Q 10 command must be applied next, because IOS accepts an IP address on a LAN subinterface only after the subinterface has been assigned an 802.1Q VLAN. Finally the VLAN's default gateway address is configured with ip address 192.168.10.1 255.255.255.0.

11
PBQmedium

You are connected to SW1. SW1 and SW2 have two redundant links (G0/1 and G0/2 on each switch). The administrator wants to use both links as one logical link with an LACP EtherChannel carrying VLAN 1 as an access port-channel. The same configuration is applied on both switches. Select the correct configuration.

Network Topology
G0/1G0/1EtherChannelSW1SW2

Hints

  • •LACP uses modes active or passive; both sides must be active or one active and one passive.
  • •The physical interfaces must have the same configuration before being added to the port-channel.
  • •The port-channel interface inherits the configuration applied to it, not the physical interfaces.
A.interface port-channel 1 switchport mode access switchport access vlan 1 interface range GigabitEthernet0/1-2 channel-group 1 mode active
B.interface port-channel 1 switchport mode trunk switchport trunk allowed vlan 1 interface range g0/1-2 channel-group 1 mode desirable
C.interface port-channel 1 switchport mode access switchport access vlan 1 interface range g0/1-2 channel-group 1 mode passive
D.interface port-channel 1 switchport mode access switchport access vlan 1 interface g0/1 channel-group 1 mode active interface g0/2 channel-group 2 mode active
AnswerA
solution
! SW1
interface GigabitEthernet0/1
channel-group 1 mode active
interface GigabitEthernet0/2
channel-group 1 mode active
interface Port-channel1
switchport mode access
switchport access vlan 1

! SW2
interface GigabitEthernet0/1
channel-group 1 mode active
interface GigabitEthernet0/2
channel-group 1 mode active
interface Port-channel1
switchport mode access
switchport access vlan 1

Why this answer

An LACP EtherChannel uses channel-group <n> mode active (or passive) on the member interfaces; at least one side must be active. The port-channel interface carries the Layer 2 settings (switchport mode access, access VLAN 1), and the members must use the same channel-group number. Option B uses mode desirable, which is PAgP, and trunk mode.

Option C uses passive on both switches, so no LACP packets are initiated and the channel never forms. Option D puts G0/2 in a different group, so the links are not bundled together.

Exam trap

Be careful to distinguish between LACP modes (active/passive) and PAgP modes (desirable/auto). Also, remember that all interfaces in an EtherChannel must use the same channel-group number and have consistent switchport settings. A common mistake is to configure trunk when an access port is needed, or to use passive on both sides, which prevents the bundle from forming.

Why the other options are wrong

B

desirable is a PAgP mode, and the task asks for LACP.

C

At least one side of an LACP channel must be active.

D

Members must use the same channel-group number.

12
PBQhard

You are connected to SW1. Configure an LACP EtherChannel between SW1 and SW2 using interfaces GigabitEthernet0/1 and GigabitEthernet0/2. The port-channel interface must be configured as a trunk allowing VLANs 10, 20, and 30. Currently, the channel is not forming due to a mismatch in speed/duplex and VLAN configuration on SW2. Troubleshoot and resolve the issue so that the EtherChannel comes up as a Layer 2 trunk.

Network Topology
Gi0/1Gi0/1LACP EtherChannelSW1SW2

Hints

  • •Check the speed and duplex settings on SW2's physical interfaces.
  • •Compare the allowed VLAN list on SW2's physical interfaces to the port-channel trunk.
  • •Use 'show etherchannel summary' to see if ports are bundled or down.
A.On SW2, configure interfaces GigabitEthernet0/1 and 0/2 with speed 1000, duplex full, and on the port-channel interface, set allowed VLANs to 10,20,30.
B.On SW2, configure interfaces GigabitEthernet0/1 and 0/2 with speed 100, duplex half, and on the port-channel interface, set allowed VLANs to 10,20,30.
C.On SW2, configure interfaces GigabitEthernet0/1 and 0/2 with speed 1000, duplex full, and on the port-channel interface, set allowed VLANs to 10,20.
D.On SW2, configure interfaces GigabitEthernet0/1 and 0/2 with speed 1000, duplex full, and on the port-channel interface, set allowed VLANs to 1-4094.
AnswerA
solution
! SW2
configure terminal
interface range gigabitEthernet0/1 - 2
speed 1000
duplex full
exit
interface port-channel1
switchport trunk allowed vlan 10,20,30
end

Why this answer

SW2's member ports use speed 100/duplex half, while SW1's use 1000/full, so the links do not come up at the same speed and duplex and cannot be bundled (all members must match). In addition, SW2's trunk allows only VLANs 10 and 20 while SW1 allows 10,20,30; the trunk configuration of the port-channel and its members must also be consistent between the switches. The fix on SW2 is speed 1000/duplex full on Gi0/1 and Gi0/2, and allowed VLANs 10,20,30 on Port-channel1 (which applies to the member ports).

Exam trap

The exam trap is that candidates may focus solely on the speed/duplex mismatch and forget to verify the VLAN allowed list on the trunk. Also, they might incorrectly try to match by lowering SW1's settings instead of raising SW2's.

Why the other options are wrong

B

The speed and duplex mismatch is not fixed.

C

The allowed VLAN list still omits VLAN 30.

D

The allowed list does not match the required VLANs 10,20,30.

13
MCQhard

A switch trunk must carry VLANs 10, 20, and 30, but traffic for VLAN 20 is failing. The trunk allowed list on one side is `10,30`. What is the most likely cause?

A.VLAN 20 is missing from the allowed VLAN list on one side of the trunk.
B.The trunk must be converted to an access port for VLAN 20 to work.
C.VLAN 20 must always be the native VLAN.
D.The switches must both use ISL instead of 802.1Q.
AnswerA

The allowed VLAN list is a per-trunk filter that determines which VLANs are permitted to traverse the link. If VLAN 20 is omitted from the 'switchport trunk allowed vlan' command on either side, frames tagged for VLAN 20 will be discarded at that interface, even though the trunk itself is up. The fix is to explicitly add VLAN 20 to the allowed list on the affected side. Since this is a static configuration error, no other trunk parameter or encapsulation change is needed.

Why this answer

The most likely cause is that VLAN 20 is not in the allowed VLAN list on one side of the trunk. Option B is incorrect because converting the trunk to an access port would block all other VLANs, not just fix VLAN 20. Option C is incorrect because there is no requirement that VLAN 20 must be the native VLAN; native VLAN is unrelated to allowed list filtration.

Option D is incorrect because ISL vs 802.1Q does not affect per-VLAN filtering; the allowed list is a separate configuration independent of the encapsulation type.

Exam trap

Focus on the allowed list configuration, not on VLAN existence or trunk mode. Misconfigurations in allowed lists are a common trap.

Why the other options are wrong

B

Converting the trunk to an access port would remove all other VLANs, not solve the selective failure for VLAN 20.

C

There is no requirement that VLAN 20 must be the native VLAN; the native VLAN is used for untagged traffic and is unrelated to the allowed VLAN list.

D

The encapsulation type (ISL vs 802.1Q) does not affect per-VLAN allowed lists; the issue is purely about the allowed list configuration.

14
MCQhard

A PC in VLAN 10 receives an APIPA address (169.254.x.x). The DHCP server is on a different subnet, reached through router R1. The server's pool has many free addresses, and PCs in the server's own subnet obtain leases normally. There is no firewall in the path and DHCP snooping is not enabled on the access switch. The PC's NIC shows 'connected'. What should the technician check next?

A.Check the PC's switch port for a rogue DHCP server handing out leases.
B.Verify that no firewall is blocking UDP ports 67 and 68 between the PC and the server.
C.Run the ipconfig /release and /renew commands on the client.
D.Verify that the R1 interface for VLAN 10 has an ip helper-address pointing to the DHCP server.
AnswerD

Because the server is in a different subnet, R1 must relay the PC's broadcast DHCP Discover as unicast to the server with ip helper-address on the VLAN 10 interface. Without it no Offer is ever returned and the PC falls back to APIPA.

Why this answer

An APIPA address means the PC never received a DHCP Offer. DHCP Discover is a broadcast that R1 does not forward to another subnet unless the router interface in VLAN 10 is configured with 'ip helper-address <DHCP server>'. With the server healthy, the pool available and no firewall or snooping in the path, the missing helper-address on R1 is the most likely cause, so that is what to verify next.

A rogue DHCP server would hand out a valid (wrong) address, not an APIPA address.

Exam trap

Cisco often tests the concept that APIPA addresses are self-assigned and indicate a failure to receive a DHCP offer, and the trap here is that candidates assume the problem is with the legitimate DHCP server's configuration or connectivity, rather than considering a rogue DHCP server that is interfering with the process.

Why the other options are wrong

A

A rogue server answers clients, so the client would not fall back to APIPA.

B

No firewall exists in the path, according to the scenario.

C

The renewed broadcast Discover still will not reach the remote server.

15
MCQmedium

A network administrator is configuring VLANs on a Cisco Catalyst switch. The design requires that VLAN 10 traffic and VLAN 20 traffic share the same physical uplink to a router, but each VLAN must remain logically separate at Layer 2. The router interface is configured with 802.1Q encapsulation. Which statement correctly describes how the router will process frames arriving from both VLANs on that single physical interface?

A.The router will use subinterfaces, each associated with a VLAN ID, to terminate the 802.1Q tags and route between the VLANs.
B.The router will forward tagged frames between VLAN 10 and VLAN 20 at Layer 2, acting as a transparent bridge for those VLANs.
C.The router will strip the 802.1Q tag and route traffic between VLAN 10 and VLAN 20 without requiring any subinterfaces.
D.The router will require a separate physical interface for each VLAN because 802.1Q does not support multiple VLANs on one link.
AnswerA

Router-on-a-stick uses subinterfaces configured with encapsulation dot1q <vlan-id> so the router can terminate each VLAN tag and treat each subinterface as a distinct Layer 3 gateway. This keeps VLAN 10 and VLAN 20 logically separate while sharing one physical uplink. Traffic between the VLANs is then routed by the router, satisfying the design requirement.

Why this answer

Router-on-a-stick uses a single physical router interface configured with 802.1Q encapsulation and multiple subinterfaces, each mapped to a VLAN ID. The router terminates the VLAN tags, assigns each subinterface an IP address as the default gateway for that VLAN, and routes traffic between VLANs at Layer 3. This meets the requirement of sharing one uplink while maintaining logical separation of VLAN 10 and VLAN 20.

Exam trap

The trap here is assuming that a single router interface with 802.1Q encapsulation can route between VLANs without subinterfaces, when in fact each VLAN needs its own logical subinterface to terminate the tag.

16
MCQhard

A network administrator has configured HSRP between RouterA and RouterB for VLAN 10. End hosts using the virtual IP 192.168.1.1 as their default gateway experience intermittent connectivity losses, and pings to 192.168.1.1 often fail. The output of 'show standby brief' on both routers shows the state as Active. What is the most likely cause?

A.The virtual IP address is configured on only one router.
B.The routers are configured with mismatched HSRP authentication methods.
C.The HSRP group number on one router is set to 0.
D.The priority on both routers is configured to the same value.
AnswerB

Mismatched authentication (e.g., MD5 vs. text) causes each router to disregard the other's HSRP hellos. Each then assumes no peers exist and becomes Active, leading to both routers claiming the virtual IP and MAC, which results in ARP table flapping and intermittent connectivity.

Why this answer

When both routers show the HSRP state as Active, a 'dual-active' scenario exists, which causes intermittent connectivity because both routers forward traffic for the virtual IP. Mismatched HSRP authentication methods (e.g., one router using plain-text authentication and the other using MD5) prevent the routers from exchanging proper Hello messages, so they fail to negotiate a single Active router. This is the most likely cause because authentication mismatches break the HSRP adjacency, leading to both routers assuming the Active role.

Exam trap

Cisco often tests the concept that HSRP authentication mismatches cause a dual-active failure, while candidates may incorrectly assume that equal priorities or group number 0 are the root cause.

Why the other options are wrong

A

A missing virtual IP on one router does not cause both to be Active; the router without the virtual IP cannot claim the Active role for that address.

C

A group number mismatch does not cause both routers to appear as Active for the same virtual IP; they would be in separate groups.

D

Equal priority does not lead to multiple Active routers; HSRP uses the interface IP address as a tiebreaker to elect a single Active router.

17
MCQhard

A trunk link between two switches is up, but voice phones connected through one access switch no longer receive the correct voice VLAN treatment. Data users still pass traffic. Which area should be checked first?

A.Whether the voice VLAN is being carried and handled correctly across the switching path.
B.Whether OSPFv3 neighbors are fully adjacent on the phone switch ports.
C.Whether the wireless controller has the correct guest SSID.
D.Whether BGP uses a lower metric than the static route.
AnswerA

The correct focus is verifying that the voice VLAN is configured and permitted consistently across the entire switching path: the access ports connected to phones must carry the auxiliary voice VLAN, and the trunk between the switches must include that VLAN in its allowed list without stripping or re-tagging it incorrectly. Because the trunk is up but phones fail selectively, the fault almost certainly lies in voice VLAN propagation or 802.1Q tagging, not in physical connectivity or routing. Checking the voice VLAN's allowed status and native VLAN behavior on the trunk will reveal the misconfiguration.

Why this answer

The first area to check is the end-to-end handling of the voice VLAN across the switching path. In practical terms, the data VLAN can still work while the voice VLAN experiences a forwarding, configuration, or policy problem. Because the phones depend on the correct voice VLAN behavior, that VLAN path should be examined first rather than assuming the whole trunk is broken.

This is a selective-services troubleshooting question. One class of traffic can fail even when ordinary user data still works.

Exam trap

Be cautious not to assume that a general network issue is the cause when only specific traffic types are affected. Focus on the specific VLAN configuration first.

Why the other options are wrong

B

OSPFv3 is an IPv6 routing protocol and has no role in Layer 2 voice VLAN handling on access ports. The issue is about VLAN assignment and trunking, not routing protocol adjacency.

C

The scenario involves wired switches and IP phones, not wireless LAN. Guest SSID configuration on a wireless controller is unrelated to voice VLAN treatment on a wired trunk link.

D

BGP is an exterior routing protocol used for interdomain routing, not for Layer 2 VLAN handling. The symptom is about voice VLAN treatment on a trunk, which is unrelated to BGP metrics or static routes.

18
PBQhard

You are connected to R1. R1 and R2 are HSRP peers for VLAN 100 (group 1, virtual IP 192.0.2.254). R2 uses the default priority 100. R1 must be the active gateway, preempt, and track its G0/1 interface with a decrement of 20. The exhibit shows R1's current state. Which change on R1 makes R1 the active router?

Hints

  • •When priorities are equal, the router with the higher IP address becomes active.
  • •Preempt only takes effect if R1 has a higher priority than the current active router.
A.Set the HSRP priority on R1 to 110 (standby 1 priority 110).
B.Remove the standby 1 track command from R1.
C.Configure preempt on R2.
D.Change the HSRP group number on R1 from 1 to 2.
AnswerA
solution
! R1
configure terminal
interface GigabitEthernet0/0.100
standby 1 priority 110
end

Why this answer

R1 already has the correct virtual IP, preempt and tracking. However, its priority is the default 100, the same as R2's. With equal priorities the router with the higher interface IP address wins the election, and R2 (192.0.2.2) is higher than R1 (192.0.2.1), so R2 is active.

Preempt only helps when R1's priority is higher, so R1's priority must be raised above 100, for example 'standby 1 priority 110'. R1 then preempts and becomes active.

Exam trap

Trap: Candidates may focus on the track command or preempt, but the primary issue is the virtual IP mismatch and default priority. Always verify the virtual IP belongs to the same subnet as the interface and adjust priority to ensure the desired active router.

Why the other options are wrong

B

Tracking is required, and removing it does not make R1 active.

C

This favors R2 and is outside the scope of R1.

D

A different group number removes R1 from R2's group.

19
PBQhard

You are connected to a multilayer switch MLS1. FastEthernet0/1 is currently a routed port with PoE disabled. Convert it into an access port for an IP phone and a PC, with data VLAN 10 and voice VLAN 20, and enable PoE. Select the correct configuration.

Hints

  • •The interface currently has 'no switchport' — remove that to make it a Layer 2 port.
  • •You need to set both access VLAN and voice VLAN using the switchport command.
  • •PoE is currently disabled globally or per interface — enable it with 'power inline auto'.
A.interface FastEthernet0/1 switchport switchport mode access switchport access vlan 10 switchport voice vlan 20 power inline auto
B.interface FastEthernet0/1 no switchport ip address 192.168.1.1 255.255.255.0 power inline auto
C.interface FastEthernet0/1 switchport switchport mode trunk switchport trunk allowed vlan 10,20 power inline auto
D.interface FastEthernet0/1 switchport switchport mode access switchport access vlan 10 switchport voice vlan 20 power inline never
AnswerA
solution
! MLS1
configure terminal
interface FastEthernet0/1
switchport
switchport mode access
switchport access vlan 10
switchport voice vlan 20
power inline auto
end

Why this answer

The port is a routed port ('no switchport'), so it must first be made a Layer 2 port with the switchport command (access-port commands are rejected on a routed port). It is then set to access mode with data VLAN 10 and voice VLAN 20, and PoE is restored with power inline auto (it is currently 'power inline never'). Option B keeps the port routed, option C configures a trunk, which is not used for a phone and PC, and option D leaves PoE disabled.

Exam trap

The trap is that candidates may incorrectly use 'no switchport' to make the interface a routed port, or use trunk mode instead of access mode with voice VLAN. Remember that for end devices, the port must be an access port; the voice VLAN is configured separately. Also, ensure PoE is enabled with 'auto', not 'never'.

Why the other options are wrong

B

'no switchport' creates a routed port, which cannot handle VLANs for an IP phone and PC.

C

Trunk mode is for inter-switch links, not for end devices; access mode is required.

D

'power inline never' disables PoE, but the IP phone needs power from the switch.

20
PBQmedium

You are connected to R1 via console. R1 is a router that needs to provide DHCP services to hosts on VLAN 10 (192.168.10.0/24) and VLAN 20 (192.168.20.0/24). The router has two subinterfaces on GigabitEthernet0/0: G0/0.10 (192.168.10.1/24) and G0/0.20 (192.168.20.1/24) with 802.1Q encapsulation. Configure R1 as a DHCP server for both VLANs, excluding addresses 192.168.10.1-10 and 192.168.20.1-10, with a lease of 1 day. Ensure DNS server 8.8.8.8 is provided.

Network Topology
G0/0.10192.168.10.1/24trunkR1SW1

Hints

  • •Use 'ip dhcp excluded-address' to reserve addresses.
  • •Create DHCP pools with 'network', 'default-router', and 'dns-server'.
  • •Lease time is in days; use 'lease 1' for 1 day.
A.ip dhcp excluded-address 192.168.10.1 192.168.10.10 ip dhcp excluded-address 192.168.20.1 192.168.20.10 ip dhcp pool VLAN10 network 192.168.10.0 255.255.255.0 default-router 192.168.10.1 dns-server 8.8.8.8 lease 1 ip dhcp pool VLAN20 network 192.168.20.0 255.255.255.0 default-router 192.168.20.1 dns-server 8.8.8.8 lease 1
B.ip dhcp excluded-address 192.168.10.1 192.168.10.10 ip dhcp pool VLAN10 network 192.168.10.0 255.255.255.0 default-router 192.168.10.1 dns-server 8.8.8.8 lease 1 ip dhcp pool VLAN20 network 192.168.20.0 255.255.255.0 default-router 192.168.20.1 dns-server 8.8.8.8 lease 1
C.ip dhcp excluded-address 192.168.10.1 192.168.10.10 ip dhcp excluded-address 192.168.20.1 192.168.20.10 ip dhcp pool VLAN10 network 192.168.10.0 255.255.255.0 default-router 192.168.10.1 dns-server 8.8.8.8 lease 24 ip dhcp pool VLAN20 network 192.168.20.0 255.255.255.0 default-router 192.168.20.1 dns-server 8.8.8.8 lease 24
D.ip dhcp excluded-address 192.168.10.1 192.168.10.10 ip dhcp excluded-address 192.168.20.1 192.168.20.10 ip dhcp pool VLAN10 network 192.168.10.0 255.255.255.0 default-router 192.168.10.1 dns-server 8.8.8.8 lease 0 1 ip dhcp pool VLAN20 network 192.168.20.0 255.255.255.0 default-router 192.168.20.1 dns-server 8.8.8.8 lease 0 1
AnswerA
solution
! R1
ip dhcp excluded-address 192.168.10.1 192.168.10.10
ip dhcp excluded-address 192.168.20.1 192.168.20.10
ip dhcp pool VLAN10
network 192.168.10.0 255.255.255.0
default-router 192.168.10.1
dns-server 8.8.8.8
lease 1
ip dhcp pool VLAN20
network 192.168.20.0 255.255.255.0
default-router 192.168.20.1
dns-server 8.8.8.8
lease 1

Why this answer

Option A has an exclusion for each subnet, correct dotted-decimal network statements, the right default routers and the DNS server, and 'lease 1', which means 1 day. Option B omits the exclusion for the VLAN 20 range, so addresses 192.168.20.1-10 could be leased. Option C uses 'lease 24', which IOS interprets as 24 days.

Option D uses 'lease 0 1', which is 1 hour.

Exam trap

Be careful with the lease command: the default unit is days, not hours. Also, remember that the network command in DHCP pool configuration requires a subnet mask in dotted decimal format, not CIDR prefix length. Excluded addresses are configured globally, not within the pool.

Why the other options are wrong

B

The network command in DHCP pool configuration requires a subnet mask in dotted decimal format, not CIDR notation like /24.

C

The lease command uses days as its unit; `lease 24` sets a 24-day lease, not the required 1 day.

D

The lease command sets duration in days, so `lease 24` gives a 24-day lease instead of a 1-day lease.

21
MCQhard

After configuring a trunk port to allow VLAN 40, a technician finds that VLAN 40 is not listed among the VLANs in spanning tree forwarding state in the show interfaces trunk output. What is the most likely cause?

A.The trunk port is using ISL encapsulation, which does not support VLAN 40.
B.The technician omitted the 'add' keyword when adding VLAN 40 to the allowed list, so the trunk no longer permits VLAN 40.
C.VLAN 40 has not been created in the VLAN database on the switch.
D.VTP pruning is enabled, and VLAN 40 is not needed by any downstream neighbor, so it is pruned from this trunk.
AnswerC

A VLAN must be defined in the local VLAN database for the switch to build a spanning-tree instance and forward frames for that VLAN. If it is permitted on the trunk but does not exist, the switch marks it as pruned and it will not appear in the 'VLANs in spanning tree forwarding state' list. This is the exact symptom presented.

Why this answer

VLAN 40 must exist in the local VLAN database before it can participate in spanning tree on a trunk port. Even if the trunk is configured to allow VLAN 40, if the VLAN has not been created on the switch, the spanning tree protocol will not place it in a forwarding state. The 'show interfaces trunk' output will list only VLANs that are both allowed and existent, so the absence of VLAN 40 in the forwarding state indicates it was never created.

Exam trap

Cisco often tests the distinction between allowing a VLAN on a trunk and actually creating the VLAN in the VLAN database—candidates mistakenly assume that configuring the trunk alone is sufficient for the VLAN to be operational.

Why the other options are wrong

A

Candidates might associate VLAN support with trunk encapsulation types, but ISL fully supports VLAN 40. This is a distractor.

B

This is a common operational mistake, but the resulting output would show VLAN 40 missing from the 'Vlans allowed' column, not from the forwarding list.

D

Candidates might confuse local pruning (due to non-existent VLAN) with VTP pruning. VTP pruning would also require a multi-switch VTP domain and is less likely in a standalone troubleshooting scenario.

22
MCQmedium

A client on VLAN 20 must obtain an IPv4 lease from a DHCP server located on VLAN 100. Which feature is required on the Layer 3 interface for VLAN 20?

A.NAT overload
B.DHCP relay
D.Private VLAN
AnswerB

A DHCP relay agent, configured on the VLAN 20 SVI or routed interface, listens for DHCPDISCOVER broadcasts sent by the client. It then forwards the request as a unicast to the DHCP server's IP address while adding the interface's IP address in the giaddr field, which tells the server the correct subnet for allocating an IPv4 address. The server's DHCPOFFER is relayed back to the client, enabling a successful lease across VLANs.

Why this answer

A DHCP relay agent forwards client broadcasts as unicast to the remote server, typically using ip helper-address.

Exam trap

A common exam trap is selecting NAT overload or port security as the required feature for DHCP communication across VLANs. NAT overload is used for IP address translation and does not forward DHCP broadcasts, while port security restricts MAC addresses on switch ports but does not relay DHCP messages. Another trap is confusing private VLANs with DHCP relay; private VLANs isolate Layer 2 domains but do not forward DHCP requests between VLANs.

The key is understanding that DHCP relay is the only feature that forwards DHCP broadcasts as unicast messages across Layer 3 boundaries, enabling clients on VLAN 20 to obtain leases from a DHCP server on VLAN 100.

Why the other options are wrong

A

NAT overload translates private IP addresses to a public IP for outbound traffic but does not forward DHCP broadcasts between VLANs. It is unrelated to DHCP relay functionality required for inter-VLAN DHCP communication.

C

Port security restricts which MAC addresses can connect to a switch port but does not forward DHCP broadcasts or relay DHCP messages between VLANs, so it cannot enable DHCP communication across VLANs.

D

Private VLANs isolate devices within a VLAN for security purposes but do not provide DHCP relay capabilities or forward DHCP requests between VLANs, making this option incorrect.

23
MCQhard

A switchport connected to a user workstation is placed in VLAN 30. The administrator also wants to prevent that port from learning more than one MAC address. Which feature should be configured?

AnswerA

Port security is the correct answer because it directly restricts the number of unique MAC addresses that can be learned on a switchport, typically an access port connected to an end-user workstation. By configuring a maximum MAC address count (e.g., `switchport port-security maximum 1`) and violation modes like shutdown or restrict, it mitigates MAC flooding attacks and prevents unauthorized devices from connecting to that specific interface. This feature operates entirely at layer 2 and is designed precisely for securing user-facing switchports.

Why this answer

The correct feature is port security. In practical terms, port security lets the administrator control how many MAC addresses can be learned on a switchport and what happens if that limit is exceeded. That makes it a very natural fit for a user-facing access port where one endpoint is expected and unmanaged extra devices are not.

This is a common access-layer hardening technique. VLAN assignment controls where the traffic belongs, but it does not limit who or what can appear on the port. Port security adds that second layer of control.

Exam trap

Don't confuse VLAN assignment or ACLs with port security; they serve different functions.

Why the other options are wrong

B

EtherChannel is used to aggregate multiple physical links into a single logical link for increased bandwidth and redundancy, not to limit MAC address learning on a single port. It does not provide any mechanism to restrict the number of MAC addresses learned on a switchport.

C

OSPF passive-interface is a routing protocol feature used to prevent OSPF from sending hello messages on an interface, typically used on interfaces that do not have OSPF neighbors. It has no effect on MAC address learning or switchport security.

D

Native VLAN is a concept used on trunk ports to specify the VLAN that carries untagged traffic. It does not control MAC address learning or limit the number of MAC addresses on a switchport.

24
MCQhard

PCs in VLAN 40 are not receiving addresses from the centralized DHCP server at 172.16.1.10. What should be configured on the VLAN 40 default gateway interface?

A.ip dhcp excluded-address 10.40.40.1 10.40.40.10
B.ip helper-address 172.16.1.10
C.service dhcp
D.ip default-gateway 172.16.1.10
AnswerB

The ip helper-address command must be applied to the VLAN 40 SVI (interface vlan 40). DHCP clients broadcast DHCPDISCOVER packets, and routers do not forward broadcasts by default; this command converts those broadcasts into unicasts and relays them to the DHCP server at 172.16.1.10. The server then replies with an address appropriate for VLAN 40's subnet, which is why this is the correct fix.

Why this answer

When DHCP clients and the DHCP server are on different subnets, the router interface serving the client subnet must relay broadcasts to the server with the ip helper-address command.

Exam trap

Ensure you understand the difference between DHCP relay and DHCP security features like snooping, as well as local DHCP server configuration.

Why the other options are wrong

A

The 'ip dhcp excluded-address' command is used on a DHCP server to prevent certain addresses from being assigned, not on a router interface to forward DHCP requests. This command would not help clients in VLAN 40 reach the centralized DHCP server.

C

The 'service dhcp' command globally enables the DHCP server or relay agent on a Cisco device, but it does not specify where to forward requests. Without the 'ip helper-address' command, DHCP broadcasts will not be forwarded to the server.

D

The 'ip default-gateway' command is used on a switch to set a default gateway for management purposes, not to forward DHCP broadcasts. It does not provide DHCP relay functionality.

25
MCQhard

A multilayer switch has SVIs for VLAN 10 and VLAN 20. Hosts in both VLANs can reach their local SVI, but they cannot reach each other. Which additional configuration is most likely required?

A.Enable `ip routing` on the multilayer switch.
B.Convert all access ports into trunks.
C.Make both VLANs use the same IP subnet.
D.Disable spanning tree on both VLANs.
AnswerA

Without `ip routing`, the switch enforces its default behavior as a Layer 2 device: the SVIs exist with IP addresses but no dynamic or static route is installed to move packets between VLANs. Entering `ip routing` enables the Layer 3 forwarding engine (CEF) and makes the SVIs act as routed gateway interfaces. This is the exact missing command for inter-VLAN forwarding on a multilayer switch.

Why this answer

The most likely missing configuration is `ip routing`. In practical terms, the switch already has Layer 3 gateway interfaces for the VLANs, which is why hosts can reach their local SVI. But inter-VLAN communication still requires the switch to actually route between those VLAN interfaces. Without IP routing enabled, the SVIs can exist and respond locally without forwarding traffic between them.

This is a classic multilayer-switch question because many learners assume that creating SVIs automatically enables inter-VLAN routing. It does not. The device must also be told to behave as a Layer 3 forwarding device across those VLAN interfaces.

Exam trap

Don't assume SVIs automatically enable inter-VLAN routing; IP routing must be explicitly enabled.

Why the other options are wrong

B

Converting all access ports to trunks is unnecessary and incorrect because host-facing ports should remain access ports assigned to a single VLAN. Trunks are used to carry multiple VLANs between switches, not to connect end hosts. This change would not enable inter-VLAN routing.

C

Making both VLANs use the same IP subnet would break the fundamental purpose of VLANs, which is to separate broadcast domains and logically segment the network. Hosts in different VLANs must be in different subnets for proper routing; otherwise, they would expect to communicate directly at Layer 2, which is not possible across VLANs.

D

Disabling Spanning Tree Protocol (STP) on both VLANs would not enable inter-VLAN routing; it would only risk creating Layer 2 loops and broadcast storms. STP is a loop-prevention mechanism and has no role in Layer 3 routing between VLANs.

26
MCQhard

A network engineer configures an EtherChannel between two Cisco switches SW1 and SW2 using LACP. After configuration, hosts connected to SW1 report intermittent connectivity to hosts on SW2. The engineer checks the EtherChannel status and sees that the trunk is up but only allows VLAN 1, while the hosts communicate across VLANs 10 and 20. Which command should the engineer apply to both switches to resolve the issue?

A.channel-group 1 mode active
B.switchport trunk allowed vlan 1,10,20
C.lacp rate fast
D.switchport mode trunk
AnswerB

This command ensures that all member ports of the EtherChannel have the same VLAN list. Inconsistent allowed VLANs across member ports can cause traffic to be dropped intermittently. Applying this to all member interfaces on both switches resolves the issue.

Why this answer

The output shows the EtherChannel is up but only VLAN 1 is allowed on the trunk, while the hosts on SW1 and SW2 communicate across VLANs 10 and 20. Applying 'switchport trunk allowed vlan 1,10,20' on both switches ensures all necessary VLANs are permitted over the EtherChannel, resolving the intermittent connectivity caused by dropped traffic for VLANs 10 and 20.

Exam trap

The trap here is that candidates assume the EtherChannel is fully functional once it shows as up/up, overlooking that the trunk's VLAN allowed list must match on both sides to pass traffic for all required VLANs.

Why the other options are wrong

A

The ports are already configured with LACP active mode, as indicated by the protocol being LACP and the ports being bundled. Reapplying this command does not address the root cause of intermittent connectivity, which is likely due to VLAN mismatch.

C

The 'lacp rate fast' command changes the LACP packet transmission rate to every second, which is used for faster failure detection. It does not affect VLAN consistency or cause intermittent connectivity; the issue is likely due to VLAN mismatch, not LACP rate.

D

The ports are already configured as trunk ports (the Po1 is Layer2 and trunking is implied). Reapplying 'switchport mode trunk' does not address the VLAN inconsistency that causes intermittent connectivity.

27
MCQmedium

A switch port connected to an end host should forward traffic for one VLAN only and should not negotiate trunking. Which configuration approach best fits that requirement?

A.Configure the interface with `switchport mode access`
B.Configure the interface with `switchport mode trunk`
C.Configure the interface with `switchport mode dynamic desirable`
D.Configure the interface with `no switchport`
AnswerA

Configuring 'switchport mode access' forces the interface to operate in permanent access mode, disabling Dynamic Trunking Protocol (DTP) and ensuring the port carries untagged traffic for only one VLAN—usually VLAN 1 by default unless reassigned with 'switchport access vlan'. This deterministic, secure configuration is exactly what an end host expects, because most host NICs send untagged frames and rely on the switch to place them in the proper broadcast domain. It is the industry-standard best practice for connecting PCs, printers, and other typical end devices.

Why this answer

The best approach is to configure the interface as an access port. In plain language, this tells the switch that the interface is for a normal endpoint and should belong to one VLAN rather than carry multiple VLANs like a trunk. It also avoids reliance on dynamic trunk negotiation, which is usually unnecessary and potentially confusing for a user-facing connection.

This is a standard access-layer design principle. End hosts such as PCs and printers usually connect to access ports, not trunks. That is why the correct answer is the one centered on explicit access-port behavior.

Exam trap

Avoid confusing trunking features with access port requirements. Remember, end devices typically connect via access ports.

Why the other options are wrong

B

A trunk port is designed to carry traffic for multiple VLANs between switches, not for a single end host. Using switchport mode trunk on an access port would allow multiple VLANs and enable trunk negotiation, violating the requirement.

C

The dynamic desirable mode actively attempts to form a trunk with the connected device using DTP. This allows trunk negotiation, which contradicts the requirement to not negotiate trunking and to forward traffic for only one VLAN.

D

The no switchport command converts the Layer 2 switch port into a Layer 3 routed port, which does not operate as a switch port and cannot be assigned to a VLAN. This is used for routing between VLANs, not for connecting an end host to a single VLAN.

28
MCQeasy

A technician is connecting a new Cisco switch to an existing switch using a copper cable. The link between the two switches must carry traffic for multiple VLANs. Which command must be configured on the interface connecting to the other switch to allow multiple VLANs to traverse the link?

A.switchport mode access
B.switchport mode trunk
C.switchport nonegotiate
D.switchport trunk allowed vlan all
AnswerB

Trunk mode allows an interface to carry traffic for multiple VLANs by tagging frames with 802.1Q. This is the standard configuration for inter-switch links that must transport multiple VLANs. The command switchport mode trunk places the interface in permanent trunking mode, enabling the link to carry VLAN 10, VLAN 20, and others as required by the design.

Why this answer

To carry traffic for multiple VLANs over a single inter-switch link, the interface must be configured as a trunk. The command switchport mode trunk sets the interface to permanent trunking mode, allowing 802.1Q-tagged frames for multiple VLANs to traverse the link. Other commands like nonegotiate or allowed vlan list are supplementary and only apply after trunk mode is enabled.

Exam trap

The trap here is confusing commands that modify trunk behavior, such as nonegotiate or allowed vlan, with the command that actually enables trunking, which is switchport mode trunk.

29
MCQhard

A switch has DHCP snooping enabled and Dynamic ARP Inspection enabled on VLAN 30. A printer with a static IP on VLAN 30 cannot communicate because its ARP packets are being dropped. What is the best fix?

A.Disable DAI on all VLANs globally.
B.Configure a static ARP inspection entry or ARP ACL for the printer.
C.Trust the user-facing printer access port for DHCP snooping and DAI.
D.Change the printer to use a larger MTU.
AnswerB

A printer with a static IP never generates a DHCP lease, so DAI finds no matching binding entry and discards its ARP packets. By configuring a static ARP access-list entry or a static DHCP snooping binding, you give the switch an explicit IP-to-MAC mapping to validate the printer's ARP traffic. This targeted fix resolves the issue without reducing security for other hosts.

Why this answer

DAI relies on trusted bindings. Static-IP devices that are not learned through DHCP often require a static ARP ACL or equivalent trusted binding mechanism.

Exam trap

A common exam trap is to disable Dynamic ARP Inspection entirely or trust the user-facing access port to fix ARP packet drops from static IP devices. Disabling DAI weakens the network’s ARP spoofing protection, which is against best practices and exam expectations. Trusting access ports is too broad and can allow malicious ARP traffic, defeating the purpose of DAI.

The trap is that these options seem easier but compromise security, whereas the correct approach is to configure static ARP inspection entries or ARP ACLs for static IP devices to maintain security and functionality.

Why the other options are wrong

A

Disabling DAI on all VLANs globally removes ARP spoofing protection network-wide, which is excessive and reduces security unnecessarily. The question requires a targeted fix, so this option is incorrect.

C

Trusting the user-facing printer access port for DHCP snooping and DAI is too permissive and can allow malicious ARP packets, weakening security. It is not recommended as a best practice or exam answer.

D

Changing the printer to use a larger MTU does not affect ARP packet validation or DAI behavior. MTU size is unrelated to ARP inspection, so this option is irrelevant and incorrect.

30
Multi-Selectmedium

Which TWO statements about 802.1Q trunking, native VLANs, and inter-VLAN routing are correct? (Choose two.)

Select 2 answers
A.802.1Q trunking is a Cisco-proprietary protocol that uses a 4-byte tag to identify VLAN membership.
B.By default, frames belonging to the native VLAN are sent untagged across an 802.1Q trunk.
C.Inter-VLAN routing can be accomplished using a Layer 2 switch configured with VLAN access maps.
D.The native VLAN must be identical on both ends of an 802.1Q trunk to avoid native VLAN mismatch errors.
E.Switches strip the 802.1Q tag from all frames before forwarding them out of a trunk port.
AnswersB, D

On an 802.1Q trunk, the native VLAN is deliberately transmitted without any VLAN tag. The receiving switch assumes that any untagged frame arriving on the trunk belongs to its configured native VLAN, which is why the administrator must ensure the native VLAN matches on both ends. This untagged behavior permits interoperability with devices that do not understand 802.1Q tagging and is enforced by default.

Why this answer

By default, 802.1Q trunking treats the native VLAN (typically VLAN 1) as untagged. Frames in the native VLAN are sent without an 802.1Q tag, allowing interoperability with devices that do not understand trunking. This behavior is defined in IEEE 802.1Q and is essential for backward compatibility.

Exam trap

Cisco often tests the misconception that all frames on a trunk are tagged, but the trap here is that the native VLAN is sent untagged by default, and candidates may incorrectly assume that inter-VLAN routing can be done with a Layer 2 switch alone.

Why the other options are wrong

A

802.1Q is an open IEEE standard. Cisco-proprietary trunking is Inter-Switch Link (ISL).

C

Layer 2 switches cannot route between VLANs. Inter-VLAN routing requires a Layer 3 device such as a router or a Layer 3 switch with SVIs.

E

Trunk ports forward tagged frames so the receiving switch can distinguish VLANs. Removing tags from all frames would defeat the purpose of trunking.

31
MCQmedium

A switchport is configured as an access port for VLAN 20, but users connected to it cannot reach the default gateway. The switch shows the interface as up/up. Which switch misconfiguration is the most likely cause?

A.The access port is missing a speed command
B.VLAN 20 has not been created on the switch
C.The switch has not enabled VTP transparent mode
D.The port should use DTP desirable mode
AnswerB

When a switchport is configured as an access port in a VLAN that does not exist in the switch's VLAN database, the port stays up/up physically but is listed as inactive in the VLAN table and forwards no traffic for that VLAN. Creating the VLAN with 'vlan 20' in global configuration mode is required before the access port can pass traffic for VLAN 20. The interface line protocol can look healthy, which is exactly why this fault is easy to miss.

Why this answer

If the access port is assigned to VLAN 20 but VLAN 20 does not exist in the VLAN database, traffic is not placed into a usable VLAN and hosts lose connectivity. The port can still appear physically up while forwarding fails at Layer 2.

Exam trap

A common exam trap is assuming that an interface showing up/up means the port is fully functional and correctly forwarding traffic. Candidates may overlook the necessity of creating the VLAN in the switch’s VLAN database. Without VLAN 20 existing, the switch cannot forward traffic for that VLAN, even though the physical link is active.

This leads to confusion because the interface status does not reflect VLAN misconfiguration, causing users to lose connectivity to the default gateway despite the port appearing operational.

Why the other options are wrong

A

The absence of a speed command on the access port does not prevent VLAN forwarding or connectivity to the default gateway. Speed settings affect physical link parameters but not VLAN membership or Layer 2 forwarding.

C

VTP transparent mode controls VLAN propagation between switches but does not affect whether a VLAN exists locally. Missing VLANs must be created manually regardless of VTP mode.

D

DTP desirable mode is used to negotiate trunk links and is irrelevant for access ports, which do not trunk and only carry untagged frames for a single VLAN.

32
MCQmedium

A switch interface connects to a user PC and should belong only to VLAN 30. Which command assigns that VLAN after the interface is in access mode?

A.switchport access vlan 30
B.switchport trunk allowed vlan 30
C.encapsulation dot1Q 30
D.ip helper-address 30
AnswerA

This is the correct command to place an interface into VLAN 30 as an access port. When configured on a switchport that is set to access mode, it assigns that single VLAN to the port, allowing the user PC to communicate with other devices in VLAN 30 while isolating it from other VLANs. This is the standard method for connecting end devices like PCs, printers, and IP phones to a switch.

Why this answer

After an interface is placed into access mode, the command used to assign its VLAN is `switchport access vlan 30`. In plain language, this tells the switch which VLAN the endpoint traffic on that access port belongs to. Access mode defines the role of the interface, and the access VLAN command defines the specific VLAN membership for that role.

This distinction matters because some commands change the port’s behavior while others set the VLAN it uses. The correct answer is the one that directly assigns VLAN 30 to the access port rather than modifying a trunk or a native VLAN setting.

Exam trap

Be careful not to confuse commands for trunk ports with those for access ports. Ensure you understand the difference between setting a port mode and assigning a VLAN.

Why the other options are wrong

B

The command 'switchport trunk allowed vlan 30' is used on trunk ports to specify which VLANs are allowed to traverse the trunk link. It does not assign a VLAN to an access port; instead, it filters VLANs on a trunk, which is not appropriate for a port connected to a single PC.

C

The command 'encapsulation dot1Q 30' is used on a router subinterface to enable 802.1Q trunking and specify the VLAN for that subinterface. It is not a valid command on a switch access port, and switch ports do not use encapsulation commands for VLAN assignment.

D

The command 'ip helper-address 30' is used to configure DHCP relay on a router or Layer 3 switch interface, forwarding DHCP broadcasts to a DHCP server. It has nothing to do with VLAN assignment on a switch port.

33
MCQhard

PCs in VLAN 30 on SwitchA cannot reach PCs in VLAN 30 on SwitchB. VLAN 30 exists on both switches and all other VLANs work across the same link. Based on the exhibit, what is the most likely cause?

A.VLAN 30 is not allowed on the trunk from SwitchA.
B.The native VLAN is mismatched.
C.The trunk must use ISL instead of 802.1Q.
D.VLAN 30 must be configured as the native VLAN.
AnswerA

VLAN 30 is not included in SwitchA's trunk allowed list, so frames from VLAN 30 are not forwarded over the trunk to SwitchB. Unlike the native VLAN, which is untagged, VLAN 30 must be explicitly permitted with the switchport trunk allowed vlan command on both ends. Without this entry, all VLAN 30 traffic remains isolated to the local switch, preventing PCs on SwitchB from reaching those on SwitchA.

Why this answer

The trunk is up, but VLAN 30 is missing from the allowed list on SwitchA. In plain language, the hallway between the switches is open, but one side is refusing to carry that specific VLAN through the hallway. Since the other VLANs are working, the failure is selective rather than total. That strongly points to an allowed-VLAN problem rather than a broader trunk outage.

This is a classic CCNA switching scenario because it tests whether you can separate trunk health from per-VLAN forwarding. A trunk can be operational and still block one VLAN if that VLAN is not permitted on one side. The native VLAN and encapsulation are not the issue shown here — the mismatch in the allowed list is.

Exam trap

Be careful not to confuse general trunk issues with specific VLAN forwarding problems. Always check the allowed VLAN list when specific VLANs fail to pass.

Why the other options are wrong

B

The exhibit shows both switches have native VLAN 1 configured, so there is no mismatch. A native VLAN mismatch would affect untagged traffic and trigger STP/CDP warnings, not selectively block a single tagged VLAN.

C

Since other VLANs are working across the same trunk, the trunk encapsulation (802.1Q) is functioning correctly. Changing to ISL would not fix the issue and would break connectivity for all VLANs.

D

A VLAN does not need to be the native VLAN to traverse a trunk; native VLAN is only for untagged traffic. Making VLAN 30 the native VLAN would not solve the problem and could introduce other issues.

34
PBQhard

You are connected to SW1 via the console. The network uses Rapid PVST+ and SW1 must become the root bridge for VLAN 10 and VLAN 20. GigabitEthernet0/1 connects to a workstation and uses PortFast with BPDU Guard. After the workstation was replaced with another device, the port went err-disabled. Fix the root bridge priority and recover the port without reloading the switch.

Network Topology
Gi0/1Gi0/2SW1workstationother switch

Hints

  • •Use 'spanning-tree vlan <vlan> priority <value>' with a value lower than the current root's; priorities are multiples of 4096.
  • •A port err-disabled by BPDU Guard needs the BPDU source removed and then shutdown / no shutdown.
  • •show interfaces status err-disabled gives the reason.
A.Configure spanning-tree vlan 10 priority 4096 and spanning-tree vlan 20 priority 4096. On GigabitEthernet0/1 remove the device that sent BPDUs, then enter shutdown followed by no shutdown.
B.Configure spanning-tree vlan 10 priority 4096 and spanning-tree vlan 20 priority 4096. Reload the switch to recover GigabitEthernet0/1.
C.Configure spanning-tree vlan 10 priority 40960 and spanning-tree vlan 20 priority 40960. Then shutdown and no shutdown GigabitEthernet0/1.
D.Configure spanning-tree vlan 10 priority 4096 and spanning-tree vlan 20 priority 4096. Recover the port with clear spanning-tree detected-protocols.
AnswerA
solution
! SW1
spanning-tree vlan 10 priority 4096
spanning-tree vlan 20 priority 4096
interface GigabitEthernet0/1
shutdown
no shutdown

Why this answer

SW1 is not the root bridge for either VLAN: the root has priority 24586 (VLAN 10) and 24596 (VLAN 20), while SW1 has 32778 and 32788. Setting spanning-tree vlan 10 priority 4096 and spanning-tree vlan 20 priority 4096 makes SW1's priority lower (4106 and 4116) so it wins the election. Gi0/1 is err-disabled with reason bpduguard because a device sending BPDUs (another switch) was connected to the PortFast port.

Remove that device, then issue shutdown and no shutdown on the interface.

Exam trap

Do not confuse 'root primary' with a guaranteed root election; always check for lower priorities. Also, remember that err-disabled ports require manual intervention (shutdown/no shutdown) unless you configure errdisable recovery. BPDU Guard err-disables the port; simply disabling BPDU Guard does not recover it.

Why the other options are wrong

B

Incorrect: the task requires recovering the port without a reload, and shutdown followed by no shutdown is enough.

C

Incorrect: 40960 is higher (worse) than the current root's priorities, so SW1 would not become root.

D

Incorrect: clear spanning-tree detected-protocols does not clear the err-disabled state; the interface must be bounced.

35
MCQhard

A network technician is troubleshooting a connectivity issue for a PC connected to switch port Gi1/0/12. The PC can ping its default gateway (192.168.10.1) but cannot ping a server at 192.168.20.10. The switch is configured with VLAN 10 for the access port and is connected to a router-on-a-stick. The technician runs 'show vlan brief' and 'show interfaces trunk' on the switch. What is the most likely cause of the problem?

A.The trunk port Gi1/0/24 is not in trunking mode.
B.The router is missing a subinterface for VLAN 20.
C.The switch port Gi1/0/12 is not assigned to VLAN 10.
D.The PC has a duplicate IP address with the server.
AnswerB

This is the correct answer because the router is configured for router-on-a-stick inter-VLAN routing but only has a subinterface for VLAN 10. Since the router lacks a subinterface with the appropriate 802.1Q encapsulation and an IP address in the VLAN 20 subnet, it simply drops or ignores VLAN 20 frames arriving over the trunk. Even though the switch and trunk are configured correctly, VLAN 20 hosts have no default gateway on the router and therefore cannot route traffic to VLAN 10 or any other network.

Why this answer

The PC can ping its default gateway (192.168.10.1) but not the server at 192.168.20.10, indicating Layer 3 routing is failing between VLANs. Since the switch is configured with VLAN 10 for the access port and uses a router-on-a-stick, the router must have a subinterface for VLAN 20 to route traffic to the server's subnet. The absence of a subinterface for VLAN 20 prevents the router from forwarding packets from VLAN 10 to VLAN 20, making option B correct.

Exam trap

Cisco often tests the misconception that a trunk misconfiguration (option A) is the cause, but the PC's ability to ping the gateway confirms the trunk is working for VLAN 10, so the real issue is the missing subinterface for the destination VLAN.

Why the other options are wrong

A

The trunk port Gi1/0/24 is in 'on' mode and trunking, as shown in 'show interfaces trunk'. Therefore, the trunk is operational and not the cause of the issue.

C

The 'show vlan brief' output shows that port Gi1/0/12 is assigned to VLAN 10, so the PC is in the correct VLAN. This is not the issue.

D

A duplicate IP address would cause connectivity issues to the gateway as well, but the PC can ping the gateway successfully. Therefore, duplicate IP is not the problem.

36
MCQhard

Refer to the exhibit. A network administrator is troubleshooting a connectivity issue between two remote sites connected via a WAN link. Hosts on VLAN 10 at Site A (192.168.10.0/24) cannot ping the server at Site B (10.10.20.100). The configuration on RouterA contains 'ip route 0.0.0.0 0.0.0.0 10.10.10.2', but the default route does not appear in the routing table. What is the most likely cause of the problem?

A.The 10.10.20.0/24 server subnet has no specific route, which prevents the default route from being installed.
B.The GigabitEthernet0/0 interface is administratively down.
C.The default route is not configured; the gateway of last resort is missing.
D.The next-hop router 10.10.10.2 is unreachable.
AnswerD

The connected subnet on GigabitEthernet0/0 is 10.10.10.4/30, which does not include 10.10.10.2. No other route reaches the next hop, so the static default route cannot be installed.

Why this answer

A static route with a next-hop IP address is installed only if the next hop resolves through a connected or other route in the routing table. GigabitEthernet0/0 is up with the connected network 10.10.10.4/30 (hosts .5 and .6), so 10.10.10.2 is not inside any connected subnet and no other route reaches it. The default route stays in the configuration but is not installed, and the gateway of last resort is not set.

The next hop 10.10.10.2 is unreachable.

Exam trap

Candidates assume a configured static route is always in the routing table. A static route that uses a next-hop address is installed only when that address is reachable via a route that is already present.

Why the other options are wrong

A

The installation of a default route does not depend on specific routes to remote subnets.

B

The connected route proves the interface is up/up.

C

The route is configured but not installed; the gateway of last resort is unset because of that.

37
PBQhard

You are connected to a Multilayer Switch MLS1. Configure the switch so that interface GigabitEthernet1/0/1 is an access port for VLAN 10, with voice VLAN 110 for an IP phone, and enable PoE. Additionally, interface GigabitEthernet1/0/2 must be an access port for VLAN 20 to connect an AP. Verify the configuration using 'show interfaces switchport' and 'show power inline'.

Network Topology
G1/0/1G1/0/2SiMLS1IP PhoneAP

Hints

  • •Use 'switchport mode access' to set the port as an access port.
  • •For the IP phone port, apply both 'switchport access vlan' and 'switchport voice vlan' commands.
  • •PoE is enabled by default but ensure 'power inline auto' is configured.
A.Gi1/0/1: switchport mode access, switchport access vlan 10, switchport voice vlan 110, power inline auto. Gi1/0/2: switchport mode access, switchport access vlan 20.
B.Gi1/0/1: switchport mode trunk, switchport trunk allowed vlan 10,110, power inline auto. Gi1/0/2: switchport mode access, switchport access vlan 20.
C.Gi1/0/1: switchport mode access, switchport access vlan 10, switchport voice vlan 110, power inline never. Gi1/0/2: switchport mode access, switchport access vlan 20.
D.Gi1/0/1: switchport mode access, switchport access vlan 110, switchport voice vlan 10, power inline auto. Gi1/0/2: switchport mode access, switchport access vlan 20.
AnswerA
solution
! MLS1
interface GigabitEthernet1/0/1
switchport mode access
switchport access vlan 10
switchport voice vlan 110
power inline auto
exit
interface GigabitEthernet1/0/2
switchport mode access
switchport access vlan 20
exit

Why this answer

Gi1/0/1 is configured as an access port in VLAN 10 with voice VLAN 110 and PoE enabled (power inline auto), and Gi1/0/2 is an access port in VLAN 20. A trunk would tag the PC's traffic, power inline never would not power the phone, and swapping the VLANs would put the PC in the voice VLAN.

Exam trap

Watch out for the difference between access and trunk ports when a voice VLAN is involved. The voice VLAN is configured on an access port, not a trunk. Also, ensure PoE is enabled (auto) and not disabled (never).

Finally, do not confuse the access VLAN with the voice VLAN.

Why the other options are wrong

B

Incorrect: the phone and PC port must be an access port with a voice VLAN; a trunk would tag the PC's data traffic.

C

Incorrect: power inline never disables PoE, so the IP phone would not be powered.

D

Incorrect: the data and voice VLANs are swapped; the PC would be placed in the voice VLAN.

38
MCQhard

A network technician notices CDP native VLAN mismatch warnings between switches SW1 and SW2 on their trunk link. The technician runs 'show interfaces trunk' on SW1 and sees native VLAN 1, then on SW2 and sees native VLAN 99. Data traffic is currently passing, but the mismatch can cause broadcast loops. What should the technician do next?

A.Add VLAN 99 to the allowed VLAN list on the trunk interface of SW1.
B.Remove the trunk configuration and set both interfaces as access ports in VLAN 1.
C.Enable spanning‑tree PortFast on the trunk ports.
D.Configure the native VLAN to match on both ends of the trunk.
AnswerD

The root cause is a configured native VLAN mismatch (1 vs 99). Changing one switch’s native VLAN to match the other (or setting both to a common VLAN) immediately resolves the CDP warning and eliminates the potential for broadcast loops caused by the mismatch. This is the most direct and least disruptive next step.

Why this answer

The correct action is to configure the native VLAN to match on both ends of the trunk. CDP reports a native VLAN mismatch when the native VLANs differ on the two sides of a trunk link. Although data traffic may still pass because 802.1Q does not tag frames on the native VLAN, the mismatch can cause broadcast loops and security risks, as frames from one native VLAN may be misinterpreted on the other side.

Setting both sides to the same native VLAN (e.g., VLAN 1 or VLAN 99) resolves the mismatch and ensures proper Layer 2 behavior.

Exam trap

Cisco often tests the misconception that data traffic passing means the configuration is fine, but the trap here is that the native VLAN mismatch can still cause serious issues like broadcast loops and security vulnerabilities, even if user data appears to work.

Why the other options are wrong

A

Common misconception: the warning message implies a VLAN is not allowed, but native VLAN mismatch means the trunk ports disagree on the native VLAN, not that a VLAN is missing from the allowed list.

B

Over‑reaction: candidates might think a trunk problem requires eliminating the trunk, but the correct approach is to correct the native VLAN parameter on the existing trunk.

C

Wrong feature: PortFast addresses access port convergence, not VLAN mismatches. Candidates may reach for any familiar command, but it targets the wrong layer and port type.

39
Multi-Selectmedium

A network administrator is configuring a Cisco switch port to support a new voice VLAN. The port has already been assigned to data VLAN 10. The design requires that an IP phone and a PC share the same switch port, with voice traffic tagged in VLAN 50 and the PC's data traffic untagged. Which two commands are required on the switch port to complete this configuration? (Choose two.)

Select 2 answers
A.switchport voice vlan 50
B.switchport mode trunk
C.switchport trunk native vlan 10
D.switchport trunk encapsulation dot1q
E.switchport mode access
AnswersA, E

The switchport voice vlan 50 command configures the port to use VLAN 50 for voice traffic. The switch will send CDP or LLDP-MED messages to the IP phone, instructing it to tag voice frames with VLAN 50. This allows the phone to separate voice and data traffic, with voice frames tagged and data frames untagged, meeting the design requirement.

Why this answer

With the data VLAN already assigned, the port must be an access port (switchport mode access) so the PC traffic stays untagged, and it needs the voice VLAN (switchport voice vlan 50) so the switch tells the phone through CDP/LLDP-MED to tag voice frames with VLAN 50. A trunk is not needed, and a native VLAN or trunk encapsulation command does not apply to an access port.

Exam trap

The trap here is thinking the port must be a trunk to carry both voice and data, when in fact a voice VLAN configuration uses access mode with a special voice VLAN designation.

Why the other options are wrong

C

Native VLAN is a trunk setting and does not configure a voice VLAN.

40
MCQhard

A trunk link between two switches is operational, but one side shows a native VLAN mismatch warning. What is the main concern with that condition?

A.Untagged traffic may be associated with different VLANs on each end of the trunk
B.All tagged VLAN traffic is automatically converted to routed traffic
C.The mismatch forces OSPF adjacency reset on all routers
D.The trunk can carry only one VLAN until the mismatch is cleared
AnswerA

On an IEEE 802.1Q trunk, the native VLAN is the only VLAN whose frames are sent untagged. If the two switches have different native VLANs configured, untagged frames arriving on the trunk are placed into the receiving switch's configured native VLAN, which may be a different VLAN than the one used by the sending switch. This causes the untagged traffic to be silently associated with the wrong VLAN, breaking Layer 2 segmentation and potentially creating a security or bridging loop, while tagged VLAN traffic still works normally.

Why this answer

A native VLAN mismatch can cause untagged traffic to be interpreted as belonging to different VLANs on each end of the trunk. In plain language, the two switches disagree about where untagged frames belong. That can lead to confusing traffic behavior, reachability problems for certain flows, and operational warnings. It is not always a total outage, but it is a design inconsistency that should be corrected.

This matters because trunks carry multiple VLANs, and the native VLAN defines how untagged traffic is handled. If both ends do not agree, the logical treatment of those frames becomes inconsistent. The correct answer is the one that focuses on misclassification of untagged traffic, not on unrelated routing behavior.

Exam trap

Be careful not to confuse native VLAN mismatches with general trunk failures or issues affecting tagged traffic.

Why the other options are wrong

B

A native VLAN mismatch does not convert tagged traffic into routed traffic. Tagged frames continue to be switched based on their VLAN tags, and the trunk remains a Layer 2 link. The mismatch only affects untagged frames on the native VLAN.

C

A native VLAN mismatch is a Layer 2 trunking issue and does not directly affect OSPF or any routing protocol. OSPF adjacency is a Layer 3 process and would only be impacted if the mismatch caused connectivity loss for the router interfaces, but the mismatch itself does not force OSPF adjacency resets.

D

A native VLAN mismatch does not prevent the trunk from carrying other tagged VLANs. Tagged frames for other VLANs are still forwarded correctly because they are not affected by the native VLAN configuration. The trunk can carry multiple VLANs, but the native VLAN traffic is misdirected.

41
Multi-Selectmedium

Which four of the following are characteristics of Dynamic Trunking Protocol (DTP) and VLAN Trunking Protocol (VTP) used in Cisco switching? (Choose four.)

Select 4 answers
.DTP is a Cisco proprietary protocol used to negotiate trunking between two switches.
.VTP allows synchronization of VLAN information across switches in the same VTP domain.
.A switch configured with 'switchport mode dynamic desirable' actively attempts to form a trunk using DTP.
.VTP pruning helps reduce unnecessary broadcast traffic by limiting flooded traffic to only switches that need the VLAN.
.VTP transparent mode stores and forwards VTP advertisements but also modifies the VLAN database based on received updates.
.DTP can form a trunk regardless of whether both ends are configured with 'switchport nonegotiate'.

Why this answer

The four correct statements are: (1) DTP is a Cisco proprietary protocol for negotiating trunk links; (2) VTP synchronizes VLAN information across switches in the same VTP domain; (3) 'switchport mode dynamic desirable' actively sends DTP frames to form a trunk; (4) VTP pruning reduces unnecessary broadcast traffic by limiting flooded traffic to only switches that need the VLAN. The two incorrect statements: VTP transparent mode forwards VTP advertisements but does **not** modify its VLAN database based on received updates—it only passes them through. DTP **cannot** form a trunk when both ends are configured with 'switchport nonegotiate' because that command disables DTP frame transmission entirely, preventing trunk negotiation.

Exam trap

Cisco often tests the distinction between DTP modes (dynamic desirable vs. dynamic auto) and the fact that VTP can cause catastrophic VLAN propagation errors if revision numbers are not reset before adding a switch to a production network.

42
MCQhard

A switch displays the following output: Switch# show interfaces trunk Port Mode Encapsulation Status Native vlan Gi1/0/24 on 802.1q trunking 99 Port Vlans allowed on trunk Gi1/0/24 10,20,30 Port Vlans active in management domain Gi1/0/24 10,20,30,40 Users in VLAN 40 cannot reach resources across this trunk. What is the most likely reason?

A.VLAN 40 is active, so spanning tree must be blocking it
B.VLAN 40 is not in the native VLAN, so it cannot cross the trunk
C.VLAN 40 is not permitted on the trunk
D.802.1Q trunks can carry only three VLANs at a time
AnswerC

Correct. This is correct. The allowed VLAN list controls which VLANs are transported across the trunk. Because VLAN 40 is absent from that list, users in VLAN 40 cannot use that trunk to reach resources on the far side.

Why this answer

The trunk is not carrying VLAN 40 because VLAN 40 is missing from the allowed VLAN list (only 10, 20, 30 are allowed). Option A is incorrect because spanning tree does not block VLANs by default without evidence of a loop; the output shows no STP blocking. Option B is incorrect because native VLAN only affects tagging, not whether a VLAN can traverse a trunk; all VLANs can cross a trunk if permitted.

Option D is incorrect because 802.1Q can carry up to 4094 VLANs, not just three. The key distinction is that a VLAN may be active on the switch but still fail to cross a specific trunk if it is not in the allowed list.

Exam trap

Ensure you differentiate between VLANs configured on the switch and those allowed on the trunk. Just because a VLAN is active doesn't mean it's allowed on a trunk.

Why the other options are wrong

A

Spanning Tree Protocol (STP) can block a VLAN if there is a loop, but the output shows VLAN 40 is active in the management domain and not listed as blocked. The explicit absence of VLAN 40 from the allowed VLAN list is the direct cause, not STP.

B

The native VLAN is only for untagged traffic on an 802.1Q trunk. All other VLANs are tagged and can cross the trunk regardless of the native VLAN. VLAN 40 is not the native VLAN, but that does not prevent it from being carried if permitted.

D

802.1Q has no limit of three VLANs per trunk; it can support up to 4094 VLANs. The output shows only three VLANs allowed because of configuration, not a protocol limitation.

43
MCQhard

A network administrator has configured a DHCP server at 192.168.100.10/24 on VLAN 100, behind a router. Clients on VLAN 200 (192.168.200.0/24) cannot obtain an IP address. The router's VLAN 200 gateway interface has an ip helper-address pointing to the server, and the router can ping the server. The router connects to the access switch on GigabitEthernet0/1, and DHCP snooping is enabled on VLAN 200 of that switch. Based on the exhibit, what is the most likely cause?

A.The relay address is incorrect because it does not point at the DHCP server.
B.DHCP snooping is dropping the relayed server replies because the switch port toward the router is untrusted.
C.The DHCP server is unreachable from the router.
D.The ip helper-address command is missing from the VLAN 200 interface.
AnswerB

GigabitEthernet0/1, the port toward the router, is shown as untrusted and the snooping statistics show packets dropped from untrusted ports. Configure 'ip dhcp snooping trust' on that port.

Why this answer

DHCP snooping drops server-type messages (DHCPOFFER, DHCPACK) that arrive on untrusted ports. The DHCP replies are relayed by the router and enter the switch on GigabitEthernet0/1, which the exhibit shows as untrusted (Trusted: no), and the statistics show the dropped packets increasing. The fix is 'ip dhcp snooping trust' on GigabitEthernet0/1, the port toward the router and the DHCP server.

Exam trap

A correct relay configuration does not guarantee DHCP works: DHCP snooping discards server replies that arrive on an untrusted port, and the uplink toward the router or server must be trusted.

Why the other options are wrong

A

The exhibit shows the helper address matches the server IP.

C

The server is reachable; the failure is on the switch.

D

The helper address is configured; the problem is snooping trust.

44
MCQhard

A multilayer switch has SVIs for VLAN 10 and VLAN 20, but hosts in those VLANs still cannot reach each other. The SVIs are up/up. Which additional condition is most likely required?

A.IP routing must be enabled on the multilayer switch
B.Every access port must be converted to a trunk
C.DHCP snooping must be disabled globally
D.The switch must remove all VLAN assignments
AnswerA

IP routing must be enabled globally on the multilayer switch (via the 'ip routing' command) so it can forward packets between the Layer 3 SVIs for VLAN 10 and VLAN 20. Without this, the switch operates only at Layer 2 and will not perform a routing lookup, so frames arriving in one VLAN cannot be forwarded out the other VLAN's SVI. Each SVI must also be up/up and assigned an IP address in a distinct subnet for the routing table to have valid directly connected routes.

Why this answer

If the SVIs are up but inter-VLAN traffic still fails, the most likely missing condition is that IP routing is not enabled on the multilayer switch. In plain language, the switch has the VLAN gateway interfaces present, but it has not been told to behave as a Layer 3 router between them. Without IP routing enabled, the SVIs can exist and still not actually route traffic between VLANs.

This is a classic multilayer-switch design issue because many learners assume the presence of SVIs alone automatically creates routing. In reality, routed forwarding between VLANs still requires the switch to operate as a Layer 3 device. That is why enabling routing is the best answer.

Exam trap

Don't assume SVIs automatically enable routing; IP routing must be explicitly configured.

Why the other options are wrong

B

Converting all access ports to trunk ports is unnecessary and incorrect for inter-VLAN routing. Access ports belong to a single VLAN, and hosts connect via access ports. Trunk ports are used to carry multiple VLANs between switches, not to connect end hosts.

Changing all ports to trunks would break connectivity for hosts.

C

DHCP snooping is a security feature that filters DHCP messages and does not affect Layer 3 routing between VLANs. Disabling it would not enable inter-VLAN communication. The issue is routing, not DHCP.

D

Removing all VLAN assignments would break the network entirely, as hosts would lose their VLAN membership and connectivity. VLANs are essential for segmenting the network; removing them would not solve the routing issue.

45
MCQhard

A switch port should allow an IP phone and attached PC to operate correctly. The phone should place voice traffic in VLAN 200 while the PC remains in VLAN 20. Which configuration approach best supports that design?

A.Configure the port with an access VLAN for data and a voice VLAN for the phone
B.Configure the port as a routed port with no switchport
C.Configure the port as an EtherChannel member
D.Use a native VLAN only and disable all tagging
AnswerA

Cisco IP phones contain a small 3-port switch that places PC traffic on the configured access VLAN while the phone itself uses a distinct voice VLAN advertised via CDP. This design keeps data and voice in separate Layer 2 broadcast domains, allows separate QoS policies and subnets, and works over a single physical cable without a trunk to the desktop. The access VLAN carries untagged PC frames, while the voice VLAN uses 802.1Q tagging on the phone uplink, making coexistence correct.

Why this answer

The best approach is to configure the access VLAN for user data and the voice VLAN separately. In plain language, the PC should remain a normal untagged data endpoint in VLAN 20, while the phone can tag its own voice traffic for VLAN 200. Cisco access-port designs support this exact use case and allow the switch to keep voice and user traffic logically separated without requiring two physical ports.

This is a classic CCNA edge-port design. It is not a general trunking problem, and it does not require EtherChannel or router subinterfaces. The important idea is that one switchport can support an access VLAN and a voice VLAN together in a way designed specifically for IP phones with downstream PCs.

Exam trap

Avoid assuming trunk mode is needed for VLANs; understand access vs. voice VLANs for edge ports.

Why the other options are wrong

B

A routed port (no switchport) is used for Layer 3 routing between switches or routers, not for connecting end devices like IP phones and PCs. It does not support VLAN assignment or the coexistence of multiple VLANs on a single port, making it unsuitable for this scenario.

C

EtherChannel is used to aggregate multiple physical links into a single logical link for increased bandwidth and redundancy. It does not provide any mechanism to separate voice and data traffic into different VLANs on a single port, and it is not relevant to the requirement of connecting an IP phone and PC.

D

Using a native VLAN only and disabling all tagging would place all traffic (voice and data) in the same VLAN, which contradicts the requirement to separate voice into VLAN 200 and data into VLAN 20. The native VLAN is used for untagged traffic on a trunk, but this design requires distinct VLANs with tagging for voice.

46
PBQmedium

You are connected to SW1 via the console. SW1 is a Layer 2 switch. Port GigabitEthernet0/1 connects to a PC in VLAN 10, and port GigabitEthernet0/2 connects to a server in VLAN 20. Both ports are currently in VLAN 1. Configure SW1 to assign GigabitEthernet0/1 to VLAN 10 and GigabitEthernet0/2 to VLAN 20, and verify the configuration.

Network Topology
G0/1G0/2SW1PCServer

Hints

  • •Use switchport mode access to configure the port as an access port.
  • •Use switchport access vlan to assign the VLAN.
A.interface GigabitEthernet0/1: switchport mode access, switchport access vlan 10. interface GigabitEthernet0/2: switchport mode access, switchport access vlan 20. Verify with show vlan brief.
B.interface GigabitEthernet0/1: switchport mode access, switchport access vlan 20. interface GigabitEthernet0/2: switchport mode access, switchport access vlan 10.
C.interface GigabitEthernet0/1: switchport mode access, switchport access vlan 10 only; GigabitEthernet0/2 is left unchanged.
D.interface GigabitEthernet0/1 and GigabitEthernet0/2: switchport mode trunk, switchport trunk allowed vlan 10,20.
AnswerA
solution
! SW1
interface GigabitEthernet0/1
switchport mode access
switchport access vlan 10
interface GigabitEthernet0/2
switchport mode access
switchport access vlan 20

Why this answer

The correct configuration sets each access port to access mode and assigns the appropriate VLAN (10 for Gi0/1, 20 for Gi0/2), then verifies with 'show vlan brief'. Access mode is required because each port connects to a single end device (PC or server) in one VLAN. 'show vlan brief' displays VLAN-to-port assignments, confirming the change.

Exam trap

The trap is choosing trunk mode because it 'allows VLANs', or omitting 'switchport mode access' assuming it is default; 200-301 tests whether you know access ports serve single-VLAN end devices and that explicit mode configuration is expected.

Why the other options are wrong

B

Incorrect: the VLANs are swapped, putting the PC in VLAN 20 and the server in VLAN 10.

C

Incorrect: GigabitEthernet0/2 stays in VLAN 1 instead of VLAN 20.

D

Incorrect: the ports connect to single end devices, so they must be access ports, not trunks.

47
MCQhard

A network engineer notices that users in VLAN 10 report intermittent connectivity and slow file transfers to a server on the same switch. The engineer issues the show interfaces fa0/1 command on the switch port connected to the server and observes a high number of runts, input errors, and CRC errors, while output errors are minimal. The interface configuration shows speed 100 and duplex full.

A.The server NIC is set to 10 Mbps half-duplex, causing a speed mismatch.
B.The server NIC is auto-negotiating to 100 Mbps half-duplex, resulting in a duplex mismatch.
C.The cable connecting the server to the switch is faulty, introducing excessive noise.
D.The switch port is configured with an incorrect native VLAN, causing duplex negotiation issues.
AnswerB

Hard-coding the switch port to 100 Mbps full duplex usually disables auto-negotiation on it. The server's NIC, still auto-negotiating, detects the speed but cannot learn the duplex, so it falls back to half duplex. The half-duplex side backs off and abandons frames when it sees traffic, and the full-duplex switch receives those cut-off frames as runts and CRC errors. Set both sides to auto, or hard-code both identically.

Why this answer

The symptoms—high runts, input errors, and CRC errors with minimal output errors—are classic indicators of a duplex mismatch. When the switch port is hardcoded to 100 Mbps full-duplex and the server NIC auto-negotiates to 100 Mbps half-duplex (a common fallback when one side is manually set), the half-duplex side experiences collisions while the full-duplex side does not sense the collision. These collisions cause the half-duplex side to truncate frames, resulting in runts and CRC errors on the full-duplex switch port.

The speed matches (both 100 Mbps), so the issue is purely duplex-related.

Exam trap

Cisco often tests the misconception that speed and duplex mismatches always occur together; the trap here is that a duplex mismatch can exist even when speed matches, and the error pattern (high input errors, low output errors) specifically points to duplex, not cabling or VLAN issues.

Why the other options are wrong

A

Misconception that speed mismatch produces specific error counters; in reality, incompatible speeds cause link failure, not runts and CRC errors.

C

Misconception that CRC errors alone point to a bad cable; duplex mismatch is one of the most common causes of runts and CRC errors on forced-full interfaces.

D

Misconception that a VLAN mismatch can trigger interface errors; these errors are purely physical/data-link layer phenomena unrelated to VLAN settings.

48
PBQmedium

You are connected to R1 via the console. R1 is a router that needs to provide DHCP services for hosts on VLAN 10 (192.168.10.0/24) and VLAN 20 (192.168.20.0/24). The DHCP server is located on VLAN 10 at 192.168.10.100, but hosts on VLAN 20 cannot reach it directly. Configure R1 to forward DHCP broadcasts from VLAN 20 to the DHCP server.

Network Topology
G0/0.10192.168.10.1/24G0/0.20192.168.20.1/24DHCP ServerVLAN 10R1VLAN 20Hosts

Hints

  • •The helper address should be placed on the interface that receives the DHCP broadcast.
  • •The helper address is the server's IP address.
  • •Only one command is needed.
A.interface GigabitEthernet0/0.20; ip helper-address 192.168.10.100
B.interface GigabitEthernet0/0.10; ip helper-address 192.168.10.100
C.interface GigabitEthernet0/0.20; ip helper-address 192.168.20.1
D.interface GigabitEthernet0/0.20; ip dhcp relay information trusted
AnswerA
solution
! R1
interface GigabitEthernet0/0.20
ip helper-address 192.168.10.100

Why this answer

The ip helper-address command enables the router to forward UDP broadcasts (including DHCP) to a specific server. Placing it on the VLAN 20 subinterface ensures that DHCP requests from VLAN 20 are unicast to the server on VLAN 10.

Exam trap

The key trap is placing the ip helper-address on the wrong interface. Remember: the helper-address must be on the interface that receives the client's broadcast, not on the server's interface. Also, do not confuse ip helper-address with DHCP server configuration or relay option commands.

Why the other options are wrong

B

Incorrect: the DHCP broadcasts arrive on the VLAN 20 subinterface, not on the VLAN 10 subinterface.

C

Incorrect: 192.168.20.1 is R1's own VLAN 20 address, not the DHCP server.

D

Incorrect: that command only affects option 82 handling and does not forward DHCP broadcasts to the server.

49
Drag & Dropmedium

Drag and drop the following steps into the correct order to configure SW1 in this sequence: Rapid PVST+ mode, root bridge for VLAN 1, PortFast on the access ports, and BPDU Guard on PortFast ports.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4
5Step 5

Why this order

Enter global configuration mode, set the spanning-tree mode to rapid-pvst, make SW1 the root bridge for VLAN 1 with spanning-tree vlan 1 root primary, enable PortFast on the access ports, and enable BPDU Guard on PortFast ports with spanning-tree portfast bpduguard default.

50
PBQhard

You are connected to SW1. Configure a Layer 2 LACP EtherChannel trunk between SW1 and SW2 using GigabitEthernet0/1 and GigabitEthernet0/2 that carries VLAN 10. The channel is not coming up. Inspect the exhibit and fix the problems on SW1.

Network Topology
Gi0/1Gi0/1LACPSW1SW2

Hints

  • •Check the speed and duplex on both member interfaces.
  • •Verify that the port-channel interface and the member ports are both Layer 2.
  • •Both members are passive; at least one end of an LACP bundle must be active.
A.Port-channel1: no ip address, switchport, switchport mode trunk, switchport trunk allowed vlan 10. Gi0/2: speed 1000, duplex full. Gi0/1 and Gi0/2: channel-group 1 mode active.
B.Change only the LACP mode on Gi0/1 and Gi0/2 to active.
C.Correct only the speed and duplex on Gi0/2 to 1000 and full.
D.Configure no switchport on Gi0/1 and Gi0/2 to match the routed Port-channel1 and change the mode to active.
AnswerA
solution
! SW1
configure terminal
interface Port-channel1
no ip address
switchport
switchport mode trunk
switchport trunk allowed vlan 10
exit
interface GigabitEthernet0/2
speed 1000
duplex full
channel-group 1 mode active
exit
interface GigabitEthernet0/1
channel-group 1 mode active
end

Why this answer

Three problems prevent the bundle: the members use different speed and duplex (Gi0/1 is 1000/full while Gi0/2 is 100/half), Port-channel1 is a routed port (no switchport, with an IP address) while the members are Layer 2 trunks, and both members use LACP passive so that, unless the peer is active, no LACP negotiation starts. Fix Gi0/2 to speed 1000 and duplex full, remove the IP address and make Port-channel1 a Layer 2 trunk for VLAN 10, and set mode active on both members.

Exam trap

Watch for mismatches in speed, duplex, and Layer2/Layer3 configuration between member ports and the port-channel interface. Also, ensure LACP mode is active on at least one side to initiate negotiation.

Why the other options are wrong

B

Incorrect: the speed and duplex mismatch and the Layer 3 port-channel still prevent a bundle.

C

Incorrect: the Layer 3 port-channel and passive LACP mode on both members remain.

D

Incorrect: this creates a Layer 3 channel, but the requirement is a Layer 2 trunk carrying VLAN 10, and the speed/duplex mismatch remains.

51
MCQhard

Refer to the exhibit. A network administrator is troubleshooting a connectivity issue on switch SW1. Users connected to port Gi0/3 are unable to reach resources in VLAN 30. The administrator issues the show vlan brief command and receives the output shown. What is the most likely cause of the problem?

A.The Gi0/3 port is in an error-disabled state due to port security violations.
B.The VLAN 30 SVI is administratively down.
C.VLAN 30 is administratively shut down.
D.Spanning Tree Protocol has placed Gi0/3 into a blocking state for VLAN 30.
AnswerC

The Status column for VLAN 30 reads 'act/lshut', which is Cisco's shorthand for 'active but locally shut down'—meaning the VLAN has been administratively disabled via the 'shutdown' command in VLAN configuration mode. An administratively shut down VLAN will not pass traffic for any access port assigned to it, regardless of the physical or operational state of those ports. This is a VLAN database condition, distinct from an SVI being down or an interface errdisable, and it applies to the entire broadcast domain.

Why this answer

The 'show vlan brief' output shows VLAN 30 with a status of 'act/lshut' (administratively shutdown) or 'shutdown', indicating that the VLAN has been disabled via the 'shutdown' command in VLAN configuration mode. A shutdown VLAN does not forward traffic, and all access ports assigned to it become operationally inactive for that VLAN, even though the ports themselves may still be listed in the output. The SVI for VLAN 30 would also be down.

Therefore, the most likely cause is that VLAN 30 has been administratively shut down.

Exam trap

Common mistake: Candidates think that a shutdown VLAN disappears from 'show vlan brief'. In fact, it remains listed with a status such as 'act/lshut'. A VLAN that is missing entirely means it has been deleted, not merely shutdown.

Why the other options are wrong

A

Candidates often confuse port-level issues with VLAN-level states. Port security violations would result in an err-disable status, which is not reflected in the VLAN status column; the VLAN would still show 'active' if it were enabled.

B

Candidates may mistake the VLAN shutdown for an SVI shutdown because both involve the 'shutdown' keyword. However, the SVI state would appear in 'show ip interface brief' or 'show interface vlan 30', not here.

D

Candidates often attribute connectivity loss to STP blocking, which is a common cause of forwarding issues. However, this exhibit’s specific clue is the 'act/lshut' flag, directing attention to the VLAN administrative state.

52
Multi-Selectmedium

Which TWO statements accurately describe 802.1Q trunking and inter-VLAN routing on Cisco switches?

Select 2 answers
A.The native VLAN on a trunk port sends frames with an 802.1Q tag containing VLAN ID 1.
B.802.1Q trunking adds a 4-byte tag that includes a 12-bit VLAN ID field, increasing the maximum frame size.
C.A router-on-a-stick configuration uses subinterfaces, each mapped to a VLAN with 802.1Q encapsulation and an IP address in a unique subnet.
D.A trunk port can only forward traffic for one VLAN at a time.
E.The native VLAN on a trunk cannot be changed from VLAN 1.
AnswersB, C

802.1Q trunking inserts a 4-byte tag field between the source MAC address and the EtherType/length field. This tag comprises a 16-bit TPID (0x8100) and a 16-bit TCI, which contains a 3-bit priority, a 1-bit Drop Eligible Indicator (DEI), and a 12-bit VLAN ID supporting up to 4094 usable VLANs. Adding this 4-byte field increases the maximum Ethernet frame size from 1518 to 1522 bytes for tagged frames.

Why this answer

Option B is correct because 802.1Q inserts a 4-byte tag into the Ethernet frame, and that tag contains a 12-bit VLAN Identifier (VID) field supporting VLAN IDs 1-4094, which increases the frame size beyond the standard 1518 bytes (up to 1522 bytes). Option C is correct because router-on-a-stick uses one physical router interface divided into logical subinterfaces, and each subinterface is configured with encapsulation dot1q <vlan-id> plus an IP address in a distinct subnet to route between VLANs. Option A is incorrect because the native VLAN is the one VLAN whose frames are sent untagged on an 802.1Q trunk, not tagged with VLAN ID 1.

Option D is incorrect because a trunk port carries traffic for multiple VLANs simultaneously, tagging frames to keep them separated. Option E is incorrect because the native VLAN is configurable per trunk port with the switchport trunk native vlan command and is not locked to VLAN 1.

Exam trap

Cisco often tests the misconception that the native VLAN is always VLAN 1 and that it is tagged, when in fact the native VLAN is untagged and can be changed to any VLAN number.

Why the other options are wrong

A

By default, frames belonging to the native VLAN (VLAN 1) traverse a trunk link without an 802.1Q tag.

D

Trunk ports differentiate frames from multiple VLANs using VLAN tags, permitting concurrent forwarding for all allowed VLANs.

E

Cisco switches allow administrators to assign any active VLAN as the native VLAN for a trunk port.

53
MCQhard

Refer to the exhibit. A network engineer examines SW3 and notices that the GigabitEthernet0/0 uplink is up but is not forwarding traffic for VLAN 10. The engineer issues the show spanning-tree vlan 10 command and receives the output shown. Based on the output, what is the most likely explanation?

A.GigabitEthernet0/0 is administratively down, which prevents the host from communicating.
B.The port is in the Blocking state because the switch detected a loop and moved the port to error-disabled state.
C.The port is blocked because SW3 has a lower bridge priority than the root bridge and should be the designated port for that segment.
D.The interface GigabitEthernet0/0 is in the Blocking state because it received a superior BPDU, making it an alternate port to the root bridge.
AnswerD

The output shows Gi0/0 with role Altn and state BLK. An alternate port is blocked because it receives a superior BPDU from another bridge on its segment, providing a backup path to the root while Gi0/1 is the root port. This is normal STP behavior and explains why the uplink does not forward.

Why this answer

The output shows Gi0/0 with role Altn and state BLK. SW3's root port is Gi0/1 (cost 4), and Gi0/0 offers an equal-cost second path to the root, so it is an alternate port. An alternate port is blocking because it receives a superior BPDU on that segment from another bridge, which keeps the topology loop-free.

This is normal STP operation, not an error or an administrative shutdown.

Exam trap

Cisco often tests the distinction between a port being blocked due to normal STP operation (receiving a superior BPDU) versus being error-disabled or administratively down, leading candidates to incorrectly assume a physical or administrative issue.

Why the other options are wrong

A

Candidates may incorrectly associate the blocked state with an administratively disabled interface.

B

Candidates often confuse error-disabled state (caused by features like BPDU guard) with the standard STP blocking state.

C

Candidates may misunderstand the root election process and assume a lower priority switch always becomes designated for all segments, ignoring the Altn role.

54
PBQhard

You are connected to SW1. An LACP EtherChannel (channel-group 1, mode active on both switches) between SW1 and SW2 must use GigabitEthernet0/1 and GigabitEthernet0/2 as an access port channel in VLAN 100. Only Gi0/1 is bundled; Gi0/2 is suspended because of a speed mismatch. Correct SW1 and verify the EtherChannel with show etherchannel summary.

Hints

  • •Read the %EC-5-CANNOT_BUNDLE2 message; it names the differing attribute.
  • •LACP requires identical speed and duplex on all member ports.
  • •Change the member that does not match the working one.
A.On Gi0/2 enter speed 1000 (duplex full already matches), then shutdown and no shutdown.
B.On Gi0/1 enter speed 100.
C.On Port-channel1 enter switchport mode trunk.
D.On Gi0/2 enter channel-group 1 mode passive.
AnswerA
solution
! SW1
configure terminal
interface GigabitEthernet0/2
speed 1000
shutdown
no shutdown
end

Why this answer

The log message states that Gi0/2 is suspended because its speed is 100M while Gi0/1 is 1000M. LACP members must have the same speed and duplex. Setting speed 1000 on Gi0/2 (duplex full already matches) and bouncing the port with shutdown and no shutdown lets it join the bundle, after which both ports show P.

The port-channel is already an access port in VLAN 100, matching the members.

Exam trap

Do not confuse LACP modes (active/passive) with PAgP modes (desirable/auto). Also, remember that physical parameters like speed and duplex must match across all member ports; logical configurations like VLAN or trunking are separate but must also be consistent. Always verify the root cause before changing unrelated settings.

Why the other options are wrong

B

Incorrect: this lowers the working link to the wrong speed instead of correcting Gi0/2 and wastes bandwidth.

C

Incorrect: the port-channel mode is consistent with the members; the log points to speed.

D

Incorrect: the LACP mode is not the cause, and the speed mismatch would still suspend the port.

55
Multi-Selectmedium

Which three of the following are correct statements about VLAN configuration and verification on a Cisco switch? (Choose three.)

Select 3 answers
.The 'switchport mode access' command places the interface into a non-trunking mode.
.By default, all ports on a Cisco switch are in VLAN 1.
.The 'show vlan brief' command displays VLANs that are active on the switch.
.VLANs 1002–1005 are reserved for user-created VLANs.
.A VLAN must be manually created before its name can be assigned.
.The 'switchport trunk native vlan' command restricts the native VLAN to only tagged frames.

Why this answer

The correct statements are: (1) The 'switchport mode access' command places the interface into a non-trunking mode; (2) By default, all ports on a Cisco switch are in VLAN 1; (3) The 'show vlan brief' command displays VLANs that are active on the switch. The remaining statements are false because: VLANs 1002–1005 are reserved for legacy FDDI/Token Ring VLANs, not for user-created VLANs; a VLAN does not need to be manually created before its name can be assigned (assigning a port to a new VLAN can automatically create it, after which you can set its name); and the 'switchport trunk native vlan' command does not restrict the native VLAN to only tagged frames—native VLAN traffic is sent untagged.

Exam trap

Candidates often confuse the native VLAN as carrying tagged frames, and mistakenly believe VLANs 1002–1005 are user-configurable, when in fact they are reserved for legacy technologies.

Why the other options are wrong

D

VLANs 1002–1005 are reserved for legacy FDDI and Token Ring, not user-created VLANs.

F

The native VLAN on a trunk sends frames untagged; this command sets the native VLAN, not a tagging restriction.

56
PBQmedium

You are connected to SW1 (a Catalyst 3560 that supports both ISL and 802.1Q) via the console. Ports G0/1 and G0/2 connect two PCs that must be in VLAN 10 (Sales), which does not exist yet; the ports are currently in VLAN 1. Port G0/3 is a trunk to another switch. Configure the switch so G0/1 and G0/2 are access ports in VLAN 10 and G0/3 is an 802.1Q trunk with native VLAN 99.

Network Topology
trunkPC1SW1 G0/1SW1 G0/2OtherSwitch

Hints

  • •Check the current VLAN assignment on access ports.
  • •The trunk encapsulation must be set to dot1q for 802.1Q support.
  • •Native VLAN should match on both ends of the trunk.
A.Create VLAN 10, assign G0/1 and G0/2 as access ports in VLAN 10, configure G0/3 as trunk with encapsulation dot1q and native VLAN 99.
B.Create VLAN 10, assign G0/1 and G0/2 as access ports in VLAN 10, configure G0/3 as trunk with encapsulation isl and native VLAN 99.
C.Create VLAN 10, assign G0/1 and G0/2 as trunk ports in VLAN 10, configure G0/3 as trunk with encapsulation dot1q and native VLAN 99.
D.Create VLAN 10, assign G0/1 and G0/2 as access ports in VLAN 10, configure G0/3 as trunk with encapsulation dot1q and native VLAN 1.
AnswerA
solution
! SW1
vlan 10
name Sales
interface GigabitEthernet0/1
switchport mode access
switchport access vlan 10
interface GigabitEthernet0/2
switchport mode access
switchport access vlan 10
interface GigabitEthernet0/3
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk native vlan 99

Why this answer

Option A is correct. VLAN 10 must first be created (vlan 10 / name Sales), G0/1 and G0/2 become access ports with switchport access vlan 10, and G0/3 is an 802.1Q trunk (switchport trunk encapsulation dot1q, switchport mode trunk) with switchport trunk native vlan 99. The native VLAN should be configured identically on both ends of the trunk, otherwise CDP/STP report a native VLAN mismatch and untagged traffic leaks between VLANs.

Exam trap

The trap is selecting ISL encapsulation (deprecated) or forgetting to set the native VLAN correctly. Candidates may also confuse access and trunk port configurations, especially when the question asks for both.

Why the other options are wrong

B

ISL is not 802.1Q, and a native VLAN is an 802.1Q concept; the stem requires 802.1Q with native VLAN 99.

C

The specific factual error is that ports connected to end devices (PCs) should be access ports, not trunk ports. Trunk ports are used for inter-switch links.

D

The native VLAN must be set to 99, not left at the default 1.

57
MCQhard

A technician is troubleshooting a network issue where hosts in VLAN 20 on SW1 cannot communicate with hosts in VLAN 20 on SW2. Both switches are connected by an Ethernet trunk link that is up/up and configured as a trunk. The VLAN databases on both switches include VLAN 20, and the spanning tree for VLAN 20 is in a forwarding state on all ports. Hosts within VLAN 20 on each switch can communicate with each other locally. What is the most likely cause?

A.The native VLAN is mismatched on the two ends of the trunk.
B.VLAN 20 has not been created in the VLAN database on SW2.
C.The trunk encapsulation is mismatched between SW1 and SW2.
D.VLAN 20 is not in the switchport trunk allowed VLAN list on the trunk port between SW1 and SW2.
AnswerD

When a trunk port’s allowed VLAN list explicitly excludes a VLAN, the switch drops all frames tagged for that VLAN, even though the VLAN exists locally and the trunk is active. This results in the described symptom of local intra-VLAN communication working but no cross-switch communication for VLAN 20.

Why this answer

The most likely cause is that VLAN 20 is not included in the allowed VLAN list on the trunk port between SW1 and SW2. Even though the trunk is up/up and VLAN 20 exists in the VLAN database, the switchport trunk allowed vlan command restricts which VLANs can traverse the trunk. If VLAN 20 is omitted from this list, frames from VLAN 20 will be dropped at the trunk, preventing inter-switch communication for that VLAN.

Exam trap

Cisco often tests the distinction between VLAN existence in the database and VLAN permission on a trunk; candidates mistakenly think that if a VLAN is created and spanning tree is forwarding, it must work, but the trunk allowed list is an independent filter that can block traffic.

Why the other options are wrong

A

Candidates may think that a native VLAN mismatch breaks all trunk functions.

B

Candidates may assume that a missing VLAN on one switch explains inter-switch failures, ignoring that local communication would also fail.

C

Candidates might overlook that the trunk link is operational, which implies matching encapsulation.

58
MCQmedium

A network administrator is troubleshooting a switch that is receiving DHCPDISCOVER messages from a client on VLAN 20, but the DHCP server on a different subnet never sees those requests. The interface VLAN 20 has the address 10.20.0.1/24, and the DHCP server address is 10.99.0.10. Which command should be applied to enable the switch to forward these requests to the server?

A.ip dhcp pool VLAN20
B.ip forward-protocol udp 67
C.ip dhcp relay information option
D.ip helper-address 10.99.0.10
AnswerD

The ip helper-address command on the client VLAN's SVI converts broadcast DHCPDISCOVER messages into unicast packets destined for the specified server address. It also fills in the gateway address field so the server can select the correct scope for the 10.20.0.0/24 subnet, allowing the reply to be routed back to the client.

Why this answer

DHCP relay is configured with the ip helper-address command on the interface facing the clients, which unicasts their DHCP broadcasts to the specified server and sets the gateway address so the server can match the correct scope. Without it, the broadcast stays on the local subnet and the remote server never receives the request.

Exam trap

The trap here is assuming that enabling option 82 or listing UDP port 67 is enough, when only the ip helper-address statement actually forwards the client request to the server.

59
Multi-Selectmedium

A network administrator is configuring a new switch port for a server that will host multiple VLANs. The server's NIC supports 802.1Q tagging. The administrator wants to ensure that only VLANs 10, 20, and 30 can traverse the link. Which two commands must be configured on the switch port to achieve this? (Choose two.)

Select 2 answers
A.switchport mode trunk
B.switchport access vlan 10
C.switchport voice vlan 20
D.switchport trunk allowed vlan 10,20,30
E.switchport nonegotiate
AnswersA, D

This command sets the port to trunk mode, which is required for carrying multiple VLANs with 802.1Q tagging. A trunk port allows traffic from multiple VLANs to pass through a single physical link. Without trunk mode, the port would only support a single VLAN, and the server would not be able to communicate on multiple VLANs.

Why this answer

To configure a trunk port that carries only VLANs 10, 20, and 30, you must set the port to trunk mode and then specify the allowed VLANs. The switchport mode trunk command enables trunking, and the switchport trunk allowed vlan 10,20,30 command restricts the trunk to those VLANs. This ensures the server can communicate on the required VLANs while blocking others.

Exam trap

The trap here is thinking that setting an access VLAN or voice VLAN is sufficient for a trunk port, or that disabling DTP negotiation restricts VLANs.

60
MCQhard

A network technician is troubleshooting an inter-VLAN routing issue on a multilayer switch. Hosts on VLAN 10 can reach the SVI for VLAN 10 (10.0.10.1) but cannot reach hosts on VLAN 20. The technician has verified that 'ip routing' is enabled and that the 'show ip route' command displays directly connected routes for both VLANs. No static routes are configured. What should the technician do next?

A.Check the ARP table for entries on VLAN 20.
B.Issue the 'show ip routing' command again to confirm routing is enabled.
C.Configure a default route pointing to the next-hop gateway.
D.Verify the VLAN membership of the destination host on VLAN 20.
AnswerA

The Layer 3 routing table is correct; the problem is likely that the switch lacks a Layer 2 MAC address for the destination host on VLAN 20. Examining the ARP cache will confirm whether the switch can map the destination IP to a MAC address, and if not, will show that ARP resolution is failing, which explains the connectivity break.

Why this answer

The hosts on VLAN 10 can reach the SVI (10.0.10.1) but not hosts on VLAN 20, which indicates that Layer 3 routing is working (ip routing enabled, directly connected routes present). The issue is likely that the switch does not have the MAC address of the destination host in VLAN 20 in its ARP table, so it cannot forward frames to that host. Checking the ARP table for VLAN 20 entries will reveal whether the switch has resolved the Layer 3-to-Layer 2 address mapping for the destination.

Exam trap

Cisco often tests the misconception that if 'ip routing' is enabled and routes are present, inter-VLAN routing should work, but they trap candidates by omitting the critical step of ARP resolution, which is required to deliver frames to the destination host's MAC address.

Why the other options are wrong

B

This option revisits a step already completed and verified, making it redundant. Candidates might think double-checking routing is safe, but the scenario explicitly states routing is working as expected.

C

Some candidates might believe inter-VLAN communication requires a default route, but directly connected routes already provide full reachability without static routing. This action is overly drastic and misdirected.

D

Candidates often jump to VLAN misconfigurations when inter-VLAN communication fails, even when routing is confirmed. The scenario already establishes the VLAN 20 host's location; the next logical layer to inspect is ARP resolution.

61
MCQhard

Refer to the exhibit. A network administrator is troubleshooting connectivity to devices in VLAN 10 on a Layer 3 switch. The administrator issues the show ip interface brief command on SW1 and sees the output displayed. What is the most likely reason that the VLAN 10 SVI is not functioning?

A.No active ports are assigned to VLAN 10.
B.The VLAN 10 SVI has been administratively shut down.
C.The IP address configured on the VLAN 10 SVI is incorrect for the subnet.
D.The switch ports assigned to VLAN 10 are all configured as trunk ports.
AnswerA

The SVI for VLAN 10 will not transition to up/up until at least one switch port is in the up/up state and actively assigned to VLAN 10 (either as an access port in that VLAN or as a trunk port that has VLAN 10 allowed and active). With no active member ports, the switch considers the VLAN to have no operational Layer 2 presence, so the SVI's line protocol remains down even though the VLAN exists and is configured with an IP address. This is a standard Cisco IOS behavior: the SVI's status mirrors the presence of an active port in the associated VLAN, not merely the VLAN's existence.

Why this answer

The VLAN 10 SVI will remain in a down/down state if there are no active ports assigned to VLAN 10, because a Layer 3 switch requires at least one active Layer 2 interface in the VLAN to bring the SVI up. This is a fundamental behavior of Cisco switches: the SVI is operationally down until the VLAN has at least one active port in a non-blocking state. The show ip interface brief output would show the VLAN10 interface as 'down/down' rather than 'administratively down' or 'up/up'.

Exam trap

Cisco often tests the subtle distinction between an SVI being 'down/down' due to no active ports in the VLAN versus 'administratively down' due to a shutdown command, and candidates may incorrectly assume a misconfigured IP address or trunk port issue is the cause.

Why the other options are wrong

B

Candidates often confuse 'down' with 'administratively down', assuming any disabled interface will show 'down'. They need to distinguish the two statuses.

C

Some candidates think a misconfigured IP address can cause an interface to be down, but status does not reflect IP configuration.

D

A common misunderstanding is that trunk ports do not make a VLAN active; in reality, a trunk carrying VLAN 10 can activate the SVI as long as the trunk is up/up and the VLAN is not pruned.

62
MCQmedium

A switch interface connected to another switch must carry VLANs 10, 20, and 30 only. Which command best enforces that requirement on the trunk?

A.switchport trunk allowed vlan 10,20,30
B.switchport access vlan 10,20,30
C.switchport mode dynamic auto
D.switchport trunk native vlan 10,20,30
AnswerA

The correct command for a trunk interface is `switchport trunk allowed vlan 10,20,30`; it explicitly defines the allowed VLAN list for IEEE 802.1Q tagging. By specifying only VLANs 10, 20, and 30, the administrator ensures that frames from other VLANs are not forwarded across this trunk, providing precise traffic segmentation between the two switches.

Why this answer

The correct command is the one that explicitly sets the allowed VLAN list on the trunk. In plain language, the administrator wants the inter-switch link to carry only the named VLANs instead of every VLAN by default. Cisco trunks can transport multiple VLANs, but that does not mean every VLAN should always be permitted. Restricting the allowed list supports cleaner design and helps reduce unnecessary VLAN transport.

This is a common CCNA switching task because it distinguishes between creating a trunk and controlling what the trunk actually carries. Simply enabling trunking is not enough when the requirement names exact VLANs. The answer must directly restrict the allowed list rather than change the native VLAN or apply an unrelated access-port command.

Exam trap

A common exam trap is selecting commands that do not correctly restrict VLANs on a trunk. For example, using 'switchport access vlan 10,20,30' is invalid because access ports support only one VLAN. Another trap is confusing the native VLAN setting with allowed VLANs; 'switchport trunk native vlan' only defines the untagged VLAN and does not filter VLANs.

Also, relying on dynamic trunk negotiation commands like 'switchport mode dynamic auto' does not restrict VLANs and can lead to trunks carrying all VLANs by default. These mistakes cause VLAN traffic to flow where it shouldn’t, violating design requirements.

Why the other options are wrong

B

Incorrect because 'switchport access vlan' applies only to access ports and cannot specify multiple VLANs; it does not configure trunk VLANs.

C

Incorrect because 'switchport mode dynamic auto' controls trunk negotiation but does not limit which VLANs are allowed on the trunk.

D

Incorrect because 'switchport trunk native vlan' sets only one native VLAN for untagged traffic and does not restrict the allowed VLAN list.

63
MCQhard

A network administrator recently configured BPDU Guard on all access ports of a switch to protect against rogue switches. After the change, users in VLAN 10 report intermittent connectivity issues and frequent link flaps. The administrator checks the switch and notices that several ports are in an err-disabled state. What is the most likely cause of the problem?

A.Root Guard is preventing the port from becoming a root port.
B.BPDU Guard is enabled on access ports that are receiving BPDUs, causing the ports to go into err-disabled state.
C.Loop Guard has detected a unidirectional link and placed the port into err-disabled state.
D.BPDU Guard is globally enabled but not configured on the interface, so the port is err-disabled due to a BPDU received.
AnswerB

BPDU Guard is a security feature that intentionally places a PortFast-enabled access port into err-disabled when any BPDU is received, protecting against rogue switches attempting to participate in spanning tree. When an unauthorized device sends BPDUs, the switch immediately disables the port and logs an error, requiring an administrator to manually re-enable it or rely on errdisable recovery. This matches the scenario where access ports receiving BPDUs are error-disabled.

Why this answer

BPDU Guard is configured to protect against rogue switches by placing a port into an err-disabled state upon receiving a BPDU. In this scenario, BPDU Guard is enabled on access ports that are receiving BPDUs (possibly from a rogue switch or misconfiguration), causing the ports to err-disable and flap. PortFast is not required for BPDU Guard to function; the issue is that BPDUs are being received on ports that are not expected to receive them.

The intermittent connectivity occurs as ports cycle into err-disabled and are re-enabled.

Exam trap

A common mistake is believing BPDU Guard requires PortFast to function; in reality, BPDU Guard can be enabled per-interface without PortFast and will err-disable the port when a BPDU is received.

Why the other options are wrong

A

Root Guard prevents a port from becoming a root port by placing it in a root-inconsistent state, not err-disabled. It does not cause link flaps or err-disable ports.

C

Loop Guard prevents alternate or root ports from becoming designated in the absence of BPDUs, but it does not err-disable ports. It places ports in a loop-inconsistent state, which is not err-disabled.

D

The global 'spanning-tree portfast bpduguard default' command only applies BPDU Guard to PortFast-enabled ports. If a port receives a BPDU and is not PortFast, it will not be err-disabled by this global command. The scenario states BPDU Guard was configured on all access ports, implying interface-level configuration.

64
MCQmedium

A network administrator enables DHCP snooping on a Catalyst switch with 'ip dhcp snooping' and 'ip dhcp snooping vlan 10', and configures the uplink Gi1/0/24 with 'ip dhcp snooping trust'. A rogue DHCP server is connected to access port Gi1/0/5 (untrusted) in VLAN 10 and sends a DHCPOFFER. What does the switch do with the DHCPOFFER?

A.Forward the DHCPOFFER to the client because it is a DHCP message in VLAN 10.
B.Drop the DHCPOFFER because server messages are not allowed on an untrusted port.
C.Forward the DHCPOFFER only if its source MAC address is in the DHCP snooping binding table.
D.Convert the untrusted port to a trusted port automatically after receiving the first DHCPDISCOVER.
AnswerB

Correct: DHCPOFFER, DHCPACK and DHCPNAK received on an untrusted port are dropped, which blocks rogue DHCP servers.

Why this answer

With DHCP snooping, ports are untrusted by default. Client messages such as DHCPDISCOVER and DHCPREQUEST are accepted from untrusted ports, but DHCP server messages (DHCPOFFER, DHCPACK, DHCPNAK) received on an untrusted port are dropped. Only ports configured with ip dhcp snooping trust (such as the uplink toward the legitimate server) may send server messages, so the rogue server's offer is dropped.

Exam trap

The trap here is assuming that untrusted ports cannot send any DHCP messages, when in fact they can send client-originated requests but cannot receive server replies.

Why the other options are wrong

A

Server messages on untrusted ports are dropped.

C

The port trust state decides, not the binding table.

65
PBQmedium

You are connected to SW1 (a Layer 2 switch). Ports G0/1 and G0/2 each connect to a NIC of a hypervisor host that tags VLANs 10 and 20 with 802.1Q. Configure both ports as trunks that carry only VLANs 10 and 20, with native VLAN 99.

Network Topology
G0/1, G0/2HostSW1

Hints

  • •Use the 'switchport trunk allowed vlan' command to restrict which VLANs are carried.
  • •The native VLAN must match on both ends of the trunk.
A.interface range gigabitethernet0/1-2 switchport mode trunk switchport trunk allowed vlan 10,20 switchport trunk native vlan 99
B.interface range gigabitethernet0/1-2 switchport mode trunk switchport trunk allowed vlan 10-20 switchport trunk native vlan 99
C.interface range gigabitethernet0/1-2 switchport mode trunk switchport trunk allowed vlan 10,20 switchport native vlan 99
D.interface range gigabitethernet0/1-2 switchport mode trunk switchport trunk allowed vlan 10,20 switchport trunk native vlan 1
AnswerA
solution
! SW1
interface gigabitethernet0/1
switchport mode trunk
switchport trunk allowed vlan 10,20
switchport trunk native vlan 99
interface gigabitethernet0/2
switchport mode trunk
switchport trunk allowed vlan 10,20
switchport trunk native vlan 99

Why this answer

The correct configuration sets the ports as trunk, restricts allowed VLANs to exactly 10 and 20 with 'switchport trunk allowed vlan 10,20', and sets the native VLAN to 99 with 'switchport trunk native vlan 99'. This matches every requirement in the question: trunk mode, only VLANs 10 and 20 carried, native VLAN 99.

Exam trap

The trap here is confusing the allowed VLAN list syntax — candidates often pick '10-20' thinking it means '10 and 20', when it actually permits every VLAN in that range.

Why the other options are wrong

B

The specific factual error is using a range (10-20) instead of a list (10,20), which includes unintended VLANs.

C

The specific factual error is omitting the 'trunk' keyword in the native VLAN command, which is required for trunk ports.

D

The specific factual error is setting the native VLAN to 1 instead of 99, which does not meet the requirement.

66
PBQmedium

You are connected to SW1 via the console. SW1 is a Layer 2 switch with two VLANs: VLAN 10 (Sales) and VLAN 20 (Engineering). Port G0/1 is connected to a sales PC, and port G0/2 is connected to an engineering PC. You need to ensure that each PC is in the correct VLAN. However, the sales PC is currently unable to ping the engineering PC because they are in different VLANs. You have a router R1 connected to SW1 via port G0/3. Configure inter-VLAN routing using Router-on-a-Stick on R1, and ensure SW1's port G0/3 is properly configured as a trunk. Use 192.168.10.1/24 as the VLAN 10 gateway and 192.168.20.1/24 as the VLAN 20 gateway on R1.

Network Topology
G0/1G0/1G0/3G0/3G0/0G0/2SW1PC1VLAN 10R1PC2VLAN 20

Hints

  • •Router-on-a-Stick uses subinterfaces on the router with 802.1Q encapsulation.
  • •The switch port connected to the router must be configured as a trunk to carry multiple VLANs.
  • •Each subinterface must have an IP address in the respective VLAN's subnet.
A.Configure subinterfaces on R1 with encapsulation dot1Q and assign IP addresses in VLAN 10 and VLAN 20. Configure SW1 interface G0/3 as a trunk port.
B.Configure a routed port on SW1 G0/3 and assign an IP address. Then configure static routes on R1 to reach each VLAN.
C.Configure SW1 interface G0/3 as an access port in VLAN 10. Then configure R1 with a single IP address in VLAN 10 and enable proxy ARP.
D.Configure SW1 interface G0/3 as a trunk port. Then configure R1 with a single IP address on the physical interface and enable VLAN routing using the 'vlan' command.
AnswerA
solution
! R1
interface GigabitEthernet0/0.10
encapsulation dot1Q 10
ip address 192.168.10.1 255.255.255.0
interface GigabitEthernet0/0.20
encapsulation dot1Q 20
ip address 192.168.20.1 255.255.255.0
interface GigabitEthernet0/0
no shutdown

! SW1
interface GigabitEthernet0/3
switchport mode trunk

Why this answer

Router-on-a-Stick requires the router's physical interface to be divided into subinterfaces, each tagged with 802.1Q encapsulation for a specific VLAN and assigned an IP address that serves as that VLAN's default gateway. The switch port facing the router must be configured as a trunk so it can carry tagged frames for both VLAN 10 and VLAN 20. This combination lets R1 route between the two VLANs while SW1 remains a Layer 2 device.

Exam trap

The trap here is confusing a routed port (Layer 3 switch port) with a trunk port; candidates who pick the routed-port option forget that inter-VLAN routing via a router requires 802.1Q subinterfaces on a trunk, not a single Layer 3 link.

Why the other options are wrong

B

Layer 2 switches do not support routed ports; they only support switchport mode access or trunk.

C

An access port cannot carry multiple VLANs; a trunk is required for Router-on-a-Stick.

D

Router-on-a-Stick requires subinterfaces; a single IP address on the physical interface only handles one VLAN. The 'vlan' command is not used on routers for inter-VLAN routing.

67
PBQmedium

You are connected to SW1 via the console. SW1 is a multilayer switch with SVIs for VLANs 10 (192.168.10.1/24) and 20 (192.168.20.1/24). Hosts in VLAN 10 can ping their default gateway (192.168.10.1), but cannot ping hosts in VLAN 20. You suspect IP routing is not enabled or the SVIs are not up.

Hints

  • •Check if IP routing is enabled globally.
  • •Verify that the SVIs are up/up.
  • •Use ping with source to test connectivity between VLANs.
A.Enable IP routing on SW1 with the 'ip routing' global configuration command.
B.Configure a trunk port between SW1 and an external router, then enable routing on the router.
C.Ensure the SVIs are not shut down and have the 'no shutdown' command applied.
D.Add a static route on SW1 pointing to the VLAN 20 subnet via the VLAN 10 SVI.
AnswerA
solution
! SW1
ip routing

Why this answer

A multilayer switch requires 'ip routing' to forward packets between VLANs. Without it, the switch acts as a Layer 2 device. Enabling IP routing allows the SVIs to route traffic between VLANs.

The verification commands confirm routing is active and SVIs are operational.

Exam trap

The trap is that candidates may focus on interface status or static routes, overlooking the fundamental requirement of 'ip routing' on a multilayer switch. Remember that SVIs can be up and pingable, but without IP routing enabled, the switch cannot forward packets between VLANs.

Why the other options are wrong

B

The specific factual error is that the question states SW1 is a multilayer switch with SVIs, so it can route internally without an external router. The issue is that IP routing is not enabled on the switch itself.

C

The specific factual error is that the SVIs are already up (hosts can ping the gateway), so 'no shutdown' is not the missing step. The problem is at Layer 3 routing, not Layer 2/3 interface status.

D

The specific factual error is that directly connected networks do not require static routes; the switch automatically installs them when the SVI is up. The problem is that 'ip routing' is not enabled, so the switch does not use these routes for forwarding.

68
MCQhard

An 802.1X port on a Cisco IOS-XE switch is configured with a static access VLAN 10, where the workstation's default gateway (192.168.10.1, SVI Vlan10) lives. The workstation authenticates successfully but cannot ping its default gateway. Based on the exhibit, what is the most likely cause?

A.The RADIUS server has not been configured with the correct shared secret, causing authentication to fail silently.
B.The RADIUS server assigned VLAN 50 to the session, and VLAN 50 has no gateway, so the workstation is not in VLAN 10.
C.The switch port is in 'err-disabled' state due to a port-security violation, preventing any traffic.
D.The workstation's supplicant is not configured with the correct EAP method, causing the authentication to use the guest VLAN instead.
AnswerB

Correct: the Server Policies show VLAN 50 from the RADIUS server, Gi1/0/1 is in VLAN 50, and the gateway SVI exists only in VLAN 10.

Why this answer

The session is authorized with dot1x authentication success, so the credentials and RADIUS shared secret are fine. The Server Policies section shows the RADIUS server assigned VLAN 50, overriding the configured access VLAN 10, and show vlan brief shows Gi1/0/1 in VLAN 50. The only SVI is Vlan10, so the workstation sits in a VLAN with no gateway and cannot reach 192.168.10.1.

Exam trap

Cisco often tests the distinction between authentication success (port state 'authorized') and network connectivity success (correct VLAN assignment), tricking candidates into focusing on authentication failures when the real issue is a post-authentication VLAN misconfiguration.

Why the other options are wrong

A

A wrong shared secret would prevent authentication, but authentication succeeded.

C

The port is authorized, not err-disabled.

D

Authentication succeeded, so this is not a guest VLAN placement.

69
MCQhard

In a network running STP, SW2 became the root bridge for VLAN 10. Both SW1 and SW2 have the same bridge priority. Why did SW2 become the root?

A.Because SW2 has the lower bridge ID due to the lower MAC address.
B.Because SW2 has the higher VLAN number configured.
C.Because SW2 has more trunk ports than SW1.
D.Because SW2 has the highest bridge priority.
AnswerA

In STP, each switch's bridge ID is composed of a configurable priority (default 32768) and its MAC address, concatenated to form a unique identifier. When SW1 and SW2 have equal bridge priority, the election breaks the tie by comparing the MAC portion, and the numerically lower MAC address wins. Since SW2's MAC is lower, its bridge ID is lower, making it the root bridge for the VLAN.

Why this answer

SW2 became the root bridge because its bridge ID is lower. In practical terms, spanning tree elects the root bridge by comparing bridge IDs, which are based on priority plus MAC address. The device with the lowest bridge ID wins. In the exhibit, both switches use the same priority, so the tie is broken by the lower MAC address.

This is a classic STP interpretation question. Many learners focus only on priority, but if priorities match, the MAC address becomes decisive.

Exam trap

Remember, in STP, lower values are preferred. If priorities match, the MAC address decides the root bridge.

Why the other options are wrong

B

The VLAN number is not a factor in the STP root bridge election. The election is based solely on bridge ID, which consists of bridge priority and MAC address.

C

The number of trunk ports does not affect the root bridge election. STP uses bridge ID (priority and MAC address) to determine the root bridge, not port count or type.

D

The root bridge is elected based on the lowest bridge ID, not the highest. A higher bridge priority (numerically larger) makes a switch less likely to become root.

70
MCQmedium

A campus switch has VLANs 10, 20, and 30 configured. Port GigabitEthernet0/5 connects to a server that must send and receive traffic for all three VLANs, and the server's NIC supports 802.1Q tagging. The administrator wants the server to handle VLAN tagging itself. Which configuration on GigabitEthernet0/5 is appropriate?

A.switchport mode access and switchport access vlan 10
B.switchport mode trunk, switchport trunk native vlan 10, and switchport access vlan 20
C.switchport mode trunk and switchport trunk allowed vlan 10,20,30
D.switchport mode dynamic desirable and switchport trunk allowed vlan 10,20,30
AnswerC

A trunk port with the allowed VLAN list permits the server to send and receive tagged frames for VLANs 10, 20, and 30. Because the server NIC supports 802.1Q, it can create and interpret the tags itself, so the switch does not need to assign an access VLAN. This matches the requirement for a single interface carrying multiple VLANs.

Why this answer

When a server NIC performs 802.1Q tagging itself, the switch port must be a trunk so tagged frames for multiple VLANs can pass. Restricting the allowed VLAN list to 10, 20, and 30 limits unnecessary traffic and matches the requirement. A static trunk avoids DTP negotiation issues with a server that does not run DTP.

Exam trap

The trap here is assuming an access port can carry multiple VLANs if the NIC tags frames, but access ports do not forward tagged traffic for other VLANs.

71
MCQhard

A network engineer has enabled DHCP snooping on a Catalyst switch to prevent rogue DHCP servers. All access ports in VLAN 10 are untrusted. A router attached to a trunk port on the switch acts as the default gateway for VLAN 10 and is configured with the ip helper-address 10.1.2.5, which points to a remote DHCP server. After enabling DHCP snooping, hosts in VLAN 10 cannot obtain IP addresses; packet captures show DHCPDISCOVER messages are sent, but no DHCPOFFER is received. What is the most likely cause?

A.The router's ip helper-address command is pointing to an incorrect DHCP server IP address.
B.The switch port connecting to the router is not configured as a trusted port for DHCP snooping.
C.The DHCP server is on a different subnet, so the switch needs a switched virtual interface (SVI) in VLAN 10 with an IP address for Layer 3 connectivity.
D.DHCP snooping is dropping DHCPDISCOVER messages because the client access ports are untrusted.
AnswerB

DHCP snooping trusts only designated ports to forward DHCP server messages. Since the router relays the DHCPOFFER onto the trunk port, an untrusted port will cause the switch to discard the offer, resulting in DHCP failure.

Why this answer

DHCP snooping treats all ports as untrusted by default. When a router acting as a DHCP relay is connected to an untrusted trunk port, the switch drops DHCPOFFER messages received from the router because they originate from an untrusted interface. Configuring the trunk port as trusted allows DHCP server responses (OFFER, ACK) to pass through to clients.

Exam trap

Cisco often tests the distinction that DHCP snooping blocks DHCP server messages (OFFER/ACK/NAK) on untrusted ports, not client messages (DISCOVER/REQUEST), leading candidates to incorrectly assume client messages are dropped.

Why the other options are wrong

A

This distractor exploits the common tendency to blame the helper address configuration first, overlooking the security feature that silently drops the returning DHCPOFFER.

C

This plays on the misconception that a switch requires an IP address on the client VLAN to facilitate DHCP, when in fact the router acting as the relay agent provides Layer 3 connectivity.

D

This misinterprets DHCP snooping behavior: it assumes all DHCP traffic is filtered on untrusted ports, overlooking the critical distinction that only server-side messages are blocked, not client requests.

72
PBQhard

You are troubleshooting a PC (PC-A) connected to switch SW1, which is connected to router R1. PC-A has an APIPA address (169.254.23.45) and cannot reach the internet (203.0.113.1). You confirm that R1 has a correctly configured DHCP pool for the 192.168.10.0/24 subnet, but the DHCP service is not enabled. The network uses VLAN 10 with subnet 192.168.10.0/24. Verify and correct the configuration on PC-A, SW1, and R1 to restore full connectivity.

Network Topology
G0/0/0192.168.10.1/24G0/0/0192.168.10.1/24203.0.113.1PC-ASW1R1Internet

Hints

  • •Check if the DHCP server process is running on R1.
  • •APIPA addresses (169.254.x.x) indicate DHCP failure.
  • •The DHCP pool is configured but not yet active.
A.Enable the DHCP service on R1 with the 'service dhcp' command.
B.Configure a default gateway on PC-A with the IP address 192.168.10.1.
C.Change the VLAN on SW1's interface connected to PC-A from VLAN 10 to VLAN 1.
D.Add the 'ip helper-address' command on R1's interface connected to SW1.
AnswerA
solution
! R1
service dhcp

! SW1


! PC-A

Why this answer

PC-A has an APIPA address, so it received no DHCP offer. The pool on R1 is correct, and the PC is in VLAN 10 with R1 reachable on the same subnet, but the exhibit shows R1 has the DHCP server service disabled (no service dhcp). Enabling it with service dhcp lets R1 answer DHCP discovers from the pool. ip helper-address is only needed to relay to a server on another subnet.

Exam trap

Do not assume that configuring a DHCP pool is sufficient; the DHCP service must be explicitly enabled with 'service dhcp'. Also, remember that APIPA addresses indicate DHCP failure, not just a missing gateway.

Why the other options are wrong

B

The PC's APIPA address cannot reach the 192.168.10.1 gateway because it is not in the same subnet, so configuring a default gateway alone does not restore connectivity.

C

Changing the VLAN to VLAN 1 would isolate PC-A from the correct subnet (VLAN 10), breaking connectivity instead of fixing it.

D

The 'ip helper-address' command is used on interfaces that need to forward DHCP broadcasts to a remote DHCP server; here R1 itself is the DHCP server and is directly attached, so the command is not needed.

73
PBQhard

You are connected to a multilayer switch MLS1 via the console. Configure MLS1 so that IP phones connected to interface GigabitEthernet0/1 receive power via PoE, use VLAN 10 for data traffic, and use VLAN 20 for voice traffic, while the access port for an AP on GigabitEthernet0/2 should be placed in VLAN 30 and have PoE disabled. Verify your configuration using appropriate show commands.

Hints

  • •Voice VLAN is configured with a separate command from the access VLAN.
  • •PoE can be disabled per interface using 'power inline never'.
  • •Use 'show interfaces switchport' to see both voice and access VLAN assignments.
A.interface GigabitEthernet0/1 switchport mode access switchport access vlan 10 switchport voice vlan 20 power inline auto ! interface GigabitEthernet0/2 switchport mode access switchport access vlan 30 power inline never
B.interface GigabitEthernet0/1 switchport mode trunk switchport trunk allowed vlan 10,20 power inline auto ! interface GigabitEthernet0/2 switchport mode access switchport access vlan 30 power inline never
C.interface GigabitEthernet0/1 switchport mode access switchport access vlan 20 switchport voice vlan 10 power inline auto ! interface GigabitEthernet0/2 switchport mode access switchport access vlan 30 power inline never
D.interface GigabitEthernet0/1 switchport mode access switchport access vlan 10 switchport voice vlan 20 power inline never ! interface GigabitEthernet0/2 switchport mode access switchport access vlan 30 power inline auto
AnswerA
solution
! MLS1
interface GigabitEthernet0/1
switchport voice vlan 20
power inline auto
interface GigabitEthernet0/2
switchport access vlan 30
power inline never

Why this answer

For the IP phone port (G0/1), you need to enable PoE (power inline auto) and configure the voice VLAN (switchport voice vlan 20) so that the phone uses VLAN 20 for voice and the access VLAN 10 for data. For the AP port (G0/2), you must change the access VLAN to 30 and disable PoE (power inline never) to prevent powering the AP through the switch. Verify with 'show interfaces switchport' to confirm voice VLAN and access VLAN settings, and 'show power inline' to check PoE status.

Exam trap

A common trap is confusing the voice VLAN command with trunking or swapping the access and voice VLANs. Also, remember that IP phones require PoE, while the AP in this scenario does not. Always verify with show commands.

Why the other options are wrong

B

The specific factual error is that IP phones typically use an access port with a voice VLAN, not a trunk port. Trunking is unnecessary and can cause compatibility issues.

C

The specific factual error is confusing the access VLAN and voice VLAN assignments. The voice VLAN is configured with 'switchport voice vlan', and the access VLAN with 'switchport access vlan'.

D

The specific factual error is reversing the PoE settings: 'power inline never' on the phone port and 'power inline auto' on the AP port.

74
MCQhard

A network engineer has implemented DHCP snooping on a Cisco switch to prevent unauthorized DHCP servers. The switch's VLAN 100 SVI is configured with ip helper-address to relay DHCP requests to a legitimate server in VLAN 200. Clients in VLAN 100 cannot obtain IP leases, even though the DHCP server is reachable from the switch and has available addresses.

A.The ip helper-address command has been incorrectly applied to VLAN 100 instead of VLAN 200.
B.The switch port that connects to the DHCP server's VLAN is not configured as a trusted DHCP snooping port.
C.DHCP snooping must be disabled globally because it conflicts with the configured DHCP relay agent.
D.The DHCP server lacks a valid default gateway, preventing replies from reaching the relay agent's SVI subnet.
AnswerB

DHCP snooping drops DHCPOFFER and DHCPACK messages received on untrusted ports, since only trusted ports are allowed to accept server-originated replies. The switch port connected to the legitimate DHCP server in VLAN 200 must be explicitly configured as trusted with 'ip dhcp snooping trust'. Without that, the relay agent forwards the client's DISCOVER, but the server's OFFER/ACK are silently discarded, leaving clients without a lease despite the relay configuration.

Why this answer

DHCP snooping treats all switch ports as untrusted by default, which blocks DHCP server messages (OFFER, ACK) from entering the switch. Even though the switch itself can reach the DHCP server, the relayed reply from the server arrives on a port that is not trusted, so DHCP snooping drops the packet before it can be forwarded to the client. Configuring the port connecting to the DHCP server as a trusted port allows the server's responses to pass through the switch, resolving the issue.

Exam trap

Cisco often tests the interaction between DHCP snooping and DHCP relay, where candidates mistakenly think the relay bypasses snooping or that the issue is with the helper-address configuration, rather than the untrusted port blocking the server's unicast reply.

Why the other options are wrong

A

Many engineers mistakenly think the helper should reside on the server VLAN; however, it must reside on the client-facing L3 interface.

C

A common misconception is that DHCP relay bypasses snooping, but snooping still inspects the server's unicast response and drops it unless the ingress port is trusted.

D

Candidates often suspect routing issues, but verified reachability eliminates this. The problem lies in the snooping policy, not IP connectivity.

75
MCQmedium

A switch stack is running PVST+. Users on VLAN 40 lose connectivity for roughly 30 seconds every time the uplink on SW2 flaps. Based on the exhibit, which change would most directly improve convergence for this VLAN?

A.Configure spanning-tree mode rapid-pvst.
B.Increase the bridge priority on SW2 for VLAN 40.
C.Disable PortFast on all access ports.
D.Convert the uplink to a routed port.
AnswerA

Configuring `spanning-tree mode rapid-pvst` directly addresses the 30-second connectivity loss by enabling Rapid PVST+ (R-PVST+). PVST+ utilises fixed listening and learning states, contributing to the observed delay during topology changes. R-PVST+ employs a rapid convergence mechanism, such as the Proposal/Agreement (P/A) process, allowing designated and root ports to transition to forwarding much faster, often within sub-seconds. This significantly reduces the reconvergence time for VLAN 40 when SW2's uplink flaps, directly improving user connectivity.

Why this answer

The switch runs PVST+ (Spanning tree enabled protocol ieee). PVST+ depends on timer-based transitions: a port moving to forwarding passes through listening and learning (15 s each), and indirect failures also wait for Max Age, so VLAN 40 can be unreachable for roughly 30 seconds or more after the uplink flaps. Rapid PVST+ (spanning-tree mode rapid-pvst) uses the proposal/agreement handshake on point-to-point links and converges in about a second or a few seconds.

Exam trap

A frequent exam trap is selecting options that change the root bridge election or port roles, such as increasing bridge priority, assuming this will speed up convergence. While root bridge placement affects path selection, it does not reduce the inherent delay caused by legacy STP timers. Another trap is disabling PortFast on access ports, which only affects edge port transitions and does not influence uplink link flap recovery times.

Additionally, converting uplinks to routed ports changes the network design and removes STP from those ports, which is not the intended solution for VLAN-specific STP convergence delays. The key mistake is confusing topology optimization with protocol speed improvements.

Why the other options are wrong

B

Increasing bridge priority changes root bridge election but does not speed up the STP convergence process, so it does not resolve the 30-second connectivity loss.

C

Disabling PortFast affects only edge ports and does not influence the convergence time of uplink ports or VLANs experiencing link flaps.

D

Converting the uplink to a routed port removes it from STP but alters network design and does not specifically improve VLAN 40’s STP convergence speed.

Page 1 of 3 · 221 questions totalNext →

Ready to test yourself?

Try a timed practice session using only VLAN questions.