Courseiva

CCNA VLAN Questions

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

76
MCQhard

A network engineer receives a call that users in VLAN 10 on Switch B cannot ping the default gateway, which is a router on a stick connected to Switch A. The engineer checks the Spanning Tree Protocol state on the interface connecting Switch A to Switch B (GigabitEthernet0/1) and finds it is in a root-inconsistent state. Which command output best explains the cause of the issue?

A.The interface is in err-disable state due to BPDU guard.
B.Root guard is enabled and the port received a superior BPDU, causing it to become root-inconsistent.
C.Loop guard is enabled and the port is in a blocking state due to missing BPDUs.
D.The port is in a forwarding state but the VLAN is misconfigured.
AnswerB

Root guard is correctly the cause: when a port configured with root guard receives a superior BPDU (i.e., a BPDU that would make the local switch root or change the root bridge), the port is moved to a root-inconsistent state. This blocks all traffic on the port to protect the existing root bridge and prevent a rogue switch from hijacking the spanning tree. The symptom matches exactly—the port is administratively placed in this state, not in err-disable or loop-inconsistent.

Why this answer

Root guard, when enabled on a port, places that port into a root-inconsistent blocking state if it receives a superior BPDU, preventing the switch from becoming the root bridge. This root-inconsistent state stops forwarding traffic, which explains why users in VLAN 10 cannot reach the default gateway. The port remains physically up but is blocked by spanning tree, so normal interface status would not show a down state, making the root-inconsistent state the key indicator.

Exam trap

Candidates often confuse root guard with BPDU guard: BPDU guard err-disables a port upon receiving any BPDU on a PortFast port, while root guard responds to superior BPDUs by placing the port in root-inconsistent state, not err-disable.

Why the other options are wrong

A

BPDU guard causes an err-disable state, which would show the interface as down or err-disabled, not as root-inconsistent.

C

Loop guard places a port into loop-inconsistent blocking state when BPDUs stop being received, not when a superior BPDU is received.

D

A forwarding state would allow traffic; the problem here is that the port is in a blocked state due to root guard, not a misconfigured VLAN.

77
PBQhard

You are connected to R1. Configure HSRP so that R1 becomes the active router for VLAN 10, with a virtual IP of 192.168.10.1. Ensure that R1 preempts if it comes back online after a failure. Also, configure R1 to decrement its HSRP priority by 20 if its GigabitEthernet0/1 interface goes down. The current configuration shows both routers as active — identify and fix the issues.

Network Topology
Gi0/0.10192.168.10.3/24Gi0/0.10192.168.10.2/24switchR1R2

Hints

  • •Both routers show Active because they have equal priority and no preempt.
  • •The virtual IP configured is 192.168.10.254 but the task requires 192.168.10.1.
  • •To ensure R1 is active, set its priority higher than R2's default (100) and enable preempt.
A.Change the virtual IP to 192.168.10.1, set priority to 110, enable preempt, and track interface GigabitEthernet0/1 with decrement 20.
B.Change the virtual IP to 192.168.10.1, set priority to 90, enable preempt, and track interface GigabitEthernet0/1 with decrement 20.
C.Change the virtual IP to 192.168.10.254, set priority to 110, enable preempt, and track interface GigabitEthernet0/1 with decrement 20.
D.Change the virtual IP to 192.168.10.1, set priority to 110, enable preempt, but do not track any interface.
AnswerA
solution
! R1
interface GigabitEthernet0/0.10
standby 10 ip 192.168.10.1
standby 10 priority 110
standby 10 preempt
standby 10 track GigabitEthernet0/1 20

Why this answer

R1 is Active with no standby because R2 is configured with virtual IP 192.168.10.1 while R1 uses 192.168.10.254: HSRP hellos with a different virtual IP are ignored, so each router sees no peer. Set the virtual IP to 192.168.10.1 on R1 so both agree, give R1 a priority above R2's default 100 (110), enable preempt so it reclaims the active role after a failure, and track GigabitEthernet0/1 with a decrement of 20.

Exam trap

Watch for three common mistakes: (1) forgetting to set a higher priority to win the election, (2) using the wrong virtual IP address, and (3) omitting the track command when required. Also note that preempt alone does not guarantee active status if priorities are equal.

Why the other options are wrong

B

Priority 90 is lower than R2's 100.

C

The virtual IP address must be consistent across all HSRP routers and match the configured gateway; a mismatch prevents proper operation.

D

Without tracking, R1's priority remains unchanged even if the uplink fails, so R1 would remain active despite losing connectivity, causing traffic black-holing.

78
MCQmedium

A switch displays the following output: Interface Status VLAN Gi1/0/5 connected 20 Gi1/0/6 notconnect 1 Gi1/0/24 trunk trunk Which interface is operating as an access port in VLAN 20?

A.Gi1/0/5
B.Gi1/0/6
C.Gi1/0/24
D.None of the interfaces
AnswerA

The output for Gi1/0/5 shows an interface that is up/connected and explicitly assigned to VLAN 20 as an access port, which exactly matches the requirement stated in the question. The status column indicates the link is active, and the VLAN column confirms membership in VLAN 20, leaving no doubt that this is the correct interface.

Why this answer

The output explicitly shows Gi1/0/5 in VLAN 20 and not operating as a trunk.

Exam trap

Be careful not to confuse trunk ports with access ports or assume interfaces not shown in the output are relevant.

Why the other options are wrong

B

Gi1/0/6 is an access port in VLAN 1 (the default VLAN), not VLAN 20. The question specifically asks for an interface operating as an access port in VLAN 20, so this option is incorrect.

C

Gi1/0/24 is configured as a trunk port, which carries traffic for multiple VLANs and is not an access port. Access ports belong to a single VLAN, so this option is incorrect.

D

Gi1/0/5 is clearly an access port in VLAN 20, so there is an interface that matches the description. Therefore, 'None of the interfaces' is incorrect.

79
MCQhard

Users on VLAN 100 report intermittent connectivity to the server farm. The access switch shows no errors on its uplink, but ServerFarm-SW1 reports problems on its Gi0/1 interface, which connects to the access switch over fiber. The engineer runs 'show interfaces GigabitEthernet0/1' on ServerFarm-SW1 (exhibit). What is the most likely cause?

A.A duplex mismatch on the interface.
B.A physical-layer fault on the receive path, such as a failing SFP or damaged or dirty fiber.
C.A VLAN mismatch between the two switches.
D.A speed mismatch caused by disabled auto-negotiation.
AnswerB

Correct: the input errors are all CRC errors on a full-duplex link with no collisions, so frames are being corrupted in transit, pointing at the SFP or fiber.

Why this answer

ServerFarm-SW1 Gi0/1 is up at 1000 Mb/s full duplex (matching the other side, with no collisions or late collisions) but has tens of thousands of input errors, all of them CRC errors. Frames are being corrupted on the receive path while the other switch's transmit side shows nothing wrong, which points to a physical-layer fault such as a failing or incompatible SFP or damaged/dirty fiber. Duplex and speed are not the cause.

Exam trap

Cisco often tests the distinction between 'show interfaces' (which shows input errors but not the specific physical-layer cause) and 'show controllers' (which reveals the exact physical-layer errors), leading candidates to mistakenly choose duplex mismatch or cable length issues without recognizing that the command output points to SFP or transceiver problems.

Why the other options are wrong

A

No collisions or late collisions; duplex is full.

C

VLAN mismatches do not cause CRC input errors.

D

The link is up at the expected speed and duplex.

80
Multi-Selecthard

A trunk link between two switches is up, but hosts in VLAN 30 on opposite switches cannot communicate. VLAN 10 works across the same trunk. Which two causes are the most likely?

Select 2 answers
A.VLAN 30 is not allowed on the trunk on one side
B.VLAN 30 may not exist in the VLAN database on the affected switch
C.The trunk native VLAN should always be 30
D.PortFast must be disabled on the access ports in VLAN 30
AnswersA, B

A trunk port has an allowed VLAN list, and both ends must include VLAN 30 in that list for its traffic to cross the link. If one switch's trunk configuration omits VLAN 30 (via the allowed vlan command), the trunk remains up and carries other VLANs, but frames tagged with VLAN 30 are discarded at that port. This mismatch is a frequent cause of a single VLAN failing while the trunk itself appears operational.

Why this answer

When one VLAN fails but others work across the same trunk, the problem is likely VLAN-specific. VLAN 30 may not exist on one switch or may not be allowed on the trunk. Option C is incorrect because the native VLAN does not need to be 30; a native VLAN mismatch would typically cause connectivity issues on all VLANs, not just VLAN 30.

Option D is incorrect because PortFast only affects the speed at which an access port enters the forwarding state and does not impact communication across an already-up trunk.

Exam trap

Don't assume trunk issues affect all VLANs equally; check for VLAN-specific settings.

Why the other options are wrong

C

The native VLAN ID is not required to match the VLAN that is having connectivity issues; native VLAN is used for untagged traffic on the trunk and does not affect communication for specific VLANs like VLAN 30.

D

PortFast is used on access ports to speed up the transition to forwarding state and is unrelated to inter-VLAN communication across a trunk. Disabling PortFast would not resolve connectivity issues for VLAN 30 hosts on different switches.

81
MCQhard

A switch port is configured with `switchport voice vlan 150` and `switchport access vlan 20`. Which statement best explains the design purpose?

A.It separates voice and data traffic on the same edge port by assigning them to different VLANs.
B.It turns the port into a routed WAN interface.
C.It forces the phone to use CAPWAP before receiving power.
D.It makes VLAN 150 the native VLAN on all trunks automatically.
AnswerA

The `switchport voice vlan 150` command marks the port as a Cisco Unified Communications access port, so it instructs an attached IP phone to tag its voice frames with VLAN 150 while the PC behind the phone remains untagged on the data VLAN. As a result, voice and data traffic share the same physical cable but are isolated into separate Layer 2 broadcast domains, allowing distinct QoS policies, subnets, and security controls to be applied independently.

Why this answer

The design purpose is to let the switch support a phone and an attached workstation on the same physical access port while placing their traffic into different VLANs. In practical terms, the phone can use the voice VLAN while the user's data traffic uses the access VLAN. This is a common enterprise edge design for IP telephony.

The key idea is role separation on one port, not trunking the port as a normal inter-switch link.

Exam trap

Avoid confusing voice VLAN configurations with trunking or prioritization settings.

Why the other options are wrong

B

The commands `switchport voice vlan 150` and `switchport access vlan 20` are used on a Layer 2 switch port, not a routed interface. A routed WAN interface would require `no switchport` and an IP address configuration, which is not present here.

C

CAPWAP (Control and Provisioning of Wireless Access Points) is a protocol used for wireless LAN controller and access point communication, not for voice VLAN configuration. The voice VLAN feature is unrelated to CAPWAP.

D

The `switchport voice vlan` command only affects the specific access port where it is configured, not all trunk ports. The native VLAN on trunks is configured separately with `switchport trunk native vlan`.

82
PBQhard

You are connected to SW1. A spanning-tree topology change left SW2 as the root bridge for VLAN 1, but SW1 is the intended root. Using the root primary macro, make SW1 the root bridge. Then enable PortFast and BPDU Guard on GigabitEthernet0/3 (an edge port connected to a server). Later, a BPDU arrives on Gi0/3 and the port goes err-disabled; once the offending device is removed, recover the port immediately without reloading the switch.

Network Topology
G0/0G0/0G0/1G0/0G0/2G0/0G0/3SW1SW2SW3SW4Server

Hints

  • •'spanning-tree vlan 1 root primary' lowers the priority below the current root (32769) so SW1 wins.
  • •PortFast and BPDU Guard are configured under the interface.
  • •To recover an err-disabled port immediately, bounce it with 'shutdown' then 'no shutdown'; errdisable recovery only re-enables it after the timer.
A.spanning-tree vlan 1 root primary; interface GigabitEthernet0/3; spanning-tree portfast; spanning-tree bpduguard enable; interface GigabitEthernet0/3; shutdown; no shutdown
B.spanning-tree vlan 1 priority 4096; interface GigabitEthernet0/3; spanning-tree portfast; spanning-tree bpduguard enable; interface GigabitEthernet0/3; errdisable recovery cause bpduguard
C.spanning-tree vlan 1 root secondary; interface GigabitEthernet0/3; spanning-tree portfast; spanning-tree bpduguard enable; interface GigabitEthernet0/3; no shutdown
D.spanning-tree vlan 1 root primary; interface GigabitEthernet0/3; spanning-tree portfast; spanning-tree bpdufilter enable; interface GigabitEthernet0/3; shutdown; no shutdown
AnswerA
solution
! SW1
configure terminal
spanning-tree vlan 1 root primary
interface GigabitEthernet0/3
spanning-tree portfast
spanning-tree bpduguard enable
end
configure terminal
interface GigabitEthernet0/3
shutdown
no shutdown
end

Why this answer

SW1 is not root (its Root ID address 0001.1111.1111 belongs to another switch and Gi0/0 is the root port). spanning-tree vlan 1 root primary lowers SW1's priority below the current root's so SW1 wins the election. On the server-facing edge port Gi0/3, spanning-tree portfast and spanning-tree bpduguard enable make the port go straight to forwarding and err-disable if a BPDU arrives. After the offending device is removed, the err-disabled port is recovered immediately with shutdown followed by no shutdown.

Configuring errdisable recovery would only re-enable the port after the recovery interval (300 seconds by default), and bpdufilter would silently ignore BPDUs rather than protect the edge port.

Exam trap

Watch out for confusing root primary vs root secondary, BPDU Guard vs BPDU filter, and the correct method to recover an err-disabled port. Manual shutdown/no shutdown is immediate, while errdisable recovery relies on a timer.

Why the other options are wrong

B

errdisable recovery is timer-based and not an immediate recovery.

C

Wrong macro, and no shutdown alone does not clear err-disable.

D

bpdufilter is not BPDU Guard.

83
PBQhard

You are connected to R1 and SW1. R1 is the DHCP server for VLAN 10 (192.168.10.0/24) and the clients are on the same subnet as R1's subinterface, so no relay is needed. Clients cannot get addresses. Fix the R1 DHCP configuration (an overly broad excluded range and an unneeded ip helper-address pointing at an unrelated server) and fix DHCP snooping on SW1 so the port toward R1 is trusted while the access ports stay untrusted to block rogue DHCP servers.

Network Topology
G0/0.10192.168.10.1/24SW1R1Hosts

Hints

  • •The excluded range removes every address in the pool, so nothing can be leased.
  • •R1 is the server on the clients' own subnet; the stray ip helper-address is not needed.
  • •On SW1, only the port toward the DHCP server (Gi0/1) should be trusted.
A.On R1, remove the ip helper-address and narrow the excluded range to 192.168.10.1 192.168.10.10. On SW1, trust interface Gi0/1 (toward R1) and leave the access ports untrusted.
B.On R1, remove the ip helper-address and narrow the excluded range to 192.168.10.1 192.168.10.10. On SW1, set all ports as trusted.
C.On R1, remove the ip helper-address but keep the excluded range 192.168.10.1 192.168.10.254. On SW1, trust interface Gi0/1.
D.On R1, remove the ip helper-address and narrow the excluded range to 192.168.10.1 192.168.10.10. On SW1, leave interface Gi0/1 untrusted.
AnswerA
solution
! R1
configure terminal
no ip dhcp excluded-address 192.168.10.1 192.168.10.254
ip dhcp excluded-address 192.168.10.1 192.168.10.10
interface GigabitEthernet0/0.10
no ip helper-address 10.0.0.2
end

! SW1
configure terminal
interface GigabitEthernet0/1
ip dhcp snooping trust
end

Why this answer

Two things block DHCP on R1: the excluded-address range covers all of 192.168.10.1-254, leaving nothing to lease (fix it to exclude only the infrastructure addresses, such as 192.168.10.1-192.168.10.10), and the stray ip helper-address is not needed because R1 is the DHCP server on the clients' own subnet, so it is removed. On SW1, DHCP snooping drops DHCP server messages arriving on untrusted ports, including those from the real server, so the port toward R1 (Gi0/1) must be configured with ip dhcp snooping trust while access ports stay untrusted to block rogue servers.

Exam trap

Watch out for two common traps: (1) The helper-address must be the DHCP server's unicast IP, not a broadcast address. (2) DHCP snooping trusted ports are for server connections; untrusted ports are for clients. Misplacing these will break DHCP or security.

Why the other options are wrong

B

All ports trusted defeats DHCP snooping.

C

The excluded range must be narrowed.

D

The port toward the legitimate server must be trusted.

84
MCQhard

A network technician is troubleshooting a router-on-a-stick configuration. R1 has sub-interface G0/0.10 with encapsulation dot1q 10 and IP 192.168.10.1/24, and sub-interface G0/0.20 with encapsulation dot1q 20 and IP 192.168.20.1/24. Hosts in VLAN 10 cannot reach hosts in VLAN 20. The physical interface G0/0 is up and no shutdown. Both sub-interfaces show up/up. What should the technician do next?

A.Verify the switch port connected to R1 is configured as a trunk and allows VLANs 10 and 20.
B.Verify the encapsulation dot1Q numbers on the sub-interfaces match the VLAN assignments.
C.Verify the default gateway settings on hosts in VLANs 10 and 20.
D.Check the physical interface G0/0 for interface errors or duplex mismatches.
AnswerA

This directly addresses the most probable cause: a missing or misconfigured trunk on the switch side. Even with router sub-interfaces up/up, the link must be a trunk carrying the correct VLANs for inter-VLAN routing to function.

Why this answer

The router-on-a-stick configuration requires the switch port connecting to R1 to be configured as a trunk port that permits VLANs 10 and 20. Even though the router sub-interfaces are correctly configured with encapsulation dot1q and IP addresses, if the switch port is in access mode or does not allow the specific VLANs, frames from VLAN 10 or 20 will be dropped by the switch, preventing inter-VLAN routing. The next logical step is to verify the switch port configuration with commands like 'show interfaces trunk' or 'show running-config interface <port>'.

Exam trap

Cisco often tests the misconception that as long as the router sub-interfaces are up/up and have correct encapsulation, inter-VLAN routing should work, leading candidates to overlook the switch trunk configuration as the root cause.

Why the other options are wrong

B

Candidates may think the encapsulation numbers might be swapped, but the stem confirms they are correctly assigned to the respective VLAN IDs.

C

Many candidates jump to end-host configuration, assuming the router is fully reachable because interfaces are up/up, but the trunk is the prerequisite for any communication between VLANs.

D

Candidates might think any communication loss warrants a physical layer check, but here the symptoms point strongly toward a Layer 2 trunking issue.

85
MCQhard

An IP phone connected to switch port Gi0/4 is working and receiving calls, but the PC connected to the phone's data port cannot obtain an IP address. The technician confirms that interface Gi0/4 has switchport mode access and shows switchport access vlan 10 and switchport voice vlan 100. What should the technician do next?

A.Verify the DHCP scope for VLAN 10 on the DHCP server.
B.Verify that CDP is enabled on the IP phone.
C.Verify the QoS trust state on the switch port.
D.Verify the IP phone's passthrough mode for the PC port.
AnswerD

The IP phone acts as a switch; if the phone's PC port is not configured to pass traffic untagged on the correct VLAN (passthrough mode), the PC's frames will be dropped or placed in the wrong VLAN. Checking this setting directly addresses the path from PC to switch.

Why this answer

The PC connected to the IP phone's data port cannot obtain an IP address because the phone's internal switch (passthrough mode) is likely not forwarding traffic from the PC port to the upstream switch. The switch port is correctly configured with access VLAN 10 for data and voice VLAN 100 for voice, so the issue is not with the switch configuration but with the phone's ability to pass data traffic. Verifying the IP phone's passthrough mode ensures the PC port is enabled and forwarding frames to the switch.

Exam trap

Cisco often tests the misconception that a working phone implies all features are functional, but the PC port is a separate logical path that can be independently disabled or misconfigured.

Why the other options are wrong

A

Assumes the switch port configuration alone guarantees proper VLAN delivery to the PC, ignoring the phone's role as a transparent bridge.

B

Confuses the mechanism for voice VLAN assignment with the requirement for data passthrough; CDP's role is only for the phone's own voice VLAN, not for the PC's data VLAN.

C

Misapplies QoS as a potential cause for a connectivity issue; it is a quality-of-service feature and does not block DHCP or initial network access.

86
MCQeasy

A network technician is connecting a new access switch to an existing distribution switch. The access switch will carry multiple VLANs. The distribution switch port is configured with 'switchport mode dynamic desirable'. The technician wants the access switch port to form a trunk automatically, but the access switch port itself must not actively attempt to convert the link to a trunk; it should only respond to the neighbor's negotiation. Which command should be configured on the access switch port?

A.switchport mode dynamic auto
B.switchport mode dynamic desirable
C.switchport mode access
D.switchport nonegotiate
AnswerA

Dynamic auto mode allows the port to become a trunk if the other side initiates trunking. If the distribution switch is set to desirable mode, it will actively attempt to form a trunk, and the access switch port in dynamic auto mode will respond and become a trunk. This meets the requirement of automatic trunk formation.

Why this answer

The switchport mode dynamic auto command puts the port in a passive state: it does not actively try to convert the link to a trunk, but it will become a trunk if the neighbor initiates. Because the distribution port is dynamic desirable, it actively negotiates and the access port responds, forming a trunk. This meets both requirements.

Exam trap

The trap is confusing dynamic auto (passive, responds only) with dynamic desirable (actively initiates), or thinking that nonegotiate still allows automatic trunking.

87
MCQeasy

A network administrator is configuring a Cisco switch. The switch has a management VLAN 99 with IP address 10.10.99.5/24 and default gateway 10.10.99.1. The administrator wants to verify that the switch can reach a server at 10.10.99.100. Which command should be used on the switch to test reachability?

A.show ip route
B.show ip interface brief
C.traceroute 10.10.99.100
D.ping 10.10.99.100
AnswerD

The ping command on a Cisco switch sends ICMP echo requests to the specified IP address and reports replies, directly testing reachability. Since the switch has an IP address in the same subnet as the server, the ping will be sourced from VLAN 99 interface and should succeed if connectivity exists. This is the standard method to verify Layer 3 connectivity from a switch.

Why this answer

To verify reachability to a specific IP address from a Cisco switch, the ping command is the correct tool. It sends ICMP echo requests and waits for replies, providing immediate feedback on whether the destination is reachable. Other commands like show ip interface brief or show ip route only display configuration or routing information and do not test actual connectivity.

Exam trap

The trap here is confusing the display of routing or interface information with an active connectivity test.

88
MCQhard

A switchport on one side of a link is configured as a trunk, but the peer side is configured as an access port. The physical link is up, but VLAN traffic behaves unexpectedly. What is the most likely cause?

A.The two ends disagree on whether the link is a trunk or an access port.
B.The switches must both use the same hostname.
C.The native VLAN must be set to 1 on both sides first.
D.The ports need OSPF enabled.
AnswerA

A switchport in trunk mode encapsulates frames with 802.1Q tags and expects to receive tagged frames, while an access port transmits and receives only untagged frames in a single VLAN. When one end is a trunk and the other is an access port, the access port will drop tagged frames or treat them as invalid, and the trunk port may not accept the untagged frames sent by the access side. This role mismatch prevents proper VLAN segmentation and causes the link to fail at Layer 2.

Why this answer

The most likely cause is a switchport mode mismatch. In practical terms, one side expects the link to carry multiple VLANs with tagging behavior, while the other side treats it as a normal one-VLAN endpoint-style access connection. The physical interface can still come up, but the two ends do not agree on how the traffic should be handled.

This is a classic Layer 2 troubleshooting pattern. The link may not be fully down, but the configuration disagreement causes logical forwarding problems.

Exam trap

Be cautious of assuming all VLAN issues are due to allowed lists or STP. Consider mode mismatches when the link is physically up but traffic is disrupted.

Why the other options are wrong

B

Hostnames are purely for identification and have no impact on switchport operation or VLAN tagging. The trunk/access mismatch is a Layer 2 configuration issue independent of hostnames.

C

While native VLAN mismatch can cause issues on a trunk link, the primary problem here is that one side is configured as access, not trunk. Even if native VLAN is set to 1 on both sides, the access port will still not process tagged frames correctly.

D

OSPF is a Layer 3 routing protocol used for exchanging routes between routers; enabling it does not change the trunk/access mode of a switchport. This issue is a Layer 2 mode mismatch.

89
PBQhard

You are connected to SW1. A LACP EtherChannel between SW1 and SW2 uses GigabitEthernet0/1 and GigabitEthernet0/2 (channel-group 1 mode active on both sides, access VLAN 100). Gi0/2 is not bundling because its hard-coded speed and duplex differ from Gi0/1. All member ports must have identical settings. Gi0/1 is correctly set to speed 1000 and duplex full; only Gi0/2 needs correcting. Make Gi0/2's settings identical to Gi0/1's, and verify the EtherChannel with 'show etherchannel summary'.

Network Topology
Gi0/1Gi0/1EtherChannelSW1SW2

Hints

  • •Check the speed and duplex settings on both member interfaces.
  • •LACP requires all ports in the channel to have identical configuration.
  • •Use the 'show interfaces status' command to quickly see speed/duplex mismatches.
A.Configure interface GigabitEthernet0/2 with 'speed 1000' and 'duplex full', then verify the EtherChannel is up.
B.Configure interface GigabitEthernet0/1 with 'speed 100' and 'duplex half', then verify the EtherChannel is up.
C.Configure interface GigabitEthernet0/2 with 'speed auto' and 'duplex auto', then verify the EtherChannel is up.
D.Configure interface GigabitEthernet0/2 with 'channel-group 1 mode active' and 'switchport access vlan 100', then verify the EtherChannel is up.
AnswerA
solution
! SW1
interface GigabitEthernet0/2
speed 1000
duplex full
end
show etherchannel summary

Why this answer

Gi0/2 is hard-coded to speed 100 and duplex half while Gi0/1 uses speed 1000 and duplex full. Member ports of an EtherChannel must have matching speed and duplex, so the mismatched Gi0/2 is suspended (s) while Gi0/1 is bundled (P). Configuring Gi0/2 with speed 1000 and duplex full makes it identical to Gi0/1 and it joins the bundle.

Changing Gi0/1 would break the correct port, auto settings would not match the explicit Gi0/1 configuration, and re-entering the channel-group or VLAN commands changes nothing because those are already correct.

Exam trap

The trap is that candidates may overlook the speed/duplex mismatch and focus only on the LACP mode or VLAN configuration. Always verify that all physical parameters match before troubleshooting EtherChannel formation.

Why the other options are wrong

B

Gi0/1 is the correct port; changing it is wrong.

C

Settings must be identical to Gi0/1.

D

Already configured; the mismatch remains.

90
MCQhard

Refer to the exhibit. A network engineer expects SW1 to be the root bridge for VLAN 1, but SW2 is the root. The exhibit shows show spanning-tree vlan 1 output from both switches. What is the most likely cause of this issue?

A.SW1 has the default bridge priority and a higher MAC address than SW2.
B.Spanning tree is disabled on SW1 for VLAN 1.
C.SW1 has a bridge priority of 4096, but BPDU guard on SW2's port to SW1 has err-disabled the port.
D.The trunk link between SW1 and SW2 is down.
AnswerA

Both switches advertise priority 32769 for VLAN 1, so the lowest MAC address decides the election. SW2 (000a.f3e5.1234) is lower than SW1 (001b.2c3d.4e5f), so SW2 is root. SW1 even shows a root port toward SW2, so the link and BPDU exchange are working.

Why this answer

Both switches use the default priority (32768 plus the VLAN 1 system ID extension gives 32769), so the election is decided by the lowest MAC address. SW2 (000a.f3e5.1234) has a lower MAC than SW1 (001b.2c3d.4e5f), so SW2 wins. The trunk is up and forwarding (SW1 has a root port toward SW2 and SW2's port is designated), so BPDUs are being exchanged normally.

The fix is to lower SW1's priority, for example with spanning-tree vlan 1 root primary.

Exam trap

The trap is assuming that a switch you consider the main one becomes root automatically. With default priorities the lowest MAC address wins, and a working link with a root port and designated ports shows that BPDUs are being exchanged.

Why the other options are wrong

B

SW1's output shows STP active with a root port, so STP is not disabled.

C

SW1's exhibit shows priority 32769 and all ports are forwarding, which contradicts both parts of this option.

D

The exhibit shows the link forwarding on both ends; the cause is the bridge ID comparison.

91
PBQhard

You are connected to SW1. Two switches, SW1 and SW2, are connected via four GigabitEthernet links. Configure LACP EtherChannel between them using interfaces GigabitEthernet0/1 through GigabitEthernet0/4 on SW1. Set the channel-group mode to active on SW1. The port-channel interface must be configured as a trunk, allowing VLANs 10, 20, 30. However, the EtherChannel is not forming. The current configuration is shown below. Identify and fix the issue, then verify the EtherChannel is operational.

Network Topology
Gi0/1-4Gi0/1-44x linksSW1SW2

Hints

  • •Compare the Layer 2/Layer 3 status of the port-channel interface with the member interfaces.
  • •In 'show etherchannel summary', R means Layer 3 and S means Layer 2; Po1 shows R although the members are Layer 2 trunks.
  • •The port-channel interface must be a Layer 2 switchport to match the member trunk ports.
A.Remove 'no switchport' and IP address from Port-channel1, then configure 'switchport mode trunk' and 'switchport trunk allowed vlan 10,20,30'.
B.Change the channel-group mode on the member interfaces from active to passive.
C.Add the 'switchport nonegotiate' command to the member interfaces.
D.Configure the member interfaces with 'channel-group 1 mode on' instead of active.
AnswerA
solution
! SW1
interface Port-channel1
no ip address 192.168.1.1 255.255.255.0
switchport
switchport mode trunk
switchport trunk allowed vlan 10,20,30

Why this answer

Port-channel1 is configured as a routed (Layer 3) interface with no switchport and an IP address, while its member ports Gi0/1-4 are Layer 2 trunk ports. The summary flag R (Layer 3) on Po1 confirms it. The members and the port-channel must be the same type, so remove the IP address and return Port-channel1 to a Layer 2 switchport, then configure it as a trunk allowing VLANs 10, 20 and 30.

Changing the LACP mode, adding nonegotiate or using mode on does not change the Layer 3 versus Layer 2 mismatch.

Exam trap

The exam trap is that candidates often focus on LACP modes or trunk negotiation but overlook the Layer 2/Layer 3 mismatch between the port-channel interface and member interfaces. Always ensure the port-channel interface is configured as either Layer 2 or Layer 3 to match the member ports.

Why the other options are wrong

B

The specific factual error: The problem is a Layer 2/Layer 3 mismatch, not the LACP mode. Active mode is valid and commonly used.

C

The specific factual error: 'switchport nonegotiate' affects trunk negotiation, not EtherChannel bundling.

D

The specific factual error: The mode change does not fix the interface type mismatch; the port-channel must be Layer 2 to match the member ports.

92
Drag & Dropmedium

Drag and drop the following steps into the correct order to configure a Cisco Catalyst IOS-XE Layer 2 switch with the IPv4 management address 192.168.1.10/24 on VLAN 1, then enable the interface, then the IPv6 address 2001:db8:1::1/64, and finally the default gateway 192.168.1.1.

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

Enter global configuration mode, select interface vlan 1, assign the IPv4 address, enable the interface with no shutdown, assign the IPv6 address, then exit to global configuration mode because ip default-gateway is a global command, and configure the default gateway 192.168.1.1. The stem fixes the order of the IPv4 address, no shutdown and IPv6 address, while the default gateway must come after leaving the interface.

93
MCQhard

A user on VLAN 10 reports that they cannot ping the default gateway at 192.168.10.1 from their PC with IP 192.168.10.50/24. SW1 is a Layer 3 switch that is intended to be the default gateway for VLAN 10. The switch interface connecting to the PC is up/up, and the PC shows a valid IP configuration. Refer to the exhibit. What is the most likely cause of this connectivity failure?

A.Change the switchport mode to trunk to allow VLAN 10 traffic.
B.Configure an SVI for VLAN 10 with an IP address in the 192.168.10.0/24 subnet.
C.Change the PC's IP address to a different subnet, such as 192.168.20.0/24.
D.Recreate VLAN 10 and reassign the port to it.
AnswerB

The switch must provide a Layer 3 interface in VLAN 10 to serve as the default gateway for PCs in the 192.168.10.0/24 subnet. An SVI (interface vlan 10) with an IP address from that subnet creates a routable interface on the multilayer switch. This allows hosts in VLAN 10 to send traffic to other subnets, as their default gateway points to that SVI. Without this SVI, the PC has no gateway to route its traffic beyond its local segment.

Why this answer

VLAN 10 exists and Gi0/1 is correctly an access port in VLAN 10, but show ip interface brief on SW1 has no Vlan10 interface. The switch therefore has no Layer 3 interface with 192.168.10.1 for VLAN 10, so nothing answers ARP for the gateway address and the ping fails even though the access port is up/up. Creating interface vlan 10 with ip address 192.168.10.1 255.255.255.0 fixes it.

Exam trap

Cisco often tests the misconception that a VLAN alone provides Layer 3 connectivity, when in fact an SVI or a separate router-on-a-stick configuration is required for inter-VLAN routing and default gateway functionality.

Why the other options are wrong

A

A trunk port is used to carry multiple VLANs between switches, not to connect an end device like a PC. Configuring the switchport as trunk would break connectivity because the PC expects an access port.

C

Changing the PC's IP subnet would not resolve the issue because the PC would still need a default gateway on its new subnet. The root cause is the missing SVI on the switch, not the PC's IP address.

D

Recreating VLAN 10 and reassigning the port does not address the missing SVI. The VLAN already exists and the port is correctly assigned; the issue is at Layer 3, not Layer 2.

94
MCQmedium

A network engineer is troubleshooting a connectivity issue between Host A (192.168.10.10/24, VLAN 10, default gateway 192.168.10.1) and Host B (192.168.20.20/24, VLAN 20). R1 connects to the switch over a router-on-a-stick trunk on GigabitEthernet0/1, and the engineer captures traffic on that interface with embedded packet capture (EPC). The capture shows repeated ARP requests from Host A asking for 192.168.10.1 but no ARP replies. Refer to the exhibit. What is the most likely cause?

A.The router's interface is configured as an access port instead of a trunk.
B.The router's VLAN 10 subinterface has no IP address configured, so R1 does not own 192.168.10.1.
C.Host A has the wrong default gateway configured.
D.The router's interface has a duplex mismatch with the switch.
AnswerB

Gi0/1.10 has encapsulation dot1Q 10 but no ip address. R1 receives Host A's ARP requests for 192.168.10.1 but does not own that address, so it does not reply and Host A cannot reach its gateway.

Why this answer

Host A sends ARP requests for its default gateway, 192.168.10.1, because Host B is on a different subnet. The requests reach R1 on the trunk (they appear in the capture), but R1 never replies because subinterface GigabitEthernet0/1.10 has the correct VLAN 10 encapsulation but no IP address. Without 192.168.10.1 on that subinterface, R1 does not own the gateway address and cannot answer the ARP.

Configuring ip address 192.168.10.1 255.255.255.0 on Gi0/1.10 fixes it.

Exam trap

Hosts ARP for their default gateway, not for a host on another subnet. A router-on-a-stick subinterface needs both the dot1Q encapsulation and an IP address in that VLAN's subnet to answer ARP and route.

Why the other options are wrong

A

A router interface is not a switchport, and the capture shows the tagged requests arriving. The failure is the missing IP address.

C

The ARP target matches the intended gateway address for Host A's subnet.

D

Duplex mismatch causes CRC errors and collisions, but ARP requests would still be received and could be replied to. The capture shows clean ARP requests with no replies, pointing to a Layer 3 issue, not physical layer.

95
MCQhard

A switch port connected to a user PC should be placed in VLAN 20 and must not negotiate trunking. Which configuration is the most appropriate?

A.switchport mode access switchport access vlan 20
B.switchport mode trunk switchport trunk native vlan 20
C.switchport mode dynamic desirable switchport trunk allowed vlan 20
D.no switchport ip address 192.168.20.1 255.255.255.0
AnswerA

This is the correct configuration for a host port. `switchport mode access` unconditionally sets the interface as a nontrunking Layer 2 access port, disabling Dynamic Trunking Protocol (DTP) and preventing the port from becoming a trunk. The `switchport access vlan 20` command then statically assigns the port to VLAN 20, so the connected PC’s untagged frames are carried in that VLAN, exactly matching the requirement.

Why this answer

The most appropriate configuration is to force the interface into access mode and assign it to VLAN 20. In practical terms, a normal user-facing switch port is supposed to carry one VLAN only. There is no reason to rely on dynamic trunk negotiation for a desktop or laptop connection. Explicit access-port configuration is cleaner, more predictable, and safer.

This is a common switching best-practice question. The wrong answers usually leave room for unwanted trunking behavior or move the interface into a completely different role. The right answer combines the correct port role with the correct VLAN membership.

Exam trap

Avoid assuming 'auto' mode is always safe; it can lead to unintended trunking.

Why the other options are wrong

B

This configuration makes the port a trunk port, which is used to carry multiple VLANs between switches, not for a single user PC. The 'switchport trunk native vlan 20' command sets the native VLAN for untagged traffic on the trunk, but the port still actively negotiates trunking via DTP, violating the requirement to not negotiate trunking.

C

The 'switchport mode dynamic desirable' command actively attempts to form a trunk with the connected device via DTP, which contradicts the requirement to not negotiate trunking. Additionally, 'switchport trunk allowed vlan 20' only restricts which VLANs are allowed on the trunk, but the port is still in trunking mode, not an access port.

D

The 'no switchport' command converts the Layer 2 switch port into a Layer 3 routed interface, which cannot be assigned to a VLAN. This configuration is used for routing between VLANs or connecting to routers, not for connecting a user PC to a specific VLAN.

96
Drag & Dropmedium

Drag and drop the following steps into the correct order to configure a switch port for a PC behind an IP phone: select the port, make it an access port, then assign the data VLAN, then the voice VLAN, and finally enable PortFast.

Drag or tap steps into the slots.

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

Why this order

The correct order is: 1) Enter interface configuration mode, because all port-specific commands must be applied under the interface. 2) Set the port as an access port with 'switchport mode access'—a voice VLAN can only be assigned on an access port. 3) Assign the data VLAN with 'switchport access vlan' to ensure proper Layer 2 forwarding for data traffic. 4) Assign the voice VLAN with 'switchport voice vlan' so the IP phone's voice frames are tagged with the voice VLAN. 5) Enable PortFast with 'spanning-tree portfast' to immediately transition the port to forwarding, preventing DHCP timeouts for the phone and host.

97
MCQhard

Users in VLAN 60 on switch SW2 cannot reach the default gateway located on switch SW1. The trunk between SW1 and SW2 is operational and allows VLAN 60. What is the most likely reason for this issue?

A.VLAN 60 does not exist locally on SW2.
B.The native VLAN must be changed to 60 on both switches.
C.VLAN 60 is not allowed on the trunk link.
D.The default gateway must be configured as a loopback on SW2.
AnswerA

This is the most likely reason: SW2 has not been created with VLAN 60, so it does not have a spanning-tree instance or a switch virtual interface for that VLAN. Even if the trunk port with SW1 allows VLAN 60 and receives tagged frames, those frames are discarded because the VLAN is not present in SW2's VLAN database. Consequently, users in VLAN 60 cannot communicate through SW2, and no access port or SVI can be assigned to that VLAN.

Why this answer

VLAN 60 has not been created locally on SW2, even though the trunk can carry its traffic. A switch never processes VLAN traffic for a VLAN it doesn't know about; it discards tagged frames from the trunk destined for that VLAN and prevents access ports from assigning frames to it. (A) is correct. (B) is incorrect because native VLAN configuration only affects untagged frames—changing it to 60 is unnecessary for tagged VLAN 60 traffic. (C) is incorrect because the trunk is already configured to allow VLAN 60, so trunk filtering isn't the problem. (D) is incorrect because a default gateway is simply an IP address on a router or Layer 3 switch interface (like SVIs) and does not require a loopback on SW2.

Exam trap

Don't assume trunk configuration alone resolves VLAN issues; ensure VLANs exist on all relevant switches.

Why the other options are wrong

B

Native VLAN configuration does not affect tagged VLAN 60 traffic—native VLAN only matters for untagged frames.

C

The trunk is stated to allow VLAN 60, so VLAN filtering is not the problem; a student might misread the premise.

D

The default gateway resides on SW1, not SW2; configuring a loopback on SW2 does not create a gateway for VLAN 60.

98
PBQhard

You are connected to the switch MLS1 in a branch network. R1 is the DHCP server for VLAN 20 (192.168.20.0/24) and is connected to MLS1 Gi0/0, an access port in VLAN 20. Clients in VLAN 20 are not receiving IP addresses, and a rogue DHCP server has been detected on VLAN 20. On MLS1, enable DHCP snooping for VLAN 20, trust the port toward R1, rate-limit DHCP on the access port, and make sure MLS1 does not insert option 82 (R1 would ignore such requests). On R1, correct the pool (default-router 192.168.20.1, DNS 8.8.8.8) and exclude only the first 10 addresses. Verify the solution.

Network Topology
G0/0G0/0192.168.20.1/24G0/1192.168.20.0/24SiMLS1R1Clients

Hints

  • •On MLS1, DHCP snooping must be globally enabled and then applied to VLAN 20.
  • •The uplink to R1 must be trusted; access ports should have rate limiting to prevent DHCP starvation.
  • •On R1, the excluded-address range was too broad; only exclude the first 10 addresses. The default-router and DNS server were incorrect.
A.MLS1: ip dhcp snooping; ip dhcp snooping vlan 20; no ip dhcp snooping information option; Gi0/0 ip dhcp snooping trust; Gi0/1 ip dhcp snooping limit rate 10. R1: ip dhcp excluded-address 192.168.20.1 192.168.20.10; pool default-router 192.168.20.1 and dns-server 8.8.8.8.
B.MLS1: ip dhcp snooping vlan 20; no ip dhcp snooping information option; Gi0/0 ip dhcp snooping trust; Gi0/1 ip dhcp snooping limit rate 10. R1: ip dhcp excluded-address 192.168.20.1 192.168.20.10; pool default-router 192.168.20.1 and dns-server 8.8.8.8.
C.MLS1: ip dhcp snooping; ip dhcp snooping vlan 20; no ip dhcp snooping information option; Gi0/0 ip dhcp snooping trust; Gi0/1 ip dhcp snooping limit rate 10. R1: ip dhcp excluded-address 192.168.20.1 192.168.20.254; pool default-router 192.168.20.1 and dns-server 8.8.8.8.
D.MLS1: ip dhcp snooping; ip dhcp snooping vlan 20; no ip dhcp snooping information option; Gi0/1 ip dhcp snooping trust; Gi0/0 ip dhcp snooping limit rate 10. R1: ip dhcp excluded-address 192.168.20.1 192.168.20.10; pool default-router 192.168.20.1 and dns-server 8.8.8.8.
AnswerA
solution
! R1
configure terminal
no ip dhcp excluded-address 192.168.20.1 192.168.20.254
ip dhcp excluded-address 192.168.20.1 192.168.20.10
ip dhcp pool VLAN20_POOL
default-router 192.168.20.1
dns-server 8.8.8.8
end

! MLS1
configure terminal
ip dhcp snooping
ip dhcp snooping vlan 20
no ip dhcp snooping information option
interface GigabitEthernet0/0
ip dhcp snooping trust
exit
interface GigabitEthernet0/1
ip dhcp snooping limit rate 10
end

Why this answer

R1 cannot serve clients because the excluded-address range covers all of 192.168.20.1-254 and the pool hands out the wrong default-router (192.168.10.1). On MLS1, DHCP snooping must be enabled globally and for VLAN 20; the port toward the legitimate server (Gi0/0) must be trusted so that server replies are forwarded and rogue-server replies on untrusted ports are dropped; the access port is rate-limited; and option 82 insertion is disabled because a router DHCP server ignores requests with option 82 when giaddr is 0.

Exam trap

Watch for three separate issues: DHCP pool misconfiguration (default-router, DNS, excluded range), DHCP snooping not enabled globally, and the need to set trust on the uplink. Candidates often forget the global 'ip dhcp snooping' command or misconfigure the excluded range.

Why the other options are wrong

B

DHCP snooping must be enabled globally.

C

Excluded range must be 192.168.20.1-192.168.20.10.

D

Trust belongs on the port toward R1.

99
MCQhard

Two routers, R1 and R2, have been configured with HSRP for VLAN 10 to provide default gateway redundancy to hosts. The virtual IP address is 192.168.10.1. After configuration, end hosts report inconsistent connectivity to the gateway, and a failover test reveals that when the active router is shut down, connectivity is lost. The network administrator checks the HSRP status on both routers. R1 shows HSRP group 10 as Active with no standby router, and R2 shows HSRP group 20 as Active with no standby router. What is the most likely cause of the redundancy failure?

A.R2 has a lower HSRP priority than R1, so it cannot become standby.
B.The HSRP group number is mismatched between R1 and R2.
C.The HSRP authentication strings do not match.
D.HSRP version 1 is used on R1 while version 2 is used on R2.
AnswerB

R1 is Active for group 10 and R2 is Active for group 20, both with virtual IP 192.168.10.1. Because the group numbers differ, the routers do not exchange hellos as part of the same virtual router, so each shows Standby unknown and neither can take over for the other. When the active router fails, no standby takes over, which matches the failover test.

Why this answer

HSRP requires all routers participating in the same virtual router to use the same group number. Because R1 is active for group 10 and R2 is active for group 20, neither router has a standby for its group. If the active router for a group fails, no standby router can take over, causing loss of connectivity.

Authentication mismatch or HSRP version mismatch would typically prevent routers from forming a neighbor relationship, but the provided status showing each router active in a different group points specifically to a group mismatch.

Exam trap

Cisco often tests the HSRP group number mismatch as a subtle cause of redundancy failure because candidates focus on priority or authentication and overlook the fundamental requirement that the group number must be identical on all routers in the same virtual router group.

Why the other options are wrong

A

The output shows R2 is Active in its own group (20); priority only affects role election within the same group. The real problem is separate group numbers.

C

With mismatched authentication, the state would not be Active. The exhibit clearly shows Active on both routers, so authentication is not the cause.

D

Version mismatch would not change the displayed group number; the group number discrepancy is the direct evidence shown in the exhibit.

100
MCQmedium

A port connected to an end-user PC should not send or expect VLAN tags from the endpoint. Which interface type is appropriate on the switch?

C.Routed port
D.Port-channel interface
AnswerA

An access port is correct because it carries traffic for exactly one VLAN and forwards untagged frames, which is exactly what a PC's NIC expects. PCs do not generate 802.1Q VLAN tags, so an access port's behavior of stripping and expecting untagged data aligns with the end-device's native Ethernet operation. Furthermore, access ports do not transmit DTP (Dynamic Trunking Protocol) frames, preventing any unwanted trunk negotiation toward the PC.

Why this answer

The appropriate interface type is an access port. In plain language, a normal user PC is expected to connect to one VLAN and send ordinary untagged Ethernet frames. The switch associates that traffic with the configured access VLAN.

This is different from a trunk, which is designed to carry multiple VLANs and commonly uses tagging to preserve VLAN identity across the link. Routed ports are Layer 3 interfaces used for routing between VLANs, not for attaching a single end-user PC. Port-channel interfaces aggregate multiple physical links for redundancy and bandwidth, but they do not determine whether VLAN tagging is used; the underlying port mode (access or trunk) still applies.

Therefore, access port is the only correct choice for an untagged, single-VLAN end-device connection.

Exam trap

Don't confuse the need for VLANs with the need for VLAN tagging. Access ports handle untagged traffic for single VLANs.

Why the other options are wrong

B

A trunk port is designed to carry traffic for multiple VLANs using 802.1Q tagging, which is not expected from a standard PC. Using a trunk port for a PC would cause the switch to expect tagged frames, leading to communication failures.

C

A routed port is a Layer 3 interface used for routing between VLANs or connecting to routers, not for connecting end-user PCs. It does not operate as a Layer 2 switchport and would not handle VLAN tagging as required.

D

A port-channel interface is a logical bundling of multiple physical links for increased bandwidth and redundancy, not a single connection to an end-user PC. It is used between switches or to servers, not for typical PC access.

101
PBQhard

You are connected to R1. Configure inter-VLAN routing on R1 using router-on-a-stick so that hosts in VLAN 10 (192.168.10.0/24) and VLAN 20 (192.168.20.0/24) can communicate. The switch SW1 is already configured with VLANs and trunking, but R1's current configuration prevents traffic. Identify and fix the issues.

Network Topology
G0/0trunkR1SW1

Hints

  • •The subinterfaces are administratively down because their parent interface is shut down.
  • •Enable the physical interface with 'no shutdown'; the subinterfaces follow the parent.
  • •Routing is enabled by default on a router, so 'ip routing' is not needed.
A.Enable the physical interface with the 'no shutdown' command on R1.
B.Change the encapsulation on the subinterfaces to use dot1Q with native VLAN 10 and 20 respectively.
C.Enable IP routing globally with the 'ip routing' command on R1.
D.Add 'no shutdown' to each subinterface and leave the physical interface shut down.
AnswerA
solution
! R1
interface GigabitEthernet0/0
no shutdown
exit
show interfaces trunk

Why this answer

The physical interface GigabitEthernet0/0 is administratively shut down, so both subinterfaces (VLAN 10 and VLAN 20) are administratively down and no connected routes exist. Subinterfaces are enabled by default and depend on the parent, so the fix is no shutdown on GigabitEthernet0/0. The encapsulation, subinterface IP addresses and routing are already correct, and a router has IP routing enabled by default.

Exam trap

A common mistake is overlooking that router-on-a-stick requires the physical interface to be administratively up, as subinterfaces cannot function independently.

Why the other options are wrong

B

Changing encapsulation is unnecessary because the subinterfaces already use the correct dot1Q encapsulation for VLANs 10 and 20.

C

The 'ip routing' command is already enabled by default on routers, and global routing is not the problem here.

D

Subinterfaces do not support a 'no shutdown' command; their operational state is determined solely by the physical interface.

102
MCQmedium

A network administrator is troubleshooting a Windows 10 workstation that cannot access the internet. The workstation has a 169.254.x.x IPv4 address, its network cable is connected, and the switch port shows up/up. The network uses a DHCP server for the user subnet, and other workstations connected to the same switch in the user VLAN get valid addresses. What is the most likely cause of this issue?

A.The workstation's DNS server settings are incorrect.
B.The workstation's switch port is assigned to a different VLAN than the other workstations, so its DHCP Discover broadcasts never reach the DHCP server.
C.The DHCP server has exhausted its address pool.
D.The workstation's default gateway is misconfigured.
AnswerB

DHCP Discover is a broadcast confined to the VLAN. With the link up and other workstations working, a port in the wrong VLAN is the most likely reason this one host gets no DHCPOFFER and falls back to APIPA (169.254.x.x).

Why this answer

A 169.254.x.x address is an APIPA (link-local) address that Windows assigns when it gets no reply to its DHCP Discover broadcasts. The cable and link are fine and other workstations in the user VLAN receive leases, so the DHCP server and pool are working. The most likely cause is that this workstation's switch port is assigned to a different VLAN than the other workstations, so its broadcasts never reach the DHCP server (or relay) for the user subnet.

Note that a truly unplugged cable would instead show 'Media disconnected' with no IP address.

Exam trap

APIPA means DHCP Discover broadcasts got no answer, not that the cable is unplugged (an unplugged cable shows 'Media disconnected'). With link up and other hosts working, suspect the access VLAN or DHCP reachability for that port.

Why the other options are wrong

A

Incorrect DNS settings prevent name resolution but do not affect IP address assignment. The workstation would still receive a valid IP from DHCP, not an APIPA address.

C

If the DHCP pool were exhausted, all workstations would fail to obtain addresses and use APIPA. The scenario states other workstations are working correctly, so pool exhaustion is not the cause.

D

A misconfigured default gateway would prevent internet access but the workstation would still receive a valid IP from DHCP. APIPA addresses are only assigned when DHCP fails entirely.

103
Drag & Dropmedium

Drag and drop the following steps into the correct order to configure inter-VLAN routing using a router-on-a-stick topology. Configure the switch first (VLANs, access ports, trunk), then the router.

Drag or tap steps into the slots.

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

Why this order

Router-on-a-stick starts on the switch: the VLANs must exist before ports can be assigned to them or the trunk can allow them, and the trunk toward the router carries the tagged VLANs. On the router, the physical interface is enabled without an IP address, then a subinterface is created for each VLAN with the matching dot1q encapsulation and an IP address that serves as the default gateway.

104
MCQhard

A trunk link has a native VLAN mismatch between two switches. What is the most likely result?

A.All VLANs except the native VLAN stop forwarding immediately.
B.Untagged frames can be interpreted as belonging to different VLANs on each switch.
C.The trunk automatically converts to an access port.
D.STP is disabled on the trunk until the mismatch is corrected.
AnswerB

With a native VLAN mismatch, each switch places untagged 802.1Q frames into its locally configured native VLAN. For example, if Switch A's native VLAN is 10 and Switch B's is 20, a single untagged frame will be associated with VLAN 10 on one side and VLAN 20 on the other, effectively crossing broadcast domains and potentially exposing traffic to the wrong VLAN. This misclassification can lead to security breaches, routing loops, or connectivity anomalies because VLAN membership is not preserved end-to-end.

Why this answer

Untagged traffic may be placed into different VLANs on each side of the trunk, causing traffic leakage or connectivity problems.

Exam trap

Be careful not to confuse native VLAN mismatches with issues that affect tagged traffic or automatic switch behavior.

Why the other options are wrong

A

A native VLAN mismatch does not cause all other VLANs to stop forwarding. The trunk continues to forward frames for all VLANs, but untagged frames (native VLAN) are miscommunicated.

C

A trunk port does not automatically convert to an access port due to a native VLAN mismatch. The trunk remains operational, but the native VLAN mismatch causes problems for untagged traffic.

D

STP continues to run normally on the trunk link despite a native VLAN mismatch. The mismatch does not disable STP; it only affects the handling of untagged frames.

105
MCQmedium

After a switch replacement, users in VLAN 30 cannot reach devices in other VLANs. The replacement switch has a trunk link to the distribution switch that shows as up/up. What is the most likely cause?

A.The native VLAN must be changed to 30
B.VLAN 30 is not permitted on the trunk link
C.The uplink should be configured as an access port
D.STP must be disabled on VLAN 30
AnswerB

The trunk allowed list controls which VLANs traverse the link, and without an explicit 'allowed vlan add 30' statement, frames belonging to VLAN 30 are discarded at the trunk. Because the access switch and distribution switch only carry permitted VLANs, VLAN 30 has no path to the rest of the network. This exactly matches the symptom that only VLAN 30 suffers while other VLANs work normally on the same uplink.

Why this answer

The trunk is up, but VLAN 30 is not allowed on it. Traffic from that VLAN never crosses the uplink, so inter-VLAN reachability fails for users in VLAN 30 even though the local access ports may still look fine.

Exam trap

Ensure you distinguish between management settings and VLAN configuration. Focus on trunk settings when inter-VLAN issues arise.

Why the other options are wrong

A

Changing the native VLAN to 30 would not resolve the issue because the native VLAN is used for untagged traffic on a trunk, and the problem is that VLAN 30 traffic is not being allowed at all. Additionally, native VLAN mismatch can cause connectivity issues, but it does not specifically prevent only VLAN 30 from reaching other VLANs.

C

Configuring the uplink as an access port would place it in a single VLAN, preventing traffic from multiple VLANs (including VLAN 30) from traversing the link. Since the switch needs to carry traffic for multiple VLANs, the uplink must remain a trunk port.

D

Disabling STP on VLAN 30 would be dangerous as it could cause bridging loops and network instability. Moreover, STP does not control whether a VLAN is allowed on a trunk; it only prevents loops. The issue is a missing VLAN in the trunk allowed list, not a spanning-tree problem.

106
MCQhard

Based on the exhibit, which configuration should be added to restore DHCP service for clients in VLAN 30?

A.ip helper-address 10.99.99.20 under interface Vlan30
B.switchport mode trunk under interface Vlan30
C.ip default-gateway 10.99.99.20 under interface Vlan30
D.spanning-tree portfast under interface Vlan30
AnswerA

The VLAN 30 SVI is the Layer 3 gateway for that subnet, so DHCP client broadcasts must be relayed as unicast to the server at 10.99.99.20. The ip helper-address command enables this relay function and is correctly placed on the SVI that receives the clients' requests. Without it, the broadcast would be dropped by the router.

Why this answer

The correct fix is to add an IP helper address pointing to the remote DHCP server on the Layer 3 interface for VLAN 30. In practical terms, the clients are sending DHCP discovery as a broadcast, and the server is on another subnet. The SVI for VLAN 30 is the local gateway that must relay those requests toward the server.

This is one of the most exam-realistic campus troubleshooting scenarios because it tests both subnet boundaries and the role of the local gateway interface.

Exam trap

A common exam trap is confusing the ip helper-address command with ip default-gateway or Layer 2 commands like switchport mode trunk. Candidates might incorrectly apply switchport commands to an SVI, which is a Layer 3 interface, or think setting ip default-gateway will relay DHCP requests. These mistakes cause DHCP broadcasts to fail reaching the remote server, leading to no IP address assignment for clients.

Understanding that ip helper-address is the DHCP relay mechanism on Layer 3 interfaces is critical to avoid this trap.

Why the other options are wrong

B

Incorrect. The command switchport mode trunk is a Layer 2 switchport configuration and cannot be applied to an SVI, which is a Layer 3 interface. This does not affect DHCP relay.

C

Incorrect. The ip default-gateway command sets the default gateway for management traffic on a Layer 2 device and does not relay DHCP broadcasts. It does not restore DHCP service for clients.

D

Incorrect. The spanning-tree portfast command is used on physical Layer 2 switchports to speed up port transitions and has no effect on DHCP relay or SVIs.

107
MCQmedium

A switch administrator enters the following commands on interface GigabitEthernet1/0/10: interface g1/0/10 switchport mode access switchport access vlan 30 spanning-tree portfast spanning-tree bpduguard enable A user connects a small managed switch to this port, and the access port immediately changes to an err-disabled state. Which feature caused the port to shut down?

C.Access VLAN 30 assignment
D.The interface being in access mode
AnswerB

Correct. BPDU Guard is correct because it is specifically designed to shut down an edge port that should not receive BPDUs. In plain terms, the switch sees evidence that another switch was attached and decides to protect the topology by disabling the port instead of allowing a possible loop or unexpected spanning-tree participation.

Why this answer

BPDU Guard is the feature that caused the shutdown. This question is really about separating two features that are often configured together on user-facing ports: PortFast and BPDU Guard. PortFast helps an edge port come up quickly, which is useful for PCs and phones.

BPDU Guard adds protection by watching for BPDUs on that same port. If a switch is connected where only an end device should exist, the newly connected switch may send BPDUs. The local switch interprets that as a topology risk and disables the port to protect the Layer 2 network.

The clues are the err-disabled state and the fact that another switch was connected. VLAN assignment and access mode are normal here and do not explain the shutdown.

Exam trap

Remember that BPDU Guard, not PortFast, causes a port to shut down when BPDUs are received. PortFast only affects port transition speed.

Why the other options are wrong

A

PortFast is a feature that allows a port to transition immediately to the forwarding state, bypassing the usual spanning-tree listening and learning phases. It does not cause a port to shut down or enter an err-disabled state; it only speeds up convergence for end-user devices.

C

Assigning an access VLAN (VLAN 30) simply places the port into a specific broadcast domain for user traffic. It has no mechanism to detect or react to BPDUs, and it does not cause a port to enter an err-disabled state. The port would remain operational regardless of the VLAN assignment.

D

Configuring a port as an access port is a standard practice for connecting end devices. It does not inherently cause any shutdown or err-disabled condition. The port remains up and forwarding traffic unless another feature, such as BPDU Guard, triggers a protective action.

108
MCQhard

A network technician is troubleshooting connectivity between two directly connected Cisco switches. Users on VLAN 10 connected to SwitchA report very slow access to resources behind SwitchB, with frequent timeouts. Both switch ports show up/up. The technician examines the interface output on both switches. Refer to the exhibit. What is the most likely cause, and what is the fix?

A.Replace the Ethernet cable because it is faulty.
B.Configure both interfaces with the same duplex and speed settings, either both auto-negotiating or both manually set to the same matching values (for example 100 Mb/s full duplex).
C.Issue the 'shutdown' and 'no shutdown' commands on the interface to recover from err-disabled state.
D.Check the VLAN configuration on SwitchA because the interface is administratively down.
AnswerB

SwitchA runs Half-duplex and SwitchB runs Full-duplex, so there is a duplex mismatch (late collisions on A, runts/CRC on B) while both ports stay up/up. Configure both interfaces with the same speed and duplex, either both auto or both manually set to matching values, to resolve it.

Why this answer

The two ends of the link disagree on duplex: SwitchA is running Half-duplex while SwitchB is running Full-duplex at 100 Mb/s. This is the classic result of one side being hard-coded (speed 100 and duplex full on SwitchB) while the other is left on auto, so SwitchA senses the speed but falls back to half duplex. The half-duplex side sees collisions and late collisions, and the full-duplex side sees runts, CRC and frame errors, producing slow performance even though both ports stay up/up.

The fix is to configure both ends the same: both auto, or both hard-coded to the same speed and duplex.

Exam trap

A duplex mismatch keeps the link up/up. Look for Half-duplex on one side and Full-duplex on the other, with late collisions on the half-duplex side and runts/CRC/frame errors on the full-duplex side.

Why the other options are wrong

A

The exhibit shows Half-duplex on SwitchA and Full-duplex on SwitchB, which is a configuration mismatch rather than a cable fault.

C

The ports are up/up, not err-disabled; the issue is a duplex mismatch.

D

Both interfaces are up/up and the counters indicate a duplex mismatch.

109
MCQhard

A network engineer notices that a newly connected switch-to-switch link is up, but traffic from multiple VLANs is not passing. When issuing the show interfaces trunk command, no trunk ports are listed. Both switch ports are configured with switchport mode dynamic auto. What is the most likely cause?

A.There is a native VLAN mismatch between the two switches.
B.The connecting cable is a straight-through Ethernet cable rather than a crossover cable.
C.One switch lacks a VLAN that exists on the other switch.
D.Both ports are set to dynamic auto, so neither switch initiates DTP negotiation.
AnswerD

In dynamic auto mode, a switch port passively waits for DTP negotiation requests. When both ends are dynamic auto, no side initiates the negotiation, so the ports default to access mode. This perfectly matches the symptom: the link is up, but no trunk appears under show interfaces trunk, and multi-VLAN traffic is not passing.

Why this answer

When both switch ports are configured with switchport mode dynamic auto, neither actively initiates Dynamic Trunking Protocol (DTP) negotiation. DTP dynamic auto ports wait for the other side to send DTP frames to form a trunk; since both sides are passive, the link remains in access mode and does not become a trunk, preventing traffic from multiple VLANs from passing.

Exam trap

Cisco often tests the subtle difference between dynamic auto (passive) and dynamic desirable (active) DTP modes, leading candidates to incorrectly assume that two dynamic auto ports will automatically form a trunk.

Why the other options are wrong

A

Confusing DTP trunk negotiation with the operational consequences of a native VLAN mismatch.

B

Assuming that a crossover cable is mandatory for switch-to-switch connections, ignoring auto-MDIX.

C

Mistaking the ability to forward traffic for a specific VLAN with the ability to negotiate a trunk.

110
MCQhard

Two switches, SW1 and SW2, are connected via a trunk link. Hosts in VLAN 50 on SW1 cannot communicate with hosts in VLAN 50 on SW2, while hosts in other VLANs communicate normally. What is the most likely cause?

A.VLAN 50 is not allowed on the trunk from SW1.
B.The native VLAN must be changed to 50 on both switches.
C.The trunk must be changed to an access port.
D.The switches must run PPP on the uplink.
AnswerA

The trunk between SW1 and SW2 has a configured allowed VLAN list that excludes VLAN 50; any frames tagged for that VLAN are dropped at the trunk interface. Because 802.1Q trunks only forward VLANs explicitly permitted in the `switchport trunk allowed vlan` list, the missing entry prevents VLAN 50 traffic from reaching SW2. This would cause clients in VLAN 50 to lose connectivity across the link.

Why this answer

The strongest explanation is that VLAN 50 is missing from the allowed VLAN list on one side of the trunk. In practical terms, the trunk is up and carrying other VLANs, so the problem is selective rather than total. When one VLAN is omitted from the allowed list, only that VLAN fails while others continue to work normally.

This is a high-value switching troubleshooting pattern because it rewards careful reading of operational output rather than generic trunk theory.

Exam trap

Be careful to distinguish between total trunk failures and selective VLAN issues. Check the allowed VLAN list on trunk links when only one VLAN is affected.

Why the other options are wrong

B

The native VLAN is used for untagged traffic on a trunk and does not affect the forwarding of tagged frames for other VLANs. Changing the native VLAN to 50 would not resolve the issue because VLAN 50 frames are still tagged and require inclusion in the allowed VLAN list.

C

An access port can only carry a single VLAN, so changing the trunk to an access port would prevent the link from carrying multiple VLANs, including VLAN 50. The link is intended to carry multiple VLANs, so a trunk is required.

D

PPP (Point-to-Point Protocol) is a WAN protocol used on serial links, not on Ethernet trunks. Ethernet trunks use 802.1Q or ISL encapsulation, and PPP has no relevance to VLAN trunking issues.

111
MCQhard

A phone and PC share one switchport. The phone works, but the PC cannot reach its normal data resources. The switchport voice VLAN is configured, and the access VLAN is incorrect. Which explanation is strongest?

A.The PC is likely in the wrong data VLAN even though the phone still uses the correct voice VLAN.
B.If the phone works, the PC must also work because both use the same VLAN always.
C.The issue must be BGP because phones cannot use VLANs.
D.The access VLAN becomes irrelevant whenever a voice VLAN is configured.
AnswerA

The PC is likely in the wrong data VLAN even though the phone still uses the correct voice VLAN because a single switchport can serve two logical VLANs simultaneously: an access VLAN for untagged data traffic and a voice VLAN for tagged voice traffic. In a typical Cisco IP phone deployment, the phone tags its voice frames with the voice VLAN and passes the PC's untagged frames onto the access VLAN, so the phone's operation only proves the voice VLAN path is healthy. The PC's connectivity depends entirely on the access VLAN configuration—if the access VLAN ID, subnet, or DHCP scope is misconfigured, the PC will fail while the phone continues to work. Thus, the symptom directly points to a data VLAN issue, not a voice VLAN problem.

Why this answer

The switchport is configured with a voice VLAN for the phone and an access VLAN for the PC. If the access VLAN is incorrect, the PC will be placed in the wrong data VLAN, preventing it from reaching its normal data resources, while the phone continues to operate correctly on its designated voice VLAN. This is a common misconfiguration where the data VLAN ID does not match the network segment the PC expects.

Exam trap

Cisco often tests the misconception that a working phone implies the PC is also correctly configured, but the trap here is that voice and data VLANs are independent, so a misconfigured access VLAN only affects the PC.

Why the other options are wrong

B

This statement is incorrect because the phone and PC can operate on different VLANs on the same port. The phone uses the voice VLAN, while the PC uses the access (data) VLAN. They are not required to use the same VLAN, and misconfiguration of the access VLAN can cause the PC to fail while the phone works.

C

BGP (Border Gateway Protocol) is a routing protocol used between autonomous systems, not related to VLAN configuration on a switchport. The issue described is about Layer 2 VLAN assignment, not Layer 3 routing. BGP has no role in this scenario.

D

The access VLAN remains relevant even when a voice VLAN is configured. The access VLAN is used for the PC's data traffic, while the voice VLAN is used for the phone's traffic. If the access VLAN is incorrect, the PC will not be able to communicate on the correct data network.

112
MCQhard

Users in VLAN 10 report that traffic takes an unexpected path and some uplinks are idle. The design calls for distribution switch Dist1 to be the Rapid PVST+ root bridge for VLAN 10 (priority 4096). An administrator runs the command shown in the exhibit on access switch SwitchA, which has uplinks Gi0/1 and Gi0/2 to the distribution layer. Based on the output, what is the most appropriate next step?

A.Change the port type of Gi0/2 to trunk to allow multiple VLANs.
B.Configure spanning-tree portfast on Gi0/2 to speed up convergence.
C.Check the spanning-tree priority on other switches to ensure the intended root bridge has the lowest priority for VLAN 10.
D.Enable BPDU guard on Gi0/2 to prevent unauthorized switches from affecting the network.
AnswerC

Correct. The exhibit shows the root has priority 24586, not the intended 4096, so the intended root (Dist1) is not winning. Check the VLAN 10 priorities on the other switches, identify the switch with MAC 00aa.bbcc.ddee, and lower Dist1's priority.

Why this answer

SwitchA is not the root (its bridge priority 32778 is higher than the root priority 24586), so a blocked alternate port is normal behavior. The real finding is the Root ID: the elected root has priority 24586 (24576 + VLAN 10), not 4096. Dist1 was meant to win with priority 4096, so it is either misconfigured (for example still at the default) or the VLAN 10 root is some other switch with a lower bridge ID.

The correct action is to check the spanning-tree priority on the other switches, find which switch owns 00aa.bbcc.ddee, and set Dist1 to a lower priority (for example spanning-tree vlan 10 priority 4096 or root primary) so it becomes the root for VLAN 10.

Exam trap

Candidates see a port in the blocking (Altn BLK) state and blame the port or its configuration. A blocked alternate port on a non-root switch is expected; the thing to read is the Root ID section to see which bridge is actually root and whether it is the intended one.

Why the other options are wrong

A

Changing the port type to trunk does not affect root bridge election or port roles. The Altn BLK state is a normal result of the STP topology on a non-root switch.

B

PortFast is for edge ports and does not change the root election; applying it to an uplink is unsafe.

D

BPDU guard protects edge ports from rogue switches; it does not change root election and would err-disable a legitimate uplink.

113
MCQmedium

SW1 is the root bridge for VLAN 10. A user switch receives a BPDU on an access port connected to a desk-side unmanaged switch. What should happen if BPDU Guard is enabled on that port?

A.The port transitions to forwarding more quickly
B.The port is moved to err-disabled state
C.The switch elects a new root bridge
D.The port becomes a trunk automatically
AnswerB

When BPDU Guard is enabled on a PortFast edge access port, receiving any BPDU is considered a violation because a legitimate end host should never generate BPDUs. The switch immediately places the port into the err-disabled state, effectively shutting it down to prevent a rogue switch from participating in VLAN 10 spanning tree. This protects the root bridge's topology by blocking the unauthorized device at the access layer.

Why this answer

BPDU Guard is designed to protect edge ports. If a BPDU is received on a PortFast access port, the switch places the interface into the err-disabled state to stop a potential Layer 2 loop or rogue switch.

Exam trap

Remember that BPDU Guard actively disables ports, it doesn't just log or ignore BPDUs.

Why the other options are wrong

A

PortFast allows a port to transition to forwarding immediately upon link up, but it does not react to BPDU reception. BPDU Guard is a separate feature that disables the port upon receiving a BPDU, not accelerate forwarding.

C

Receiving a BPDU on a single edge port does not trigger a root bridge election. Root bridge election is based on bridge ID comparison across the entire spanning-tree domain, not on a single BPDU on a port.

D

BPDU Guard does not change the port mode; it only reacts to BPDU reception by disabling the port. Port mode (access or trunk) is configured separately and is not affected by STP protection features.

114
PBQhard

You are connected to R1. Hosts in VLAN 10, which connect through Switch1, report severe packet loss and very slow transfers to and through R1. R1's GigabitEthernet0/0 connects to Switch1 port Gi0/1. You can configure only R1. Identify the root cause from the exhibit and apply the fix on R1.

Network Topology
G0/0192.168.1.1/30Gi0/1linkGi0/1Switch1R1Hosts in VLAN 10

Hints

  • •Input errors with CRC and frame errors on an up/up link suggest a duplex mismatch.
  • •Compare R1's hard-coded duplex with the a-half value negotiated on Switch1.
  • •Return both speed and duplex to auto with the auto keywords.
A.Configure 'duplex auto' and 'speed auto' under interface GigabitEthernet0/0 to restore auto-negotiation.
B.Replace the cable between R1 and Switch1 to remove the CRC errors.
C.Configure 'speed 10' under interface GigabitEthernet0/0 to slow the link and reduce errors.
D.Clear the interface counters on GigabitEthernet0/0 without changing any configuration.
AnswerA
solution
! R1
interface GigabitEthernet0/0
duplex auto
speed auto

Why this answer

R1's Gi0/0 is hard-coded to speed 100 and duplex full, so it no longer auto-negotiates. Switch1 is auto-negotiating, detects 100 Mb/s through parallel detection but falls back to half duplex (a-half, a-100). The result is a duplex mismatch: R1, the full-duplex side, accumulates CRC and frame errors because the half-duplex side transmits while R1 is sending.

The fix is to restore auto-negotiation on R1 with duplex auto and speed auto so both ends negotiate full duplex.

Exam trap

The exam trap is that candidates often focus on speed mismatches or clearing counters, but the real issue is duplex mismatch. Remember that on GigabitEthernet interfaces, auto-negotiation is the default and recommended setting; static duplex/speed settings can cause mismatches and errors.

Why the other options are wrong

B

A cable replacement does not fix a configuration-based duplex mismatch.

C

Changing the speed does not resolve the duplex mismatch.

D

The specific factual error is that clearing counters is a diagnostic step, not a fix. The root cause (duplex mismatch) remains unaddressed.

115
MCQhard

Based on the exhibit, why are clients in VLAN 70 failing to resolve hostnames even though they can reach remote IP addresses?

A.The clients are missing valid DNS server information.
B.The default gateway must be removed from the DHCP scope.
C.The clients must use PPP before DNS works.
D.The VLAN must be converted to the native VLAN on all trunks.
AnswerA

The DHCP scope assigns IP configuration but does not include Option 6 (DNS server), so clients receive no resolver address. When a user pings a hostname, the client cannot query a DNS server, causing resolution failure; direct IP access works because no DNS is required. This exactly matches the exhibited symptom of IP connectivity succeeding while hostname-based access fails.

Why this answer

The strongest explanation is that the clients are missing valid DNS server information. In practical terms, successful reachability to remote IP addresses proves that Layer 3 forwarding is working. The failure occurs only when a hostname is used, which points to a naming service problem rather than a general connectivity problem. The DHCP scope shown provides an address and default gateway, but no DNS server option is defined.

This is a very realistic IP-services troubleshooting pattern because the network path works while application usability still fails.

Exam trap

A frequent exam trap is to mistake the inability to resolve hostnames as a routing or VLAN trunking problem. Candidates might incorrectly believe that removing the default gateway or converting the VLAN to the native VLAN on trunks will resolve the issue. However, these options do not address DNS resolution, which is an application-layer service independent of Layer 3 forwarding.

The trap arises because clients can reach remote IP addresses, misleading candidates to focus on routing or VLAN configuration rather than missing DNS server information in the DHCP scope.

Why the other options are wrong

B

Removing the default gateway from the DHCP scope is incorrect because the default gateway is essential for routing traffic outside the local VLAN. Its presence does not cause hostname resolution failures.

C

The suggestion that clients must use PPP before DNS works is incorrect because PPP is unrelated to DNS resolution in a typical VLAN and DHCP environment. DNS operates independently of PPP.

D

Converting the VLAN to the native VLAN on all trunks does not affect DNS resolution. This option addresses Layer 2 trunking issues, which are unrelated to the hostname resolution problem described.

116
Matchingmedium

Drag and drop the VLAN/trunking commands and terms on the left to their correct descriptions or functions on the right.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Enables 802.1Q trunking on a switch interface

Assigns an access port to VLAN 10

VLAN that carries untagged traffic on a trunk link; default is VLAN 1

Changes the native VLAN on a trunk to VLAN 99

Uses subinterfaces on a single router interface to route between VLANs

Why these pairings

These pairings match common VLAN/trunking commands and terms to their correct descriptions.

Exam trap

Do not confuse the commands for access and trunk ports. Remember that 'switchport mode access' places the port in access mode, while 'switchport mode trunk' places it in trunk mode. Also, the native VLAN and VLAN 1 are related to trunking and default settings, not to the configuration of an access port.

117
PBQhard

You are connected to SW1 via the console. SW1 is a Layer 2 switch with two links to SW2 configured as an EtherChannel using LACP. The EtherChannel is not coming up. Interface G0/2 was accidentally configured as an access port in VLAN 10, while G0/1 is configured as a trunk. The administrator wants to use LACP to bundle the links. Troubleshoot and fix the configuration to bring up the EtherChannel.

Hints

  • •All interfaces in an EtherChannel must have identical configuration.
  • •Compare the switchport mode of G0/1 and G0/2.
  • •Return G0/2 to the same mode as G0/1.
A.Change interface G0/2 to trunk mode and ensure both interfaces have the same allowed VLAN list.
B.Change interface G0/1 to access VLAN 10 to match G0/2.
C.Remove only the 'switchport access vlan 10' command from G0/2 and leave it in access mode.
D.Change the EtherChannel mode from LACP to PAgP on both switches.
AnswerA
solution
! SW1
interface GigabitEthernet0/2
no switchport access vlan 10
switchport mode trunk

Why this answer

All member ports of an EtherChannel must have identical Layer 2 configuration (mode, allowed VLANs, native VLAN). G0/1 is a trunk and G0/2 is an access port in VLAN 10, so G0/2 is inconsistent with the bundle and is suspended. Remove the access VLAN from G0/2 and configure it as a trunk like G0/1 (and keep the same allowed VLAN list).

Then show etherchannel summary should show Po1 (SU) with both ports bundled (P).

Exam trap

200-301 often tests EtherChannel configuration requirements; candidates may focus on the protocol mode but overlook the need for matching trunk/access and VLAN configurations.

Why the other options are wrong

B

The specific factual error is that changing G0/1 to access VLAN 10 would not resolve the mismatch if the intended configuration is trunking. It would only create a different mismatch if the other side expects trunking.

C

G0/2 would still be an access port, unlike the trunk G0/1.

D

The specific factual error is that the protocol does not affect the requirement for consistent interface configurations. Both LACP and PAgP require identical VLAN and trunk settings on all member ports.

118
MCQhard

SW2 receives the following STP details for VLAN 10: The root bridge ID is 32778:0011.1111.1111 (SW1), and SW2's bridge ID is 32778:00aa.aaaa.aaaa. Its interface Gi0/1 has a path cost of 4 to the root, while Gi0/2 has a path cost of 19. Based on this information, which statement is correct?

A.SW2 is the root bridge for VLAN 10.
B.Gi0/1 on SW2 is the root port.
C.All SW2 ports in VLAN 10 must be designated ports.
D.STP is disabled because the priorities are equal.
AnswerB

Gi0/1 is the root port because STP selects the port with the lowest root path cost to reach the root bridge, and the received BPDU lists the root as reachable through Port 1. On SW2, Port 1 maps to Gi0/1, so that interface assumes the root port role. A root port is the non-root switch's closest path to the root, and it remains in forwarding state.

Why this answer

The root bridge has the lowest bridge ID. SW1 is the root because its bridge ID is lower than SW2's local bridge ID. On a non-root switch, the port with the best path toward the root becomes the root port, so Gi0/1 is the root port here.

Exam trap

A common exam trap is to incorrectly conclude that STP is disabled when bridge priorities are equal. Candidates may mistakenly believe that equal priorities cause STP to fail or not elect a root bridge. However, STP always elects a root bridge by comparing the MAC addresses as a tiebreaker when priorities match.

Another trap is assuming all ports on a non-root switch must be designated ports, ignoring the existence of a root port that leads toward the root bridge. Misreading the root port can lead to incorrect answers about port roles and network topology.

Why the other options are wrong

A

This option is incorrect because the root bridge ID shown in the STP details differs from SW2's local bridge ID, indicating SW2 is not the root bridge for VLAN 10.

C

This option is wrong since a non-root switch does not have all ports as designated ports; it must have one root port and may have other ports as designated or blocked.

D

This is incorrect because equal priorities do not disable STP; the protocol uses the MAC address portion of the bridge ID to break ties and continue operation.

119
PBQhard

You are connected to SW1 via the console. SW1 is a Layer 2 switch connected to two other switches (SW2 and SW3) via redundant links. All switches run IEEE 802.1D-based spanning tree (PVST+). The network administrator wants SW1 to become the root bridge for VLAN 1. Currently, the root bridge is SW2. Configure SW1 to achieve this and ensure that port G0/1, which connects to an end device, immediately transitions to forwarding state upon link up and is placed in err-disabled state if a BPDU is received on it (BPDU Guard).

Network Topology
G0/1 to PCSW2SW1SW3

Hints

  • •The 'root primary' macro sets the priority lower than any other switch.
  • •PortFast allows a port to skip listening/learning states.
  • •BPDU Guard err-disables the port if a BPDU is received.
A.Configure 'spanning-tree vlan 1 root primary' globally, and on interface G0/1 configure 'spanning-tree portfast' and 'spanning-tree bpduguard enable'.
B.Configure 'spanning-tree vlan 1 priority 4096' globally, and on interface G0/1 configure 'spanning-tree portfast' and 'spanning-tree guard root'.
C.Configure 'spanning-tree vlan 1 root secondary' globally, and on interface G0/1 configure 'spanning-tree portfast' and 'spanning-tree bpduguard enable'.
D.Configure 'spanning-tree vlan 1 priority 32768' globally, and on interface G0/1 configure 'spanning-tree portfast' and 'spanning-tree bpdufilter enable'.
AnswerA
solution
! SW1
spanning-tree vlan 1 root primary
interface GigabitEthernet0/1
spanning-tree portfast
spanning-tree bpduguard enable

Why this answer

The spanning-tree vlan 1 root primary command lowers the bridge priority for VLAN 1 (to 24576, or lower than the current root if needed) so SW1 becomes root. PortFast on G0/1 lets the access port skip the listening and learning states, and BPDU Guard (spanning-tree bpduguard enable) err-disables the port if a BPDU is received, which protects against rogue switches. Root guard (option B) and BPDU filter (option D) do not do this, root secondary (C) does not make SW1 the root, and priority 32768 is the default.

Exam trap

Do not confuse 'root primary' with 'root secondary' or manual priority settings. Also, remember that BPDU Guard is for access port security, while Root Guard protects the root bridge position. BPDU Filter suppresses BPDUs and is not a security feature.

Why the other options are wrong

B

The specific factual error: 'spanning-tree guard root' is a root guard feature, not BPDU guard. Also, manually setting priority to 4096 may not guarantee root if another switch has lower priority.

C

root secondary sets a priority of 28672, which is a backup-root value; it makes SW1 root only if the current root fails or has a higher priority, and it is not the primary-root macro the task requires.

D

The specific factual error: priority 32768 is default and does not change root status. BPDU filter is not a security feature against BPDU attacks; it suppresses BPDUs entirely.

120
MCQmedium

Exhibit: PCs in VLAN 20 are not receiving addresses from a DHCP server in another subnet. The switch SVI for VLAN 20 is up, and routing is working. Which configuration is most likely missing on the gateway for VLAN 20?

A.ip default-gateway 10.20.20.1
B.ip helper-address 10.99.99.10
C.switchport trunk allowed vlan 20
D.spanning-tree portfast default
AnswerB

DHCP relies on broadcast discovery, and broadcasts do not cross Layer 3 boundaries. The PCs in VLAN 20 cannot reach the DHCP server on a different subnet unless the VLAN 20 SVI has ip helper-address 10.99.99.10 configured. That command converts the client broadcast into a unicast relayed to the server, while also inserting the SVI IP as the giaddr so the server can scope an appropriate address. Therefore, this is the missing configuration.

Why this answer

DHCP Discover messages are broadcasts and do not cross routers by default. An ip helper-address on the client gateway interface relays those requests to a remote DHCP server.

Exam trap

A frequent exam trap is selecting the ip default-gateway command as the solution for DHCP relay issues. This command only applies to Layer 2 switches for their own management traffic and does not forward DHCP broadcasts across routed interfaces. Candidates may also mistakenly focus on VLAN trunking or spanning-tree settings, which do not affect DHCP relay functionality.

The key is to recognize that DHCP broadcasts must be explicitly forwarded by the router or Layer 3 switch interface using ip helper-address to reach a DHCP server in another subnet.

Why the other options are wrong

A

The ip default-gateway command configures the default gateway for a Layer 2 switch’s management interface and does not forward DHCP broadcasts. Since the question involves DHCP relay across routed VLANs, this command is irrelevant.

C

The switchport trunk allowed vlan 20 command controls VLAN traffic allowed on a trunk link but does not influence DHCP relay or routing between VLANs. The issue is DHCP relay, not VLAN trunk configuration.

D

The spanning-tree portfast default command enables PortFast on switch ports to speed up STP convergence and does not affect DHCP relay or routing. It is unrelated to the problem of clients not receiving DHCP addresses.

121
MCQmedium

A phone and a PC are attached to the same switchport. The intended data VLAN is VLAN 10, and the phone uses voice VLAN 20. The switchport currently has `switchport voice vlan 20` configured. The phone works, but the PC cannot reach the data network. Which command is most likely missing?

A.switchport mode dynamic auto
B.switchport voice vlan 20
C.switchport access vlan 10
D.spanning-tree guard root
AnswerC

The PC fails to reach the network because it is untagged on the access port while the switchport is likely in its default VLAN 1 or a mismatched VLAN. Issuing 'switchport access vlan 10' explicitly assigns the data VLAN to the port, ensuring the PC's traffic is placed in the correct Layer 2 domain. The phone can still tag its voice traffic with VLAN 20 via the voice VLAN feature, but the access VLAN governs the untagged PC traffic.

Why this answer

When a Cisco IP phone and a PC share one port, the switchport often needs both a data VLAN and a voice VLAN. If the voice VLAN exists but the data access VLAN is wrong or missing, the phone can work while the PC fails.

Exam trap

Ensure both data and voice VLANs are configured when devices share a port. Don't confuse duplex or trunk settings with VLAN issues.

Why the other options are wrong

A

The phone works but the PC cannot reach the data network, indicating the PC is not in the correct VLAN. 'switchport mode dynamic auto' sets the port to negotiate trunking via DTP, which does not assign a data VLAN to the PC.

B

The PC cannot reach the data network because the switchport is likely configured as a voice VLAN only, but the data VLAN (access VLAN) is missing. Option B configures the voice VLAN, which is correct for the phone, but does not set the access VLAN for the PC.

D

The issue is that the PC cannot reach the data network, which is typically configured via the access VLAN. Spanning-tree guard root is unrelated to VLAN assignment; it prevents a switch from becoming the root bridge, not connectivity issues on a specific VLAN.

122
MCQmedium

A network administrator is configuring a Cisco IOS switch port that connects to an IP phone and a PC daisy-chained behind the phone. The administrator wants the PC's data traffic to be untagged on VLAN 20, and the phone's voice traffic to be tagged with VLAN 30. The phone is already configured to use VLAN 30 for voice. Which configuration on the switch port will accomplish this?

A.switchport mode trunk switchport trunk native vlan 20 switchport trunk allowed vlan 30
B.switchport mode trunk switchport trunk native vlan 30 switchport trunk allowed vlan 20
C.switchport mode access switchport access vlan 30 switchport voice vlan 20
D.switchport mode access switchport access vlan 20 switchport voice vlan 30
AnswerD

This configuration sets the port as an access port for data VLAN 20 and uses the voice VLAN 30 for tagged voice traffic. The phone will receive untagged data frames on VLAN 20 and will tag its voice frames with VLAN 30. This is the standard Cisco configuration for a port connecting to an IP phone with a PC behind it.

Why this answer

The correct configuration uses an access port for data VLAN 20 and a voice VLAN 30. This allows the PC to send untagged data frames that are assigned to VLAN 20, while the IP phone tags its voice frames with VLAN 30. This is the standard and recommended approach for connecting an IP phone and PC to a single switch port.

Exam trap

The trap here is confusing the voice VLAN and data VLAN assignments, or incorrectly using a trunk port when an access port with voice VLAN is sufficient.

123
Multi-Selecthard

A switch port is configured with DHCP snooping trust on the uplink toward the legitimate DHCP server, and DHCP snooping is enabled on the user VLAN. A user connects a rogue DHCP server to an untrusted access port. Which two statements describe what DHCP snooping does in this situation? (Choose two.)

Select 2 answers
A.DHCP server messages received on the untrusted access port are dropped.
B.The access port is automatically converted to a trusted port after the first DHCP packet is seen.
C.The switch disables the entire VLAN and places it in err-disabled state.
D.The rogue server's MAC address is added to the snooping binding table as a trusted entry.
E.Client DHCP messages received on the untrusted access port are still forwarded toward the trusted uplink.
AnswersA, E

DHCP snooping classifies ports as trusted or untrusted. Server-originated messages such as OFFER and ACK arriving on an untrusted port are discarded, which prevents a rogue server on an access port from handing out addresses. This is the core protection the feature provides in this scenario.

Why this answer

DHCP snooping builds a binding table from legitimate client transactions and blocks server messages on untrusted ports. Client messages on untrusted access ports are permitted and forwarded uplink, while rogue server offers on those same ports are discarded. This combination stops the rogue server without disrupting normal client DHCP behavior.

Exam trap

The trap here is assuming DHCP snooping blocks all DHCP traffic on untrusted ports, when it actually blocks only server-originated messages and still permits client requests.

124
MCQhard

Two switches are connected using four Gigabit Ethernet interfaces configured as an EtherChannel with LACP. The network administrator notices that only two of the four interfaces are active in the port-channel, and the other two are in a suspended state. Upon further investigation, the administrator finds that the two inactive interfaces correspond to remote interfaces that are configured with the 'on' mode, while the active ones correspond to remote interfaces configured with LACP active/passive. The administrator also verifies that all local interfaces have the same speed, duplex, and VLAN. What is the most likely cause of the suspended interfaces?

A.The interfaces are in err-disabled state due to a spanning-tree loop.
B.The remote switch interfaces corresponding to the suspended local interfaces are configured with the 'on' mode instead of 'active' or 'passive' for LACP.
C.The port-channel interface is shutdown.
D.There is a mismatch in the allowed VLANs on the member interfaces.
AnswerB

When one switch has LACP active/passive and the other has 'on' (static), LACP negotiation fails, and the ports become suspended. Changing the remote switch to 'active' or 'passive' allows LACP to negotiate and bundle the ports.

Why this answer

LACP requires both ends of a link to be configured in either 'active' or 'passive' mode to negotiate an EtherChannel. If some remote interfaces are set to 'on' mode (static EtherChannel), LACP negotiation fails on those links, causing the corresponding local LACP-enabled interfaces to remain in a suspended state. The local switch detects that LACP PDUs are not received on those interfaces and suspends them to prevent misconfiguration.

The other two interfaces with correctly configured remote peers form the EtherChannel successfully.

Exam trap

Cisco often tests the misconception that all interfaces must match in speed, duplex, and VLAN to form an EtherChannel, but the trap here is that the LACP mode mismatch (active/passive vs. on) is the specific cause of suspended interfaces even when other parameters are consistent.

Why the other options are wrong

A

The exhibit shows the ports as suspended, not err-disabled. Spanning-tree loops typically cause err-disable, not suspension.

C

The port-channel is up (U), so it is not shutdown.

D

The scenario explicitly states that all interfaces are configured with the same VLAN, so this is not the cause.

125
PBQmedium

You are connected to SW1 via console. SW1 is a Layer 2 switch connected to two other switches (SW2 and SW3) via trunk links. The network administrator wants to ensure that SW1 becomes the root bridge for VLAN 10 and VLAN 20. Currently, SW2 is the root for both VLANs. Configure SW1 to become the root bridge for these VLANs using the Cisco-recommended macro STP commands.

Network Topology
trunktrunkSW2SW1SW3

Hints

  • •Use the 'root primary' macro to set the bridge priority to 24576.
  • •Ensure VLANs 10 and 20 exist on SW1.
A.spanning-tree vlan 10 root primary; spanning-tree vlan 20 root primary
B.spanning-tree vlan 10 root secondary; spanning-tree vlan 20 root secondary
C.spanning-tree vlan 10 priority 4096; spanning-tree vlan 20 priority 4096
D.spanning-tree vlan 10 root; spanning-tree vlan 20 root
AnswerA
solution
! SW1
spanning-tree vlan 10 root primary
spanning-tree vlan 20 root primary

Why this answer

The spanning-tree vlan <vlan> root primary macro lowers the bridge priority (to 24576 when the current root has the default 32768) so the switch becomes root for that VLAN, and it is the Cisco-recommended method the stem asks for. Option B (root secondary) sets a backup priority of 28672 and does not make SW1 the root. Option C sets a static priority and is not the macro.

Option D is not valid syntax.

Exam trap

Do not confuse 'root primary' with 'root secondary'. 'root primary' sets priority to 24576 to become root; 'root secondary' sets priority to 28672 to act as backup. Also, remember that the 'root' keyword must be followed by 'primary' or 'secondary'.

Why the other options are wrong

B

Option B uses 'root secondary', which sets the priority to 28672, making SW1 a backup root, not the primary root bridge.

C

Option C uses a static priority assignment of 4096, which would also make SW1 root, but the question expects the Cisco-recommended macro command 'root primary'.

D

Option D uses incomplete syntax 'spanning-tree vlan 10 root' without 'primary' or 'secondary', which is invalid.

126
PBQhard

You are connected to Switch1. Configure an LACP EtherChannel between Switch1 and Switch2 using interfaces GigabitEthernet0/1 and GigabitEthernet0/2. The channel must be in active mode on both sides, and the port-channel interface must have VLAN 10 as the access VLAN. The current configuration has a speed/duplex mismatch and inconsistent VLAN assignments preventing the channel from forming. Verify the channel is up using 'show etherchannel summary'.

Network Topology
Gi0/1Gi0/1EtherChannelSwitch1Switch2

Hints

  • •Check that all member interfaces have the same speed and duplex settings.
  • •Ensure all interfaces (including the port-channel) are in the same VLAN.
  • •Both sides must use LACP active mode for the channel to form.
A.Set speed auto on Gi0/1 and Gi0/2, set duplex auto on both, change access VLAN on Gi0/2 to 10, change access VLAN on Port-channel1 to 10, and set channel-group mode active on both interfaces.
B.Set speed 1000 on Gi0/1, set duplex full on Gi0/1, change access VLAN on Gi0/1 to 20, change access VLAN on Port-channel1 to 20, and set channel-group mode passive on both interfaces.
C.Set speed 100 on Gi0/2, set duplex half on Gi0/2, change access VLAN on Gi0/1 to 20, change access VLAN on Port-channel1 to 20, and set channel-group mode desirable on both interfaces.
D.Set speed auto and duplex auto on both interfaces and channel-group mode active on both, but leave Gi0/2 in VLAN 20 and Port-channel1 in VLAN 1.
AnswerA
solution
! Switch1
interface gigabitethernet0/1
speed auto
duplex auto
channel-group 1 mode active
interface gigabitethernet0/2
switchport access vlan 10
channel-group 1 mode active
interface port-channel 1
switchport access vlan 10

Why this answer

The EtherChannel is not forming due to three issues: (1) Speed mismatch: Gi0/1 is set to 100 Mbps while Gi0/2 is 1000 Mbps; both must match (e.g., auto). (2) Duplex mismatch: Gi0/1 is half-duplex, Gi0/2 is full-duplex; both must be the same (e.g., full). (3) VLAN mismatch: Gi0/1 is in VLAN 10, Gi0/2 in VLAN 20, and Port-channel1 is in VLAN 1; all access VLANs must be consistent (set to VLAN 10). Additionally, the channel-group mode should be 'active' on both interfaces for LACP. The solution involves setting speed and duplex to auto, changing the access VLAN on Gi0/2 and the port-channel to VLAN 10, and setting channel-group mode to active.

Exam trap

The exam trap here is that candidates may focus only on resolving the speed/duplex and VLAN mismatches but forget to check the LACP mode requirement. Also, they might confuse LACP modes (active/passive) with PAgP modes (desirable/auto). Always verify that the mode matches the protocol and the requirement.

Why the other options are wrong

B

The specific factual error: passive mode on both sides will not form an LACP EtherChannel because neither side initiates negotiation; at least one side must be active.

C

The specific factual error: 'desirable' is a PAgP mode; LACP uses 'active' or 'passive'. Using 'desirable' would not form an LACP EtherChannel.

D

The VLAN assignments are still inconsistent: member ports must share the same access VLAN, and the stem requires VLAN 10.

127
MCQhard

A network engineer is configuring a new switch port for a VoIP phone that will have a PC daisy-chained behind it. The engineer wants to ensure that voice traffic is tagged with VLAN 100 and data traffic is untagged in VLAN 200. Which configuration should be applied to the switch port?

A.Configure the port as an access port in VLAN 200 and enable voice VLAN 100 with the switchport voice vlan 100 command.
B.Configure the port as a trunk port with native VLAN 200 and allowed VLAN 100.
C.Configure the port as an access port in VLAN 100 and enable voice VLAN 200 with the switchport voice vlan 200 command.
D.Configure the port as a trunk port with native VLAN 100 and allowed VLAN 200.
AnswerA

This configuration sets the port as an access port for data traffic in VLAN 200, while enabling voice VLAN 100 for VoIP traffic. The phone will tag voice traffic with VLAN 100, and the PC's data traffic will be untagged and assigned to VLAN 200. This meets the requirement of tagged voice and untagged data on the same port.

Why this answer

The correct configuration uses the voice VLAN feature on an access port. The port is set to access VLAN 200 for data traffic, and the voice VLAN 100 is enabled. The VoIP phone will tag voice frames with VLAN 100, while the PC's data frames remain untagged and are placed in VLAN 200.

This is the standard Cisco approach for connecting a phone and PC on a single switch port.

Exam trap

The trap here is assuming that a trunk port is required for voice and data separation, when the voice VLAN feature on an access port achieves the same result with simpler configuration.

128
Multi-Selectmedium

A network administrator is configuring a Cisco router to act as a DHCP server for a new VLAN. The router must provide IP addresses, default gateway, and DNS server information to clients. Which two commands are required in the DHCP pool configuration to provide the default gateway and DNS server to clients? (Choose two.)

Select 2 answers
A.network 10.1.1.0 255.255.255.0
B.default-router 10.1.1.1
C.dns-server 8.8.8.8
D.lease 0 8
E.ip helper-address 10.1.1.1
AnswersB, C

The default-router command in DHCP pool configuration specifies the default gateway address that will be provided to DHCP clients. In this scenario, it sets the gateway to 10.1.1.1, which is essential for clients to reach other networks. Without this command, clients would not receive a default gateway and could only communicate on the local subnet.

Why this answer

To provide default gateway and DNS server information to DHCP clients, the DHCP pool must include the default-router and dns-server commands. The default-router command supplies the gateway address, and the dns-server command supplies the DNS server address. The network command defines the pool subnet, the lease command sets lease time, and ip helper-address is used for DHCP relay, not for these parameters.

Exam trap

The trap here is mixing up the network command, which defines the pool, with the default-router and dns-server commands, which actually provide the gateway and DNS information.

129
PBQmedium

You are connected to SW1 via the console. SW1 is a Layer 2 switch connected to router R1 via trunk link G0/1. R1 performs inter-VLAN routing using subinterfaces. VLANs 10, 20, and 30 exist on SW1. Hosts in VLAN 10 (192.168.10.0/24) can ping R1's subinterface, but cannot communicate with hosts in VLAN 20. You suspect the trunk is not allowing VLAN 20 traffic.

Network Topology
G0/0.10192.168.10.1G0/1trunkR1SW1

Hints

  • •Check which VLANs are allowed on the trunk.
  • •The 'allowed vlan' command can be used to add or remove VLANs.
  • •Verify that VLAN 20 exists on the switch.
A.Configure 'switchport trunk allowed vlan add 20' on SW1's G0/1 interface.
B.Configure 'switchport mode access' on SW1's G0/1 interface.
C.Configure 'switchport trunk native vlan 20' on SW1's G0/1 interface.
D.Configure 'switchport trunk allowed vlan except 20' on SW1's G0/1 interface.
AnswerA
solution
! SW1
interface GigabitEthernet0/1
switchport trunk allowed vlan add 20

Why this answer

The symptom — VLAN 10 hosts can reach R1's subinterface but VLAN 20 hosts cannot communicate — points to VLAN 20 being pruned from the trunk. The correct fix is to add VLAN 20 to the trunk's allowed VLAN list on SW1's G0/1 interface using 'switchport trunk allowed vlan add 20', which preserves existing allowed VLANs while permitting VLAN 20. This restores 802.1Q tagging for VLAN 20 traffic across the trunk to R1.

Exam trap

200-301 often tests the misconception that configuring a native VLAN or changing port mode will fix VLAN reachability — candidates overlook that the allowed VLAN list on a trunk is exclusive once explicitly set and must be amended with the 'add' keyword.

Why the other options are wrong

B

Access mode carries only a single VLAN, so it would stop inter-VLAN routing entirely.

C

The native VLAN is for untagged frames; changing it does not add VLAN 20 to the allowed list.

D

The 'except' keyword excludes the specified VLAN, so it would prevent VLAN 20 from being carried.

130
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). Router R1 is connected to port G0/1 on SW1 and performs inter-VLAN routing with 802.1Q subinterfaces (Router-on-a-Stick). Currently the router is not routing between VLANs because the switch port is not a trunk. Configure the switch port as an 802.1Q trunk that carries only VLANs 10 and 20.

Network Topology
G0/0R1SW1 G0/1

Hints

  • •The router expects a trunk link to carry multiple VLANs.
  • •Allowed VLAN list must include only the VLANs that need routing.
  • •The switch port must be in trunk mode, not access.
A.Configure the switch port as a trunk with 802.1Q encapsulation and allow VLANs 10 and 20.
B.Configure the switch port as an access port in VLAN 10 and add VLAN 20 as a secondary VLAN.
C.Configure the switch port as a trunk with ISL encapsulation and allow all VLANs.
D.Configure the switch port as a trunk with 802.1Q encapsulation and allow only VLAN 10.
AnswerA
solution
! SW1
interface GigabitEthernet0/1
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk allowed vlan 10,20

Why this answer

The switch port was in access mode, which only carries one VLAN. Changing it to trunk with 802.1Q encapsulation allows multiple VLANs to traverse to the router. The allowed VLAN list restricts to VLANs 10 and 20 for security.

Exam trap

The trap is that candidates may confuse trunking with access ports, use outdated encapsulation (ISL), or include unnecessary VLANs like VLAN 1. Always remember that for Router-on-a-Stick, the switch port must be a trunk with 802.1Q and only allow the required VLANs.

Why the other options are wrong

B

Access ports cannot carry multiple VLANs; they are assigned to a single VLAN. The concept of secondary VLAN does not exist for access ports.

C

ISL encapsulation is deprecated in favor of 802.1Q, which is the industry standard. Allowing all VLANs violates the principle of least privilege.

D

Allowing only VLAN 10 omits VLAN 20, which also needs to be routed.

131
Multi-Selectmedium

A network administrator is configuring a new switch and needs to set up VLANs. The administrator wants to ensure that VLAN 10 is used for voice traffic and VLAN 20 for data traffic on a port connected to an IP phone and a PC. Which two commands are required on the interface to achieve this configuration? (Choose two.)

Select 2 answers
A.switchport mode access
B.switchport voice vlan 10
C.switchport mode trunk
D.switchport trunk encapsulation dot1q
E.switchport access vlan 20
AnswersB, E

This command configures VLAN 10 as the voice VLAN. The IP phone will tag its voice traffic with VLAN 10, while data traffic from the PC remains untagged and is assigned to the access VLAN. This enables proper QoS and segmentation for voice.

Why this answer

To support both voice and data on a single port, the interface must be in access mode with a voice VLAN. The 'switchport access vlan 20' command assigns the data VLAN, and 'switchport voice vlan 10' assigns the voice VLAN. The phone tags voice traffic, while data traffic remains untagged.

Exam trap

The trap here is assuming that a trunk is needed for voice and data; however, Cisco's voice VLAN feature allows an access port to carry both by tagging voice traffic.

132
MCQhard

Interface g0/0 faces the VLAN 20 LAN and has `ip nat outside`, while the WAN interface g0/1 has `ip nat inside`. Hosts in VLAN 20 must reach the internet through PAT, but users report no external connectivity. Which configuration issue best explains the problem?

A.The ACL should deny 192.168.20.0/24 instead of permit it
B.The interfaces are marked with inside and outside in the wrong places
C.PAT cannot be used with a /30 WAN link
D.NAT overload requires a route-map instead of an ACL
AnswerB

When PAT is configured, Cisco IOS identifies traffic to translate based on the inside and outside interface roles. If those labels are swapped, traffic arriving from the campus LAN appears on the 'outside' interface, so it is not considered an 'inside local' source and the translation rule does not trigger. As a result, packets are forwarded without translation and hosts on VLAN 20 cannot reach the internet through PAT. The fix is to mark the LAN-facing interface as 'inside' and the WAN-facing interface as 'outside' so the NAT process operates in the correct direction.

Why this answer

NAT overload works only when the inside and outside interfaces are identified correctly. Here the roles are reversed, so translations are not built in the right direction.

Exam trap

A frequent exam trap is assuming that the ACL or the subnet mask is the cause of NAT failure when the real issue is reversed inside and outside interface roles. Candidates often overlook the importance of interface designation commands (ip nat inside and ip nat outside), which are crucial for NAT operation. Without correct interface roles, the router cannot translate addresses properly, causing hosts to lose external connectivity even if ACLs and routing are correct.

This trap is tempting because ACLs and subnetting are more familiar concepts, but interface roles are equally critical for NAT to function.

Why the other options are wrong

A

Option A is incorrect because the ACL used for NAT must permit the inside local subnet (192.168.20.0/24) to allow translation. Denying this subnet would block NAT translation, but the question states the ACL permits it, so this is not the cause.

C

Option C is incorrect because a /30 WAN link is commonly used in point-to-point connections and does not prevent PAT from functioning. PAT works independently of the WAN subnet size.

D

Option D is incorrect because NAT overload can be configured using a standard ACL; a route-map is optional and not required. The absence of a route-map does not cause the connectivity issue described.

133
MCQmedium

A network administrator is configuring a switch port that connects to a Cisco IP phone, which in turn has a desktop PC attached to its PC port. The administrator wants the phone to be placed in VLAN 100 and the PC in VLAN 200 on the same physical switch port. Which configuration should be applied to the switch port?

A.Configure the port as a trunk port and allow VLAN 100 and VLAN 200 on the trunk.
B.Configure the port as an access port in VLAN 100 and enable the voice VLAN 100 on the port.
C.Configure the port as a dynamic auto port and enable VLAN 100 and VLAN 200 with the switchport trunk allowed vlan command.
D.Configure the port as an access port in VLAN 200 and configure the voice VLAN as 100 using the switchport voice vlan 100 command.
AnswerD

This is the correct configuration for a Cisco IP phone with a PC attached. The access VLAN (200) carries untagged data traffic from the PC, while the voice VLAN (100) carries tagged voice traffic from the phone. The switchport voice vlan command enables the phone to receive its VLAN information via CDP or LLDP-MED and tag voice frames appropriately.

Why this answer

The correct approach uses an access port for the PC data VLAN and the switchport voice vlan command for the phone voice VLAN. This allows the phone to tag voice traffic with VLAN 100 while the PC sends untagged traffic in VLAN 200. The phone learns the voice VLAN through CDP or LLDP-MED and can also pass through the PC data.

Exam trap

The trap here is assuming that a trunk port is required to support both a voice and data VLAN on a single switch port.

134
MCQhard

After hardening SSH by disabling password authentication and restricting access to an ACL permitting only the management subnet 10.1.10.0/24, configuring RADIUS AAA authentication, enabling port security with a maximum of two MAC addresses on all access ports, and implementing DHCP snooping and DAI on VLAN 10, the administrator finds that users in VLAN 10 obtain DHCP addresses and access the network normally, but SSH from the management workstation (10.1.10.20) to the switch fails with timeouts.

A.The SSH ACL is misconfigured and denies port 22 from the management subnet.
B.The management workstation’s IP-to-MAC binding is missing from the DHCP snooping binding table, causing DAI to drop its ARP traffic.
C.Port security on the switch interface connected to the management workstation has learned two MAC addresses and shut down the port.
D.RADIUS AAA authentication is missing the shared secret on the switch, causing SSH login timeouts.
AnswerB

Dynamic ARP Inspection (DAI) validates ARP packets against the DHCP snooping binding table, which contains IP-to-MAC mappings learned from DHCP. Because the management workstation uses a static IP address, no DHCP binding is ever recorded, so the switch has no entry for that IP. As a result, DAI classifies the workstation's ARP replies as invalid and drops them, preventing L2 reachability. This matches the symptom precisely: only the statically configured host fails, while DHCP-assigned management hosts continue to work normally.

Why this answer

The management workstation (10.1.10.20) is on the same VLAN 10 where DHCP snooping and DAI are enabled. DAI validates ARP packets against the DHCP snooping binding table. Since the workstation uses a static IP address, its IP-to-MAC binding is not automatically added to the DHCP snooping database.

DAI will drop the workstation's ARP replies, preventing the switch from learning its MAC address and causing SSH timeouts.

Exam trap

Cisco often tests the interaction between security features like DAI and static IP hosts, where candidates overlook that DAI requires explicit static bindings for non-DHCP clients, leading to connectivity failures that appear as timeouts rather than explicit denials.

Why the other options are wrong

A

Misunderstanding ACL processing—assumes a simple subnet permit ACL would block port 22 by default, but the ACL entry permits all traffic from the subnet, not just specific ports.

C

Assumes port security is the first cause of connectivity failure when MAC limits are configured, but the symptom does not indicate a port security violation; the port would need to go into err-disabled, which is not mentioned.

D

AAA failures manifest as authentication errors or prompts that time out after attempting RADIUS, but they typically affect all attempts, not a single source, unless combined with ACLs that permit other hosts but block this one.

135
PBQhard

You are connected to a multilayer switch MLS1. The network has two other switches: SW2 and SW3. The interface GigabitEthernet0/1 already has PortFast and BPDU Guard enabled. Configure MLS1 as the root bridge for VLAN 10 and VLAN 20 using the root primary command. After configuration, verify that the interface is not in err-disabled state and that the root bridge role is correctly assigned.

Network Topology
Gi0/1Gi0/2Gi0/3SiMLS1PCSW2SW3

Hints

  • •Use spanning-tree vlan root primary to set the switch as root for specified VLANs.
  • •Verify with show spanning-tree vlan <vlan> to confirm root bridge priority is 24576.
  • •Check interface status with show interfaces gigabitethernet 0/1 status to ensure it is not err-disabled.
A.Configure 'spanning-tree vlan 10 root primary' and 'spanning-tree vlan 20 root primary' on MLS1. Verify with 'show spanning-tree vlan 10' and 'show interfaces gigabitEthernet0/1 status'.
B.Configure 'spanning-tree vlan 10 root primary' and 'spanning-tree vlan 20 root secondary' on MLS1. Verify with 'show spanning-tree vlan 10' and 'show interfaces gigabitEthernet0/1 status'.
C.Configure 'spanning-tree vlan 10 priority 4096' and 'spanning-tree vlan 20 priority 4096' on MLS1. Verify with 'show spanning-tree vlan 10' and 'show interfaces gigabitEthernet0/1 status'.
D.Configure 'spanning-tree vlan 10 root primary' and 'spanning-tree vlan 20 root primary' on MLS1, then remove 'spanning-tree bpduguard enable' from Gi0/1 so that it can never be err-disabled.
AnswerA
solution
! MLS1
spanning-tree vlan 10 root primary
spanning-tree vlan 20 root primary

Why this answer

The exhibit shows another switch is currently root for VLAN 10 (priority 28682). spanning-tree vlan 10 root primary and spanning-tree vlan 20 root primary make MLS1 root by setting a lower priority (24576 plus the VLAN ID, or lower than the current root if needed). Gi0/1 already has PortFast and BPDU Guard and is connected (not err-disabled), so no change is needed there. Root secondary does not make MLS1 root, a priority 4096 command is not the root primary command the task requires, and removing BPDU Guard would remove an intended protection.

Exam trap

Do not confuse 'root primary' with 'root secondary' or manual priority settings. The 'root primary' command automatically sets the priority to 24576, which is the recommended value. Also, avoid adding unnecessary global commands when the interface already has the required features configured.

Why the other options are wrong

B

Using 'root secondary' for VLAN 20 sets priority to 28672, leaving MLS1 as backup root, not the primary root.

C

Manually setting priority to 4096 is valid but not the recommended method; 'root primary' is simpler and ensures proper value.

D

Global portfast and bpduguard are not required because the interface is already configured with those features; this adds unnecessary commands.

136
Multi-Selectmedium

A network technician is configuring a new Cisco switch and needs to secure unused switch ports to prevent unauthorized access. The technician decides to disable the ports and place them in an unused VLAN. Which two commands are required to accomplish this on each unused interface? (Choose two.)

Select 2 answers
A.shutdown
B.switchport mode access
C.switchport access vlan 999
D.switchport trunk allowed vlan none
E.no switchport
AnswersA, C

The 'shutdown' command administratively disables the interface, preventing any traffic from being sent or received. This is a critical step to secure unused ports. When a port is shut down, it cannot be used for unauthorized access. This command is entered in interface configuration mode. It is one of the two required commands to disable the ports as specified in the scenario.

Why this answer

To secure unused ports, you should administratively disable them with the 'shutdown' command and assign them to an unused VLAN using 'switchport access vlan 999'. This prevents unauthorized devices from connecting and isolates any potential traffic. Setting the port to access mode is also good practice but not one of the two required commands in this scenario.

Exam trap

The trap here is thinking that setting the port to access mode or using trunk commands is sufficient to secure unused ports, when the key actions are disabling the port and placing it in an unused VLAN.

137
MCQhard

A network engineer is troubleshooting connectivity issues for hosts in VLAN 10. Hosts in VLAN 10 are unable to ping the default gateway at 192.168.10.1. The engineer checks the switch configuration and notices that the SVI for VLAN 10 is configured with an IP address, but the interface is in a down/down state. What is the most likely cause of this issue?

A.The interface is administratively shut down.
B.VLAN 10 does not exist in the VLAN database.
C.The IP address is not in the correct subnet for VLAN 10.
D.The switch does not have a default gateway configured.
AnswerB

The SVI for VLAN 10 is down/down because the VLAN is not created. Once VLAN 10 is created with the 'vlan 10' command in global configuration mode, the SVI will come up if there is at least one active port in that VLAN.

Why this answer

An SVI (Switch Virtual Interface) will remain in a down/down state if the corresponding VLAN does not exist in the switch's VLAN database. Even if the SVI is configured with an IP address, the interface cannot come up because there is no Layer 2 VLAN to associate with it. This is a common cause of SVI down/down issues when the VLAN has not been created or has been deleted.

Exam trap

Cisco often tests the distinction between an SVI being down due to a missing VLAN versus an administratively shutdown interface, leading candidates to mistakenly choose the administrative shutdown option when the interface status shows 'down/down' instead of 'administratively down'.

Why the other options are wrong

A

The running-config shows 'no shutdown', so this is not the cause.

C

The IP address and subnet mask are correctly configured for the VLAN.

D

The SVI status is not affected by the presence or absence of a default gateway.

138
Multi-Selectmedium

Which TWO statements are true regarding VLAN configuration, 802.1Q trunking, and the native VLAN?

Select 2 answers
A.On an 802.1Q trunk, frames in the native VLAN are always tagged with a VLAN ID.
B.The native VLAN should be changed from the default VLAN 1 to an unused VLAN for security reasons.
C.802.1Q is a Cisco proprietary trunking protocol.
D.802.1Q supports up to 4094 VLANs (VLAN IDs 1–4094).
E.The native VLAN must be the same on both ends of an 802.1Q trunk for the trunk to operate.
AnswersB, D

Changing the native VLAN from the default VLAN 1 to an unused VLAN is a Cisco-recommended hardening step because VLAN 1 is well-documented and often carries control-plane traffic such as CDP, VTP, and PAgP. Attackers can exploit the default native VLAN to launch double-tagging (VLAN hopping) attacks, so moving native VLAN to a dedicated unused VLAN reduces the risk of layer 2 traffic being intercepted or misforwarded. Additionally, using an unused VLAN ensures that no legitimate user traffic is accidentally sent untagged on the trunk, which prevents VLAN misclassification.

Why this answer

Changing the native VLAN from the default VLAN 1 to an unused VLAN is a recommended security best practice to prevent VLAN hopping attacks. Option D is correct because 802.1Q uses a 12-bit VLAN ID field, allowing VLAN IDs from 1 to 4094 (0 and 4095 are reserved). Option A is false: on an 802.1Q trunk, frames in the native VLAN are typically sent untagged.

Option C is false: 802.1Q is an IEEE standard, not Cisco proprietary (ISL is Cisco proprietary). Option E is false: the native VLAN does not have to match on both ends; mismatched native VLANs can cause traffic to be misclassified but the trunk will still operate.

Exam trap

Cisco often tests the misconception that 802.1Q is proprietary (it is not) and that native VLAN frames are always tagged (they are untagged by default), leading candidates to incorrectly select options A or C.

Why the other options are wrong

A

The native VLAN is specifically the VLAN that does not get a tag; all other VLANs are tagged.

C

802.1Q is an open standard, whereas ISL was Cisco proprietary.

E

Mismatched native VLANs can lead to security vulnerabilities and misrouting, but the trunk itself may still come up.

139
MCQhard

A network engineer is configuring a switch port for a new wireless access point that will support multiple SSIDs mapped to different VLANs. The AP will be powered by PoE and will tag traffic for each SSID. Which configuration on the switch port is most appropriate?

A.Configure the port as a trunk port and set the native VLAN to VLAN 1, allowing all VLANs.
B.Configure the port as a trunk port, set the native VLAN to the AP management VLAN, and allow the SSID VLANs on the trunk.
C.Configure the port as an access port in the management VLAN and use 802.1X authentication for the SSIDs.
D.Configure the port as an access port in the management VLAN and enable voice VLAN for the SSIDs.
AnswerB

This is the correct configuration for an AP supporting multiple SSIDs. The AP management traffic is typically untagged and placed in the native VLAN, while each SSID's traffic is tagged with its respective VLAN. The trunk allows multiple VLANs to traverse the link. This setup enables the AP to map each SSID to a different VLAN and tag frames accordingly.

Why this answer

For an access point supporting multiple SSIDs, the switch port should be configured as a trunk. The native VLAN is used for untagged management traffic from the AP, while each SSID's traffic is tagged with its corresponding VLAN. Allowing only the necessary VLANs on the trunk is a best practice.

This configuration ensures proper segmentation and security.

Exam trap

The trap here is assuming an access port with voice VLAN can handle multiple SSIDs, or that allowing all VLANs is acceptable.

140
MCQhard

After enabling Dynamic ARP Inspection on VLAN 20, a network engineer notices that some hosts lose connectivity. The affected hosts have correct IP addresses and MAC addresses, but they cannot ping the default gateway. All other hosts on the same VLAN work fine. Further investigation reveals that the non-functioning hosts are using static IP configurations, while the working hosts are DHCP clients. What is the most likely cause?

A.The DHCP snooping binding table is exhausted and cannot accept new bindings for the static hosts.
B.IP Source Guard is also enabled on VLAN 20 and is blocking traffic from hosts that have no DHCP snooping binding.
C.DAI is dropping ARP packets from the static hosts because they do not have a corresponding entry in the DHCP snooping binding table.
D.The switch is detecting ARP spoofing from the static hosts and has shut down their switchport interfaces for security.
AnswerC

When DAI is enabled, it checks every ARP packet on untrusted ports against the DHCP snooping binding table. Since the static hosts have no DHCP lease, no binding exists, and DAI drops their ARP packets, preventing them from learning the gateway MAC address and causing loss of connectivity.

Why this answer

Dynamic ARP Inspection (DAI) relies on the DHCP snooping binding table to validate ARP packets. When a host uses a static IP address, it does not have an entry in that table, so DAI treats its ARP packets as invalid and drops them. This prevents the static host from resolving the default gateway's MAC address, breaking connectivity even though the IP and MAC are correct.

Exam trap

Cisco often tests the dependency of DAI on DHCP snooping, and the trap here is that candidates assume DAI validates based on the actual IP/MAC correctness rather than requiring a binding table entry.

Why the other options are wrong

A

Candidates may think that a large number of untrusted hosts could overwhelm the binding table, but static hosts do not interact with DHCP and would not fill the table or be rejected.

B

Candidates often confuse DAI and IP Source Guard since both use DHCP snooping; however, DAI specifically validates ARP packets, which matches the symptom of connectivity loss due to ARP resolution failure.

D

Some candidates might associate ARP security features with port shutdown, but standard DAI operation does not disable ports, and the symptom does not indicate interface down events.

141
MCQhard

An administrator notices that hosts in VLAN 30 on SW1 cannot communicate with hosts in VLAN 30 on SW2, even though both switches are connected via an 802.1Q trunk. Traffic for VLANs 10 and 20 passes without issues across the same trunk. The trunk is configured to allow all VLANs, and the allowed VLAN list explicitly includes VLAN 30. What is the most likely cause of the problem?

A.The native VLAN is mismatched between SW1 and SW2, and VLAN 30 is the native VLAN on one side.
B.The trunk encapsulation is set to ISL on one switch and 802.1Q on the other.
C.Spanning Tree Protocol has placed VLAN 30 in a blocking state on the trunk link.
D.The switched virtual interface (SVI) for VLAN 30 on SW1 is administratively down.
AnswerA

A native VLAN mismatch causes one switch to send untagged frames for VLAN 30 while the other expects tagged frames, so the receiving switch cannot associate the untagged traffic with VLAN 30, leading to a communication failure only for that VLAN.

Why this answer

The most likely cause is a native VLAN mismatch. When the native VLAN is mismatched on an 802.1Q trunk, traffic for the native VLAN is not tagged, so frames from VLAN 30 on one switch are received as untagged frames on the other switch and placed into the switch's configured native VLAN. If the native VLAN on one side is VLAN 30 and on the other side is a different VLAN (e.g., VLAN 1), the hosts in VLAN 30 cannot communicate because the frames are interpreted as belonging to different VLANs.

Traffic for VLANs 10 and 20 passes because they are not the native VLAN and are properly tagged.

Exam trap

Cisco often tests the native VLAN mismatch scenario by describing a trunk that works for most VLANs but fails for one specific VLAN, leading candidates to incorrectly suspect STP blocking or SVI issues instead of recognizing the native VLAN mismatch.

Why the other options are wrong

B

This would cause a complete trunk failure, not a failure limited to a single VLAN.

C

STP would not randomly block one VLAN on a point-to-point trunk while the rest are forwarding; this is not a typical behavior.

D

Layer 2 switching within the same VLAN does not require an SVI; an SVI is only needed for routing between VLANs or management.

142
MCQhard

Exhibit: A switch interface connected to an IP phone and PC is configured as an access port in VLAN 10. The PC works, but the phone does not register. What additional configuration is most likely needed?

A.switchport trunk encapsulation dot1q
B.switchport voice vlan <voice-vlan-id>
C.channel-group 1 mode active
D.ip helper-address on the switchport
AnswerB

This command configures a dedicated voice VLAN on an access port connected to an IP phone. It allows the phone to tag voice traffic with the specified VLAN ID while the attached PC remains untagged in the access VLAN, enabling separate QoS policies and subnets for voice and data. This is the standard Cisco configuration for a single switchport carrying both phone and PC traffic.

Why this answer

An IP phone commonly requires a voice VLAN so tagged voice traffic is separated from the data VLAN used by the attached PC. Without a voice VLAN, the PC can still work on the access VLAN while the phone fails to register properly.

Exam trap

Don't confuse portfast or trunk mode with the need for a voice VLAN. Focus on the specific requirements of IP phones.

Why the other options are wrong

A

This option is incorrect because the question specifies an access port configuration, which does not require trunk encapsulation. Access ports do not use trunking protocols like dot1q, as they are meant for single VLAN traffic only.

C

This option is wrong because the channel-group command is used for configuring EtherChannel, which is not relevant to the issue of the IP phone not registering on an access port. The problem lies in the VLAN configuration for voice traffic, not in link aggregation.

D

The 'ip helper-address' command is used to forward DHCP requests from clients to a DHCP server, but it does not address the registration issue of the IP phone in this scenario, which is related to VLAN configuration.

143
MCQmedium

Hosts in VLAN 10 need to communicate with hosts in VLAN 20. What is required for that communication to work?

A.A DHCP server
B.A DNS server
C.A Layer 3 routing function
D.A second access switch
AnswerC

Layer 3 routing is the required mechanism because VLANs represent separate broadcast domains and distinct IP subnets. A router or multilayer switch must inspect the destination IP address, perform a route lookup, and rewrite the frame's MAC addresses before forwarding the packet to the destination VLAN. Without this IP-level forwarding decision, frames remain confined to their originating Layer 2 domain, so no traffic can cross the VLAN boundary.

Why this answer

Traffic between VLANs must be routed. A router or multilayer switch provides the Layer 3 function needed for inter-VLAN communication.

Exam trap

Do not confuse trunk links or access ports with routing functions; they serve different purposes in VLAN configurations.

Why the other options are wrong

A

A DHCP server is not required for communication between VLANs; it only assigns IP addresses to devices within a network. VLAN communication requires routing, which a DHCP server does not provide.

B

A DNS server is not required for VLAN communication, as DNS resolves domain names to IP addresses, which does not facilitate inter-VLAN routing. Communication between VLANs requires Layer 3 routing, not name resolution.

D

A second access switch is not required for VLAN communication; VLANs can communicate through a Layer 3 device such as a router or a Layer 3 switch. The existing switch infrastructure can handle VLANs without needing additional switches.

144
MCQhard

A multilayer switch must route traffic between VLAN 10 and VLAN 20. Which condition is required for that to happen?

A.SVIs for the VLANs plus Layer 3 routing enabled on the switch
B.All ports in both VLANs configured as trunks
C.A separate OSPF process on every access port
D.Port security disabled on every edge port
AnswerA

On a multilayer switch, inter-VLAN routing is accomplished by creating a Switch Virtual Interface (SVI) for each VLAN and assigning each SVI an IP address in its respective subnet. These SVIs act as the default gateway for hosts in their VLAN, and the switch must have IP routing globally enabled with 'ip routing' so it can forward packets between the SVIs at Layer 3. This is the standard method for inter-VLAN routing on a multilayer switch, as opposed to using an external router or router-on-a-stick.

Why this answer

Inter-VLAN routing on a multilayer switch depends on having functional Layer 3 gateway interfaces for the VLANs and routing enabled on the switch. In plain language, the switch needs a routed brain for each VLAN, usually in the form of SVIs, and it must actually be operating as a Layer 3 device rather than only as a pure Layer 2 switch. Without those conditions, traffic may switch inside a VLAN but cannot be routed between different VLANs.

This is a core CCNA design idea because people often assume creating VLANs alone automatically gives them inter-VLAN communication. In reality, VLANs create separation, and routing is what reconnects them under controlled conditions. A trunk between switches can carry VLAN traffic, but it does not itself perform Layer 3 routing between the VLANs. The correct answer is the requirement that makes the switch act as the gateway between VLANs.

Exam trap

Don't confuse trunking with routing; trunk ports carry VLAN traffic but don't route it.

Why the other options are wrong

B

This option is wrong because configuring all ports as trunks does not facilitate inter-VLAN routing; SVIs and Layer 3 routing are necessary for that functionality.

C

This option is wrong because OSPF is a routing protocol used for dynamic routing, and access ports do not participate in routing processes. Routing between VLANs requires SVIs and Layer 3 capabilities, not OSPF on access ports.

D

Port security being disabled on every edge port is not a requirement for routing traffic between VLANs; it pertains to security configurations rather than routing functionality. VLAN routing can occur regardless of port security settings.

145
PBQhard

You are connected to R1 via console. R1 G0/0 and R2 G0/0 attach to the same VLAN 10 on multilayer switch MLS1 (Gi1/0/1 and Gi1/0/2). R2 (2001:db8:1:10::2/64) and MLS1 Vlan10 (2001:db8:1:10::3/64) are already configured for IPv6, but R1 has no IPv6 address and cannot ping either of them. Configure R1's GigabitEthernet0/0 with the prefix 2001:db8:1:10::/64 using EUI-64 so that R1 can reach both R2 and MLS1.

Network Topology
G0/0G1/0/1G1/0/1G0/0SiMLS1R1R2

Hints

  • •R1's G0/0 has no IPv6 address.
  • •Use the eui-64 keyword so the interface ID is generated from the MAC address.
  • •R2 and MLS1 are already configured; only R1 needs a change.
A.Configure 'ipv6 address 2001:db8:1:10::/64 eui-64' on R1's G0/0 interface.
B.Enable IPv6 routing on R1 with 'ipv6 unicast-routing'.
C.Configure 'ipv6 address 2001:db8:1:10::1/64' on R1's G0/0 interface (without EUI-64).
D.Change the VLAN on MLS1's G1/0/1 to match R1's VLAN.
AnswerA
solution
! R1
interface GigabitEthernet0/0
ipv6 address 2001:db8:1:10::/64 eui-64
end

Why this answer

R1 G0/0 has no IPv6 address ('show ipv6 interface brief' shows unassigned), and ipv6 unicast-routing is already enabled. R2 reaches MLS1 successfully, so VLAN 10 and the other devices are fine. Configure ipv6 address 2001:db8:1:10::/64 eui-64 on R1 G0/0; the router builds the 64-bit interface ID from the interface MAC address, after which R1 can ping 2001:db8:1:10::2 and ::3.

Exam trap

Do not confuse global IPv6 routing enablement with interface address configuration. The presence of a connected route indicates routing is enabled; the missing piece is the interface address. Also, pay attention to specific requirements like EUI-64.

Why the other options are wrong

B

IPv6 unicast-routing is already enabled; the problem is at the interface level.

C

The requirement specifies EUI-64; omitting it results in a static address that does not match the intended configuration.

D

The VLAN configuration is correct; no change is needed.

146
PBQhard

You are connected to switch SW1, which runs Rapid-PVST+. SW2 is the intended root bridge for VLAN 10 (priority 8192). SW1 was accidentally configured with priority 4096 for VLAN 10, so it became the root. In addition, the server port Gi0/1 (PortFast with BPDU Guard) was err-disabled after receiving BPDUs. Restore SW1 to the default priority for VLAN 10 so that it is no longer the root bridge, and configure automatic recovery from err-disable caused only by BPDU Guard violations, with a 300-second interval. Then verify that SW1 is not the root for VLAN 10.

Network Topology
Gi0/0Gi0/0Gi0/1SW1SW2Server

Hints

  • •To prevent a switch from becoming root, set its priority to a value higher than the current root's priority (e.g., 32768).
  • •The errdisable recovery cause command enables automatic recovery; the interval command sets the timeout.
  • •After configuration, verify with 'show spanning-tree vlan 10' that the bridge ID priority is not the lowest.
A.spanning-tree vlan 10 priority 32768; errdisable recovery cause bpduguard; errdisable recovery interval 300; show spanning-tree vlan 10
B.spanning-tree vlan 10 priority 4096; errdisable recovery cause bpduguard; errdisable recovery interval 300; show spanning-tree vlan 10
C.spanning-tree vlan 10 root primary; errdisable recovery cause bpduguard; errdisable recovery interval 300; show spanning-tree vlan 10
D.spanning-tree vlan 10 priority 32768; errdisable recovery cause all; errdisable recovery interval 300; show spanning-tree vlan 10
AnswerA
solution
! SW1
no spanning-tree vlan 10 priority 4096
spanning-tree vlan 10 priority 32768
errdisable recovery cause bpduguard
errdisable recovery interval 300

Why this answer

SW1 is the root because 'spanning-tree vlan 10 priority 4096' (global command) gives it a lower priority than SW2 (8192). Remove it or set the default 32768 so SW1 loses the election. The port Gi0/1 is err-disabled by BPDU Guard, so enable automatic recovery for that cause only with 'errdisable recovery cause bpduguard' and set the timer with 'errdisable recovery interval 300'.

Verify with show spanning-tree vlan 10 (This bridge is the root should no longer appear) and show errdisable recovery.

Exam trap

Students often confuse the priority values: lower priority is better to become root. To prevent a switch from becoming root, set its priority higher than the current root's. Also, remember that 'root secondary' sets a low priority (28672) and does not prevent root election.

For errdisable recovery, use the specific cause (bpduguard) rather than 'all'.

Why the other options are wrong

B

4096 keeps SW1 as the root.

C

root primary makes SW1 the root.

D

'all' is broader than the BPDU-Guard-only requirement.

147
MCQhard

Refer to the exhibit. A network administrator runs the show vlan brief command on SW2. Interface GigabitEthernet0/2 is intended to be an access port in VLAN 10, but it does not appear in the output. What is the most likely cause?

A.The interface is configured with switchport mode dynamic auto and no trunk has been negotiated, causing it to be hidden.
B.The interface is administratively shut down, and down ports are excluded from the show vlan brief output.
C.The interface is configured as a trunk port and therefore does not appear under any VLAN in show vlan brief.
D.VLAN 10 is not active, so the port assigned to it is not displayed in the listing.
AnswerC

show vlan brief only displays ports that are in access mode. Trunk ports are not included because they belong to all VLANs allowed on the trunk. The output shows VLAN 10 with members Gi0/9–Gi0/11 but not Gi0/2, confirming it is not an access port.

Why this answer

The `show vlan brief` command displays only access ports and their assigned VLANs. Trunk ports, which carry multiple VLANs, are not listed in this output. If GigabitEthernet0/2 is configured as a trunk port (e.g., with `switchport mode trunk` or dynamically via DTP), it will not appear under any VLAN in the `show vlan brief` output, even if it is intended to be an access port in VLAN 10.

Exam trap

Cisco often tests the distinction between access and trunk port behavior in `show vlan brief` output, trapping candidates who assume all switchports appear in the VLAN listing regardless of mode.

Why the other options are wrong

A

Confusion about how dynamic trunking protocol (DTP) modes interact with VLAN membership display.

B

Misconception that only operational interfaces are shown in VLAN membership tables.

D

Overlooking the explicit 'active' status and port list for VLAN 10 in the output.

148
MCQhard

A network engineer is troubleshooting connectivity between two hosts in different VLANs on the same switch. Host A in VLAN 10 (10.10.10.5/24) cannot ping Host B in VLAN 20 (10.10.20.5/24). The switch is configured as a router-on-a-stick with a trunk port to an external router. The trunk port is up/up, but inter-VLAN routing fails. What is the most likely cause?

A.The trunk port is not in trunking mode; it is in dynamic desirable mode.
B.The native VLAN on the switch trunk is VLAN 1, but the router subinterface for VLAN 1 is not configured with the 'native' keyword or is missing.
C.The VLANs are not allowed on the trunk; the allowed VLAN list is missing VLAN 10 and 20.
D.The switch ports Gi0/4 and Gi0/5 are in access mode but not assigned to the correct VLANs.
AnswerC

The trunk allows only VLANs 1 and 30 ('switchport trunk allowed vlan 1,30'), so VLAN 10 and 20 frames are not sent to the router and inter-VLAN routing fails even though the trunk is up/up.

Why this answer

The trunk Gi0/1 is up and trunking, but 'show interfaces trunk' and the interface configuration show that only VLANs 1 and 30 are allowed ('switchport trunk allowed vlan 1,30'). VLANs 10 and 20 exist and have access ports in them, but their tagged frames are not carried on the trunk, so the router subinterfaces never receive them and inter-VLAN routing fails. Add VLANs 10 and 20 with 'switchport trunk allowed vlan add 10,20'.

Exam trap

A common trap is assuming an up/up trunk automatically passes traffic for all VLANs, overlooking that the allowed VLAN list can be manually pruned and must include every VLAN that needs to traverse the trunk.

Why the other options are wrong

A

The trunk is operational (trunking).

B

A native VLAN mismatch only impacts untagged frames; the hosts send tagged traffic, so a missing 'native' keyword on the router subinterface does not block the VLAN 10 and VLAN 20 frames.

D

show vlan brief shows the access ports are in the correct VLANs.

149
MCQhard

A DHCP client on VLAN 30 is not receiving an IP address from a DHCP server (10.99.99.20) on another subnet. The SVI for VLAN 30 is configured with an IP address and is up, but the DHCP relay command is missing. Which command should be added to the SVI configuration?

A.ip directed-broadcast
B.ip helper-address 10.99.99.20
C.service dhcp-server 10.99.99.20
D.default-router 10.99.99.20
AnswerB

On the VLAN 30 SVI, the DHCP client's broadcast is not forwarded by default because routers do not forward link-local broadcasts. The command `ip helper-address 10.99.99.20` instructs the router to convert that DHCPDISCOVER broadcast into a unicast packet and send it to the DHCP server at 10.99.99.20, while also inserting the SVI's IP address as the giaddr field. This allows the server to know which subnet the client is on and assign an address from the correct pool. Without this command, the client's broadcast remains confined to VLAN 30 and the server never receives the request.

Why this answer

DHCP Discover messages are broadcasts and do not cross routers by default. On an SVI or routed interface facing the clients, an ip helper-address relays those broadcasts to the DHCP server on another subnet.

Exam trap

A frequent exam trap is selecting ip directed-broadcast or default-router as the solution for DHCP relay issues. ip directed-broadcast only enables forwarding of directed broadcasts but does not relay DHCP requests to servers on other subnets. default-router is a DHCP pool parameter that assigns a gateway to clients but does not affect how DHCP broadcasts are forwarded. Another trap is assuming service dhcp-server is an interface command for relay, which it is not. These distractors test your understanding of DHCP relay mechanisms and Cisco IOS command usage.

Why the other options are wrong

A

The ip directed-broadcast command enables forwarding of directed broadcasts but does not relay DHCP requests. It is unrelated to DHCP relay and will not solve the problem of clients not receiving addresses from a remote DHCP server.

C

service dhcp-server is not a valid Cisco IOS interface command for DHCP relay. It does not configure the router to forward DHCP broadcasts and thus will not resolve the issue.

D

default-router is a DHCP pool parameter used to assign the default gateway IP address to clients. It does not configure the interface to relay DHCP broadcasts and is not relevant to the relay configuration.

150
MCQmedium

On an 802.1Q trunk, which VLAN is sent untagged by default on many Cisco switches unless changed?

A.VLAN 10
B.VLAN 20
C.VLAN 1
D.The highest configured VLAN
AnswerC

By default, Cisco switches configure VLAN 1 as the native VLAN on an 802.1Q trunk. Frames in the native VLAN are transmitted without a VLAN tag, while all other VLANs carry a 802.1Q tag. This default behavior ensures that control-plane traffic like CDP, VTP, and DTP, which typically run on VLAN 1, can traverse the trunk without tagging.

Why this answer

On many Cisco platforms, VLAN 1 is the default native VLAN. Native VLAN traffic is sent untagged unless the native VLAN is changed.

Exam trap

Be cautious not to confuse commonly used VLANs in practice with the default native VLAN set by Cisco.

Why the other options are wrong

A

VLAN 10 is not the default untagged VLAN on Cisco switches; instead, VLAN 1 is typically used for this purpose unless configured otherwise. Therefore, selecting VLAN 10 would be incorrect in the context of the question.

B

VLAN 20 is not the default untagged VLAN on Cisco switches; instead, VLAN 1 is typically sent untagged on 802.1Q trunks unless configured otherwise. Therefore, selecting VLAN 20 does not align with the standard behavior of Cisco switch configurations.

D

This option is incorrect because the default untagged VLAN on many Cisco switches is VLAN 1, not the highest configured VLAN. The highest configured VLAN can vary based on the network setup and does not have a default status in this context.

← PreviousPage 2 of 3 · 221 questions totalNext →

Ready to test yourself?

Try a timed practice session using only VLAN questions.