Courseiva

CCNA STP Questions

75 of 77 questions · Page 1/2 · STP topic · Answers revealed

1
Multi-Selectmedium

Which three statements about the Spanning Tree Protocol (STP) are true? (Choose three.)

Select 3 answers
.STP uses Bridge Protocol Data Units (BPDUs) to exchange topology information.
.STP elects a root bridge based on the lowest bridge ID.
.STP places redundant ports in blocking state to prevent loops.
.STP always uses the highest port cost to select the root port.
.STP converges instantly after a topology change.
.STP is used to increase the number of broadcast domains.

Why this answer

All three statements are correct because STP relies on Bridge Protocol Data Units (BPDUs) to share topology information between switches, elects a root bridge by comparing bridge IDs (a combination of priority and MAC address, with the lowest value winning), and prevents loops by placing redundant ports into a blocking state (discarding state in Rapid PVST+). These are fundamental behaviors of the 802.1D Spanning Tree Protocol.

Exam trap

Cisco often tests the fact that STP does not use timers to elect the root bridge (it uses bridge ID comparison) and that blocking state is the mechanism for loop prevention, not disabling the port entirely or relying on TCN BPDUs alone.

2
Drag & Dropmedium

Drag and drop the following steps into the correct order to configure PortFast and BPDU Guard on access port GigabitEthernet0/1, and then recover the port after a BPDU Guard err-disable event (after the offending switch has been removed). Select the correct sequence.

Drag or tap steps into the slots.

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

Why this order

Interface commands can only be entered after global configuration mode and the interface have been selected, so the order is: configure terminal, interface GigabitEthernet0/1, enable PortFast and BPDU Guard on the port, and, once the offending device is removed from an err-disabled port, bounce the port with shutdown followed by no shutdown. Shutdown must come before no shutdown; reversing them does nothing and leaves the port in whatever state it was in.

Exam trap

Be aware that there are multiple valid ways to configure and recover from BPDU Guard. The order of steps within each method must be respected: PortFast must be enabled before BPDU Guard on the interface (unless using global defaults), and recovery commands must be configured before the error occurs for automatic recovery. Do not mix steps from different methods.

3
MCQmedium

A network administrator is troubleshooting a Cisco switch that is experiencing high CPU utilization. The administrator suspects a Layer 2 loop. Which command can be used to verify if Spanning Tree Protocol (STP) has blocked any ports due to a loop?

A.show interfaces status
B.show ip interface brief
C.show spanning-tree
D.show mac address-table
AnswerC

The show spanning-tree command displays the STP status for each VLAN, including which ports are in blocking state. If a loop exists, STP will block redundant ports to prevent loops. This command helps identify blocked ports and verify the root bridge and port roles.

Why this answer

The show spanning-tree command is the correct tool to verify STP port states, including blocking. It shows the root bridge, port roles, and states for each VLAN, allowing the administrator to confirm if STP has blocked a port to prevent a loop.

Exam trap

The trap here is confusing commands that show interface status or MAC addresses with those that show STP information. Only show spanning-tree directly displays STP port states.

4
MCQmedium

Which spanning-tree port state listens for BPDUs and participates in STP, but does not learn MAC addresses yet?

A.Blocking
B.Listening
C.Learning
D.Forwarding
AnswerB

The Listening state follows the Blocking state and precedes the Learning state in STP convergence. During Listening, the port actively listens for BPDUs to determine the root bridge and its port role, and it does not learn MAC addresses or forward user traffic. This is the state that matches the question's description, as it is the phase specifically designated for BPDU listening to build the STP topology.

Why this answer

In the classic 802.1D sequence, the listening state processes BPDUs and prepares for forwarding decisions, but it does not populate the MAC address table yet.

Exam trap

Be careful not to confuse the listening state with learning, as both involve BPDU processing but differ in MAC address table updates.

Why the other options are wrong

A

In the blocking state, the port does not participate in STP actively; it only receives BPDUs but does not send them or transition toward forwarding. The question specifies a state that listens for BPDUs and participates in STP, which is the listening state, not blocking.

C

The learning state populates the MAC address table by learning source MAC addresses from incoming frames, which directly contradicts the question's requirement that the state does not learn MAC addresses. Learning occurs after listening and before forwarding.

D

The forwarding state both learns MAC addresses and forwards traffic, which violates the condition that the state does not learn MAC addresses. Forwarding is the final state where the port is fully operational.

5
MCQhard

A network administrator notices that a switchport in access mode with PortFast enabled has transitioned to an err-disabled state. What is the most likely cause?

A.BPDU Guard disabled the PortFast-enabled access port after it received a BPDU.
B.Port security shut down the port because the VLAN was wrong.
C.DHCP snooping disabled the interface because a host requested an address.
D.EtherChannel suspended the interface because the bundle was incomplete.
AnswerA

BPDU Guard is a spanning-tree feature designed to protect PortFast-enabled access ports: when an unauthorized device such as a switch sends a BPDU, the switch immediately places the port in err-disabled state to prevent a potential Layer 2 loop. The %SPANTREE-2-BLOCK_BPDUGUARD message in the exhibit confirms this exact behavior.

Why this answer

The strongest reason is a BPDU Guard violation on a PortFast-enabled access port. In practical terms, the port was expected to face an end host, not a switching device that emits BPDUs. When BPDUs appeared, the switch treated that as a topology-policy violation and error-disabled the interface to protect the network.

This is one of the most classic access-layer protection patterns on the CCNA exam.

Exam trap

Be careful not to confuse BPDU Guard with other port security features or network issues like duplex mismatches.

Why the other options are wrong

B

Port security restricts access based on MAC addresses, not VLANs, and the event message explicitly mentions BPDU Guard, not port security. The exhibit shows a spanning-tree BPDU Guard error, not a port security violation.

C

DHCP snooping does not cause err-disabled state due to BPDU reception; it filters DHCP messages and can disable ports for DHCP attacks, but the exhibit clearly shows a spanning-tree BPDU Guard event.

D

EtherChannel suspension occurs due to configuration mismatches or link failures, not BPDU reception. The exhibit's syslog message explicitly identifies BPDU Guard, not EtherChannel issues.

6
MCQhard

A switch port connected to an edge host immediately transitions to forwarding and then later goes err-disabled after a BPDU is received. Which feature combination most likely produced this behavior?

B.NetFlow with SNMP traps
C.OSPF passive-interface with EUI-64
D.WPA3 with CAPWAP
AnswerA

PortFast immediately moves a switchport from blocking to forwarding, bypassing the STP listening and learning states, which is exactly what an edge host needs to start communicating right away. BPDU Guard then protects that edge port by placing it in errdisable state if any BPDU is received, preventing a rogue switch from forming an unintended loop. Together, these STP edge-port protections both speed up the transition and maintain loop safety for a directly connected host.

Why this answer

The most likely combination is PortFast with BPDU Guard. In practical terms, PortFast explains why the port moved quickly into forwarding when the host connected. BPDU Guard explains why the same port later shut down after seeing a BPDU that should not normally appear on an edge port.

This is a very common enterprise edge-port design pattern and a classic exam scenario.

Exam trap

Beware of confusing BPDU Guard with other protection mechanisms like Root Guard or Loop Guard; each serves a different purpose.

Why the other options are wrong

B

NetFlow is used for traffic monitoring and analysis, while SNMP traps are used for network management notifications. Neither feature affects STP behavior or port state transitions; they do not cause a port to go err-disabled upon receiving a BPDU.

C

OSPF passive-interface prevents OSPF from sending routing updates on an interface but does not affect STP or port security. EUI-64 is used for IPv6 address generation. Neither feature relates to BPDU handling or err-disable behavior.

D

WPA3 is a wireless security protocol, and CAPWAP is a control and provisioning protocol for wireless access points. These are entirely unrelated to wired switch port STP behavior and cannot cause a port to go err-disabled due to BPDU reception.

7
Multi-Selectmedium

Which TWO statements correctly describe the behavior of Root Guard, Loop Guard, and BPDU Guard in a Rapid PVST+ environment?

Select 2 answers
A.Root Guard is applied to a port that should never become a root port; if a superior BPDU is received, the port is placed into a root-inconsistent state.
B.Loop Guard is used on root ports to monitor BPDU reception; if BPDUs stop, the port is immediately placed into forwarding mode to maintain connectivity.
C.BPDU Guard is typically configured on access ports and error-disables the port if a BPDU is received, protecting against unauthorized switch connections.
D.A port in the Root Guard root-inconsistent state is err-disabled and must be recovered manually with shutdown followed by no shutdown.
E.Loop Guard is enabled on PortFast access ports and places the port in err-disabled state when any BPDU is received.
AnswersA, C

Root Guard is placed on designated ports that should never become root ports. It allows normal BPDU processing, but if a superior BPDU (one with a lower bridge ID than the current root) is received, the port transitions to a root-inconsistent state, which blocks traffic while still listening for BPDUs. This prevents an unauthorized or misconfigured switch from becoming the spanning-tree root. Unlike BPDU Guard, the port automatically recovers once the superior BPDUs cease, without manual intervention.

Why this answer

Root Guard is applied to ports that must never become root ports; if a superior BPDU arrives, the port is put into the root-inconsistent state (blocking) and recovers automatically when the superior BPDUs stop. BPDU Guard is normally enabled on PortFast access ports and places the port in err-disabled state as soon as any BPDU is received, protecting against rogue switches. Loop Guard works on non-designated ports (root and alternate ports) and, when BPDUs stop arriving, moves the port to loop-inconsistent (blocking) instead of letting it transition to forwarding.

Root Guard does not err-disable the port, and Loop Guard does not err-disable ports on BPDU receipt.

Exam trap

Cisco often tests the misconception that Loop Guard immediately forwards traffic when BPDUs stop, but in reality it blocks the port to prevent loops, and that Root Guard and BPDU Guard can coexist on the same port, which they cannot due to conflicting behaviors.

Why the other options are wrong

B

When BPDUs stop, Loop Guard blocks the port (loop-inconsistent state); it never forces it into forwarding.

D

Root Guard recovers automatically when superior BPDUs cease; only err-disabled ports (for example from BPDU Guard) need manual or timed recovery.

E

Loop Guard reacts to the absence of BPDUs, not to receiving them; err-disabling on BPDU receipt is BPDU Guard.

8
Multi-Selectmedium

Which TWO of the following statements about Spanning Tree Protocol (STP) and Rapid PVST+ are true?

Select 2 answers
A.The root bridge in STP is elected based on the lowest bridge ID.
B.The root bridge in STP is elected based on the highest bridge ID.
C.PortFast automatically enables BPDU Guard on an interface.
D.BPDU Guard places a PortFast-enabled port into an error-disabled state if a BPDU is received.
E.Rapid PVST+ uses a different root bridge election process than traditional STP.
AnswersA, D

Spanning Tree elects the root bridge through BPDU exchange, and the switch with the lowest bridge ID becomes root. The bridge ID is an 8-byte value combining the configurable priority field and the switch's MAC address; when priorities tie, the lowest MAC address breaks the tie. This deterministic election logic is identical across traditional STP and Rapid PVST+.

Why this answer

The root bridge in STP is elected based on the numerically smallest bridge ID (priority + MAC address). Option D is correct because BPDU Guard, when enabled on a PortFast-enabled port, immediately error-disables the port if a BPDU is received, protecting against accidental loops. Option B is incorrect because the root bridge is chosen by the lowest bridge ID, not the highest.

Option C is incorrect because PortFast and BPDU Guard are independent features; PortFast does not automatically enable BPDU Guard. Option E is incorrect because both traditional STP (802.1D) and Rapid PVST+ (RSTP-based) use the same root bridge election process—lowest bridge ID.

Exam trap

Cisco often tests the misconception that PortFast and BPDU Guard are automatically linked, when in fact they are separate features that must be configured independently, and the trap is that candidates assume enabling PortFast also enables BPDU Guard.

Why the other options are wrong

B

The root bridge is elected based on the lowest bridge ID, not the highest.

C

PortFast does not automatically enable BPDU Guard; they must be configured separately.

E

Rapid PVST+ uses the same root bridge election process (lowest bridge ID) as traditional STP.

9
MCQhard

A switch port configured with PortFast and BPDU Guard receives a BPDU and transitions to an error-disabled state. Which statement best explains why this is considered useful protection?

A.It prevents a port expected to be an edge port from accidentally becoming part of the switching topology and causing loops.
B.It increases the port's bandwidth by combining multiple links.
C.It automatically enables VLAN trunking on the port.
D.It forces the port to use Rapid Spanning Tree Protocol for faster convergence.
AnswerA

PortFast is designed for edge ports that connect directly to end hosts, so it places the port into forwarding state immediately. When a BPDU is received on such a port, it means an unexpected switch connection exists, so BPDU Guard—often enabled alongside PortFast—disables the port. This prevents the port from participating in STP calculations and creating a bridging loop, while preserving the intended fast-convergence behavior for genuine edge ports.

Why this answer

PortFast is used on edge ports to bypass STP listening/learning, but if a BPDU is received, the assumption that the port is an edge port is violated. BPDU Guard then error-disables the port to prevent potential loops or topology disruptions. This protects the network when an edge port unexpectedly connects to another switch, which could cause a bridging loop.

The other options describe unrelated features or incorrect mechanisms.

Exam trap

Remember that BPDU Guard disables the port, not just logs or adjusts its role. It's a protective measure, not a monitoring tool.

Why the other options are wrong

B

Increasing port bandwidth by combining links is done via EtherChannel, not related to BPDU Guard or loop prevention.

C

VLAN trunking is automatically negotiated via DTP or manually configured, not triggered by BPDU Guard or PortFast.

D

Forcing Rapid Spanning Tree Protocol is not a function of PortFast or BPDU Guard; they are separate STP optimizations.

10
MCQhard

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

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

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

Why this answer

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

Exam trap

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

Why the other options are wrong

A

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

B

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

D

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

11
PBQhard

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

Network Topology
Gi0/1Gi0/2SW1workstationother switch

Hints

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

Why this answer

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

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

Exam trap

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

Why the other options are wrong

B

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

C

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

D

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

12
Drag & Dropmedium

Drag and drop the following steps into the correct order to configure PortFast and BPDU Guard on an access port of a Cisco IOS-XE switch and then recover the port after a BPDU Guard violation.

Drag or tap steps into the slots.

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

Why this order

Enter global configuration mode, enter the interface, enable PortFast and BPDU Guard on it, and later, when a violation puts the port in err-disabled, identify it, remove the device sending BPDUs, and bounce the port with shutdown followed by no shutdown.

Exam trap

The exam trap is that candidates may confuse the order of PortFast and BPDU Guard, or think that recovery requires a switch reload or a special clear command. Remember: PortFast first, then BPDU Guard; recovery is always 'shutdown/no shutdown' on the interface.

13
PBQhard

You are connected to R1, a multilayer switch. Interface GigabitEthernet0/1 is in the err-disabled state because of a BPDU Guard violation. Configure the switch so that ports err-disabled by BPDU Guard recover automatically after 300 seconds, and verify the setting.

Hints

  • •Automatic recovery is configured per cause in global configuration mode.
  • •show errdisable recovery shows which causes are enabled and the timer.
  • •errdisable detect only controls whether a cause is detected, not recovery.
A.errdisable recovery cause bpduguard and errdisable recovery interval 300
B.errdisable detect cause bpduguard and errdisable recovery interval 300
C.errdisable recovery interval 300 only
D.spanning-tree bpduguard disable on GigabitEthernet0/1
AnswerA
solution
! R1
configure terminal
errdisable recovery cause bpduguard
errdisable recovery interval 300
end

Why this answer

Gi0/1 is err-disabled with reason bpduguard, and the recovery table shows bpduguard Disabled, so the port never recovers by itself. Enabling errdisable recovery cause bpduguard turns on the automatic recovery for that cause, and errdisable recovery interval 300 sets the timer (300 seconds is also the default). After the interval the port is re-enabled; if the BPDU source is still connected it will be err-disabled again.

Exam trap

The trap is that candidates may confuse enabling BPDU guard with configuring recovery, or they may think recovery commands are applied per-interface. Remember that errdisable recovery is a global setting, and you must specify the exact cause unless you want to recover from all causes.

Why the other options are wrong

B

Incorrect: detect only controls detection of the cause; recovery for bpduguard stays disabled.

C

Incorrect: the timer is set, but no cause is enabled for recovery, so the port stays err-disabled.

D

Incorrect: this removes the protection instead of configuring recovery and does not fit the requirement.

14
Multi-Selectmedium

Which TWO statements correctly describe the behavior of PortFast and BPDU Guard on a Cisco switch?

Select 2 answers
A.PortFast immediately transitions a port from blocking to forwarding state, bypassing listening and learning.
B.BPDU Guard disables a PortFast-enabled port if it receives any BPDU.
C.PortFast allows BPDUs to pass through the port normally, but the port remains in forwarding state.
D.BPDU Guard prevents the port from becoming a root port or designated port by ignoring superior BPDUs.
E.BPDU Guard is typically configured on trunk ports to prevent loops between switches.
AnswersA, B

PortFast is a feature applied to access ports connecting end hosts, allowing the port to skip the listening and learning states and transition directly from blocking to forwarding. This reduces the time a host takes to start sending traffic by avoiding the 30-second STP convergence delay. It does not disable STP; the switch still participates in STP but the port is forwarding immediately.

Why this answer

PortFast immediately transitions an access port from blocking to forwarding, bypassing listening and learning (Option A). BPDU Guard errdisables a PortFast-enabled port if any BPDU is received, protecting against accidental loops (Option B). Option C is incorrect because PortFast does not alter BPDU handling; the port still processes BPDUs and reverts to normal STP if one is received.

Option D is false because BPDU Guard disables the port entirely rather than ignoring BPDUs. Option E is incorrect because BPDU Guard is typically configured on access ports connected to end devices, not on trunk ports.

Exam trap

Cisco often tests the misconception that PortFast itself blocks or filters BPDUs, when in fact it only accelerates the transition to forwarding; BPDU Guard is a separate feature that must be explicitly enabled to disable the port upon BPDU reception.

Why the other options are wrong

C

PortFast does not filter BPDUs; it still processes them normally. If a BPDU is received on a PortFast port, the port will still participate in STP and may transition to a blocking state, defeating the purpose of PortFast. The statement incorrectly claims BPDUs pass through while the port remains forwarding, which is not true.

D

BPDU Guard does not affect STP election processes; it simply err-disables the port upon receiving any BPDU. It does not ignore superior BPDUs or prevent the port from becoming a root or designated port. That behavior is associated with Root Guard, not BPDU Guard.

E

BPDU Guard is intended for access ports with PortFast, not for trunk ports. Trunk ports between switches are expected to exchange BPDUs for normal STP operation; applying BPDU Guard on a trunk would cause the port to err-disable upon receiving legitimate BPDUs, disrupting the network.

15
MCQhard

A network engineer notices that a root port on a switch has transitioned to a loop-inconsistent state. The port was previously receiving BPDUs normally, but after a suspected unidirectional fiber cut, it no longer receives BPDUs. What is the most likely cause?

A.BPDU Guard is enabled on the port, causing it to be placed in error-disabled state.
B.Loop Guard is active on the root port and transitioned it to loop-inconsistent state upon BPDU loss.
C.UDLD has detected a unidirectional link and has shut down the port.
D.Root Guard is preventing the port from transitioning to designated forwarding after losing BPDUs.
AnswerB

Loop Guard is precisely designed to monitor BPDU reception on blocked or alternate ports. When a unidirectional link failure occurs and BPDUs are no longer received, Loop Guard places the port into the loop-inconsistent state, blocking all traffic to prevent a potential loop. The 'loop-inconsistent' state is a clear indicator of this feature.

Why this answer

Loop Guard is a Spanning Tree Protocol (STP) enhancement that prevents alternate or root ports from becoming designated forwarding ports when BPDUs are no longer received. When a unidirectional fiber cut causes BPDU loss on a root port, Loop Guard transitions the port to the loop-inconsistent state, blocking traffic until BPDUs are received again. This matches the scenario exactly, making option B correct.

Exam trap

Cisco often tests the distinction between Loop Guard (reacts to BPDU loss) and UDLD (detects unidirectional links via proprietary keepalives), where candidates mistakenly choose UDLD because the question mentions a unidirectional fiber cut, but the key clue is the specific 'loop-inconsistent' state, which is unique to Loop Guard.

Why the other options are wrong

A

BPDU Guard is a protective feature that disables a port upon receiving a BPDU, not upon losing BPDUs. The symptom here is a loss of BPDUs, not a reception of unexpected BPDUs.

C

UDLD acts by shutting down the port or putting it in errdisable state, while the scenario explicitly shows the port in a loop-inconsistent state, indicating an STP-based protection mechanism.

D

Root Guard would block a port if it received a BPDU with better root information, not when BPDUs stop arriving. It also does not produce a loop-inconsistent state.

16
PBQhard

You are connected to R1, an access-layer switch. GigabitEthernet0/2 is its root port toward the core, GigabitEthernet0/1 is a designated trunk toward downstream switch R2, and GigabitEthernet0/3 is a PortFast access port. Root Guard is already configured on G0/1 and BPDU Guard on G0/3. Configure Loop Guard on the uplink G0/2, and recover G0/3, which was err-disabled when an unauthorized device sent a BPDU. Interpret the output to explain the state of G0/1.

Hints

  • •Root Guard moves a port to root-inconsistent when it hears a superior BPDU and recovers automatically when they stop.
  • •Loop Guard is enabled per interface with spanning-tree guard loop.
  • •An err-disabled port must be shut down and re-enabled after the cause is removed.
A.On G0/2 enter spanning-tree guard loop; on G0/3 remove the unauthorized device, then enter shutdown and no shutdown.
B.On G0/2 enter spanning-tree guard root; on G0/3 enter shutdown and no shutdown.
C.On G0/2 enter spanning-tree guard loop; on G0/3 enter only no shutdown.
D.On G0/2 enter spanning-tree guard loop; on G0/3 enter spanning-tree bpdufilter enable.
AnswerA
solution
! R1
configure terminal
interface GigabitEthernet0/2
spanning-tree guard loop
interface GigabitEthernet0/3
shutdown
no shutdown
end

Why this answer

Gi0/1 is root-inconsistent because it received a superior BPDU; Root Guard blocks the port and it recovers on its own once superior BPDUs stop, so nothing needs to be configured. Loop Guard is enabled on the root-port uplink with spanning-tree guard loop on Gi0/2 (loop guard applies to root and alternate ports, not designated ports). Gi0/3 is err-disabled because of BPDU Guard; remove the unauthorized device and bounce the port with shutdown followed by no shutdown.

Exam trap

Do not confuse the actions of Root Guard (blocking) with BPDU Guard (err-disable). Root Guard blocks the port temporarily; BPDU Guard err-disables the port until manual intervention. Also, Loop Guard does not block immediately; it only reacts when BPDUs stop.

Why the other options are wrong

B

Incorrect: Root Guard on the root port would block the path toward the real root, and the requirement is Loop Guard.

C

Incorrect: an err-disabled port must be shut down first and then re-enabled; no shutdown alone does not recover it.

D

Incorrect: BPDU filter suppresses BPDUs and removes the protection, and it does not recover the err-disabled port.

17
Drag & Dropmedium

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

Drag or tap steps into the slots.

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

Why this order

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

18
MCQhard

A technician is troubleshooting a network-wide broadcast storm. BPDU guard is globally enabled ('spanning-tree portfast bpduguard default') on the access switch, yet no ports are in the err-disabled state. A rogue switch was found plugged into an access port. The technician examines the configuration of the access ports shown in the exhibit. What is the most likely cause?

A.Spanning tree is disabled globally, allowing the rogue switch to create a loop.
B.BPDU guard is misconfigured on the wrong ports, so it failed to block the rogue switch.
C.Root guard is incorrectly enabled on the access ports, causing the rogue switch to become the root bridge.
D.BPDU filter is enabled on the access interface, so BPDUs are neither sent nor processed and BPDU guard never triggers.
AnswerD

Interface-level 'spanning-tree bpdufilter enable', shown in the exhibit, stops BPDU transmission and ignores received BPDUs. Because the rogue switch's BPDUs are ignored, BPDU guard never puts the port in err-disabled, allowing a loop and a broadcast storm.

Why this answer

An interface-level 'spanning-tree bpdufilter enable' stops the port from sending and processing BPDUs and takes precedence over BPDU guard. The rogue switch's BPDUs are ignored, so BPDU guard never err-disables the port and the loop and broadcast storm go undetected.

Exam trap

BPDU guard only works if the port processes the BPDU. Interface-level BPDU filter ignores received BPDUs, so guard never triggers. This differs from global BPDU filter, which removes the filter as soon as a BPDU arrives.

Why the other options are wrong

A

This answer assumes STP is off entirely, but the presence of BPDU guard configuration indicates spanning tree is operational.

B

Candidates often assume that BPDU guard simply failed, overlooking the interaction with BPDU filter, which can neutralize guard by suppressing BPDUs.

C

Root guard is a different feature and not related to the suppression of BPDUs that would allow a loop to form undetected.

19
PBQhard

You are securing the spanning-tree topology on R1, an access switch. Gi1/0/1 is its root port and Gi1/0/2 its alternate port toward the core, Gi1/0/3 is a designated port toward a downstream switch with Root Guard, and Gi1/0/5 is a PortFast desktop port with BPDU Guard. A superior BPDU has blocked Gi1/0/3 (expected), and a device on Gi1/0/5 sent a BPDU and err-disabled the port (expected). Loop Guard was never applied to the uplinks. Apply the missing configuration and recover the err-disabled port.

Hints

  • •Root Guard blocks a port that receives a superior BPDU and releases it automatically when they stop.
  • •Loop Guard protects root and alternate ports and is enabled with spanning-tree guard loop.
  • •An err-disabled port is recovered after removing the cause with shutdown followed by no shutdown.
A.On Gi1/0/1 and Gi1/0/2 enter spanning-tree guard loop; on Gi1/0/5 remove the device sending BPDUs, then enter shutdown and no shutdown.
B.On Gi1/0/1 and Gi1/0/2 enter spanning-tree guard root; on Gi1/0/5 enter shutdown and no shutdown.
C.On Gi1/0/3 enter no spanning-tree guard root; on Gi1/0/5 enter no shutdown only.
D.On Gi1/0/1 and Gi1/0/2 enter spanning-tree guard loop; on Gi1/0/5 enter spanning-tree bpdufilter enable.
AnswerA
solution
! R1
configure terminal
interface GigabitEthernet1/0/1
spanning-tree guard loop
interface GigabitEthernet1/0/2
spanning-tree guard loop
interface GigabitEthernet1/0/5
shutdown
no shutdown
end

Why this answer

Gi1/0/3 is blocked by Root Guard (*ROOT_Inc) because it received a superior BPDU; it recovers automatically once superior BPDUs stop. Loop Guard is meant for root and alternate ports, so spanning-tree guard loop is configured on the uplinks Gi1/0/1 (root) and Gi1/0/2 (alternate). Gi1/0/5 is err-disabled by BPDU Guard; after removing the device sending BPDUs, bounce the port with shutdown and no shutdown.

Exam trap

Do not assume that a blocked port due to Root Guard is a problem; it is intentional. Also, do not confuse BPDU Guard with BPDU Filter; BPDU Guard err-disables, while BPDU Filter suppresses BPDUs. Remember that err-disabled ports must be manually re-enabled with 'no shutdown'.

Why the other options are wrong

B

Incorrect: Root Guard on the uplinks toward the root would block the path to the real root; Loop Guard is required.

C

Incorrect: the Gi1/0/3 blocking is expected, and no shutdown alone does not recover an err-disabled port.

D

Incorrect: BPDU filter removes the BPDU Guard protection and does not recover the err-disabled port.

20
MCQhard

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

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

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

Why this answer

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

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

Exam trap

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

Why the other options are wrong

A

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

B

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

C

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

21
MCQmedium

When spanning tree elects a root bridge, which value is considered first?

A.Lowest MAC address only
B.Lowest bridge priority only
C.Lowest bridge ID, which begins with priority
D.Highest interface bandwidth
AnswerC

In STP, the root bridge is elected by comparing the 8-byte bridge ID (BID), which is formed by a 2-byte priority value followed by the 6-byte MAC address. The lowest BID wins, and because priority occupies the most significant bytes, a switch with a lower priority always beats a switch with a higher priority. Only when priorities are identical does the MAC address become the tiebreaker within the same BID comparison. Thus the actual election value is the full bridge ID, beginning with priority.

Why this answer

The root bridge is the switch with the lowest bridge ID. The bridge ID is made up of priority and MAC address, so priority is considered first, then MAC address if priorities tie.

Exam trap

Remember that the bridge priority is evaluated before the MAC address in the root bridge election process.

Why the other options are wrong

A

The MAC address is only used as a tiebreaker when bridge priorities are equal. It is not the first value considered in root bridge election.

B

The bridge priority is only the first part of the bridge ID; the full bridge ID (priority + MAC address) is compared. If priorities are equal, the MAC address is used as a tiebreaker.

D

Interface bandwidth is used to calculate path cost, which influences port roles (root port, designated port) but does not affect root bridge election. Root bridge election is based solely on bridge ID.

22
MCQhard

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

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

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

Why this answer

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

Exam trap

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

Why the other options are wrong

A

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

B

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

C

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

23
MCQhard

A network administrator implements a set of spanning-tree enhancements to secure the switching infrastructure. Later, a help desk ticket reports that a user in a remote office cannot connect to any network resources. While investigating, the administrator notices that the switch port connecting the remote office switch to the distribution switch is in a 'root-inconsistent' state and is blocking traffic. Which protection feature, if misapplied, most likely caused this issue?

AnswerB

Root Guard ensures that a port cannot become a root port. When a superior BPDU is received on a Root Guard-enabled port, the port transitions to a root-inconsistent state and blocks traffic, exactly as described in the scenario.

Why this answer

Root Guard is the correct answer because it forces an interface to be a designated port. If a switch receives a superior BPDU (indicating a root bridge with a lower bridge ID) on a Root Guard-enabled port, the port is placed into a 'root-inconsistent' state and blocks traffic to prevent the attached switch from becoming the root bridge. This matches the symptom described: a port in 'root-inconsistent' state blocking traffic after spanning-tree enhancements were applied.

Exam trap

Cisco often tests the distinction between 'root-inconsistent' (Root Guard) and 'loop-inconsistent' (Loop Guard) states, and the trap here is that candidates confuse the two or assume BPDU Guard is responsible for any BPDU-related blocking.

Why the other options are wrong

A

A loop-inconsistent state is different from the root-inconsistent state observed. Loop Guard acts when BPDUs stop arriving, not when they appear with a superior root claim.

C

While BPDU Guard also reacts to incoming BPDUs, it puts the port in err-disabled (shutdown) state, not a blocking state named 'root-inconsistent'. The symptom described is not error-disabled.

D

BPDU Filter would not cause the port to show a root-inconsistent state. The symptom is a protective blocking state, which BPDU Filter does not provide.

24
Drag & Dropmedium

Drag and drop the following steps into the correct order to recover an access port with PortFast and BPDU Guard that was placed in err-disabled state because an unauthorized switch was connected.

Drag or tap steps into the slots.

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

Why this order

First identify the err-disabled port (show interfaces status err-disabled). Then remove the cause, the unauthorized switch sending BPDUs; if the cause is not removed, the port would immediately err-disable again. Next bounce the port with shutdown followed by no shutdown (the port must be shut down before it is re-enabled), and finally verify that the port is connected.

Exam trap

The exam trap is confusing which protection goes on which port role. Remember: Root Guard protects designated ports from becoming root; Loop Guard protects non-designated ports from becoming forwarding; BPDU Guard protects PortFast ports. Also, recovery order: global first, then interface re-enable.

25
MCQhard

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

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

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

Why this answer

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

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

Exam trap

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

Why the other options are wrong

A

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

C

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

D

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

26
MCQhard

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

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

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

Why this answer

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

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

Exam trap

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

Why the other options are wrong

B

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

C

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

D

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

27
MCQmedium

A user reports that their desk port stopped working immediately after they connected a small switch. The interface shows err-disabled, and the log mentions BPDU Guard. What most likely happened?

A.The port received a BPDU and BPDU Guard shut it down.
B.DHCP snooping blocked the user's ARP requests.
C.Port security moved the port to protect mode.
D.The trunk native VLAN matched incorrectly.
AnswerA

BPDU Guard on a PortFast-enabled edge port immediately err-disables the interface upon receiving any BPDU, typically from an unauthorized switch. This matches the symptom of a desk port stopping right after connection, and the log would explicitly show 'bpduguard error detected' putting the port in err-disable state.

Why this answer

BPDU Guard is commonly enabled on PortFast access ports to protect the topology. If the port receives a BPDU, the switch assumes another switch may have been connected and places the port into err-disabled state. That is exactly the protective behavior you want at the edge.

Exam trap

A frequent exam trap is mistaking BPDU Guard triggers for issues caused by DHCP snooping or port security. Candidates may incorrectly assume that DHCP snooping blocking ARP or port security violations cause the err-disabled state when the log explicitly mentions BPDU Guard. Another pitfall is confusing native VLAN mismatches on trunks as the cause, but these do not generate BPDU Guard errors.

The key is to recognize that BPDU Guard specifically responds to receiving BPDUs on PortFast-enabled ports, which signals an unexpected switch connection and leads to err-disable. Misreading the log or symptoms can lead to selecting incorrect answers that do not align with BPDU Guard’s function.

Why the other options are wrong

B

Incorrect. DHCP snooping blocks unauthorized DHCP messages but does not cause BPDU Guard to err-disable a port. The log specifically mentions BPDU Guard, so DHCP snooping is unrelated here.

C

Incorrect. Port security violations cause err-disable states but are triggered by MAC address violations, not by receiving BPDUs. The log message points to BPDU Guard, not port security.

D

Incorrect. A trunk native VLAN mismatch causes VLAN tagging issues but does not trigger BPDU Guard or err-disable a port due to BPDU reception. This option does not explain the BPDU Guard log message.

28
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.

29
MCQhard

A network administrator is troubleshooting connectivity loss in a switched network. All switches run Rapid PVST+. A host connected to an access port on SwitchC can no longer reach the default gateway. The access port is configured with PortFast and BPDU Guard. The administrator checks the interface status and finds it in an err-disabled state. What is the most likely cause of this issue?

A.The root bridge election failed, causing a loop.
B.BPDU Guard detected a BPDU on a PortFast-enabled port and disabled it.
C.Rapid PVST+ is not compatible with PortFast.
D.The port is configured as a trunk but should be an access port.
AnswerB

BPDU Guard is a security feature that monitors PortFast-enabled ports for incoming BPDUs. When a BPDU is received, it immediately transitions the port to err-disabled state to prevent a potential switching loop, as a valid access port should never receive BPDUs. This exactly matches the symptom: Gi0/1 is down/err-disabled after BPDU Guard was enabled. The port will remain disabled until manually re-enabled or errdisable recovery is configured.

Why this answer

B is correct because BPDU Guard is designed to protect the spanning-tree topology by disabling a PortFast-enabled port if it receives a BPDU, placing the port in err-disabled state. Option A is incorrect: a root bridge election failure would not cause a port to err-disable; loops do not directly trigger this state without BPDU Guard. Option C is incorrect because PortFast and BPDU Guard work with all spanning-tree variants including Rapid PVST+.

Option D is incorrect: a trunk misconfiguration alone would not cause err-disable unless BPDU Guard detects a BPDU on a PortFast port.

Exam trap

Cisco often tests the misconception that PortFast and BPDU Guard are incompatible with Rapid PVST+, but in reality, PortFast is a port-level feature that works identically across all spanning-tree variants, and BPDU Guard is the mechanism that causes the err-disabled state when a BPDU is received.

Why the other options are wrong

A

A root bridge election failure would not place the port in err-disabled state; it would cause loops but not trigger BPDU Guard directly.

C

PortFast and BPDU Guard are fully compatible with Rapid PVST+; this option implies incompatibility, which is incorrect.

D

A trunk misconfiguration alone would not cause the port to go err-disable unless a BPDU is received on a PortFast-enabled port, and BPDU Guard is the specific mechanism for that.

30
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.

31
Multi-Selectmedium

Which TWO statements correctly describe the configuration and effect of Root Guard and BPDU Guard on a Cisco switch?

Select 2 answers
A.Root Guard is configured on a per-port basis and causes the port to become root-inconsistent if a superior BPDU is received.
B.BPDU Guard prevents loops by disabling a trunk port that receives a BPDU from an unauthorized switch.
C.Root Guard places a port in errdisable state when a superior BPDU is received.
D.BPDU Guard is commonly enabled on ports where PortFast is configured to prevent unexpected BPDUs from causing a bridging loop.
E.Both Root Guard and BPDU Guard filter BPDUs to prevent them from being processed by the switch CPU.
AnswersA, D

Root Guard is configured per interface, usually on designated ports, to enforce the current root bridge location. When a port receives a superior BPDU, Root Guard changes the port to a root-inconsistent state, which is a blocking state for all traffic. This prevents an unauthorized switch from taking over as root, and the port resumes normal forwarding automatically after the superior BPDUs cease. It does not require errdisable or manual recovery, as it is not a security violation.

Why this answer

Root Guard is configured per interface using the 'spanning-tree guard root' command. When a port with Root Guard enabled receives a superior BPDU (one that would cause the switch to become a non-root bridge), the port is placed into a root-inconsistent state, effectively blocking traffic on that port and preventing the switch from accepting a new root bridge from that direction. This protects the spanning-tree topology from unauthorized or misconfigured switches attempting to become the root bridge.

Option D is correct because BPDU Guard is commonly enabled on ports with PortFast (typically access ports connected to end devices). When a BPDU is received on such a port, BPDU Guard places the port into errdisable state, preventing potential bridging loops that could result from an unauthorized switch connecting to the network. Option B is incorrect because BPDU Guard does not prevent loops by disabling a trunk port; it is typically used on access ports (often with PortFast) and disables the port upon receiving any BPDU, not just on trunk ports.

Option C is incorrect because Root Guard places the port into root-inconsistent state (not errdisable) when a superior BPDU is received; BPDU Guard uses errdisable. Option E is incorrect because neither Root Guard nor BPDU Guard filters BPDUs; Root Guard reacts to superior BPDUs by blocking the port, and BPDU Guard reacts to any BPDU by disabling the port. Both features allow BPDUs to be processed but then take action based on the received BPDUs.

Exam trap

Cisco often tests the distinction between the states triggered by Root Guard (root-inconsistent) versus BPDU Guard (errdisable), and candidates frequently confuse the two, assuming both place the port into errdisable or that Root Guard uses errdisable.

Why the other options are wrong

B

BPDU Guard does not prevent loops by disabling a trunk port; it is typically used on access ports with PortFast and disables the port upon receiving any BPDU.

C

Root Guard places the port into root-inconsistent state, not errdisable; errdisable is the state used by BPDU Guard.

E

Neither Root Guard nor BPDU Guard filters BPDUs; they both process received BPDUs and then take action (root-inconsistent for Root Guard, errdisable for BPDU Guard).

32
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.

33
MCQhard

A switch receives BPDUs on a user-facing port configured as an edge port, but instead of just blocking the port role it fully error-disables it. Which protection feature most likely explains that behavior?

AnswerA

BPDU Guard is a security feature designed for edge or access ports, typically used with PortFast. When a port configured with BPDU Guard receives any BPDU, it immediately transitions to the err-disabled state, because an unexpected BPDU indicates that a switch or bridge is connected to an end-user segment. This prevents the possibility of a bridging loop caused by a rogue switch and does not require manual intervention beyond the initial configuration, though recovery can be automatic if err-disable timeout is set.

Why this answer

BPDU Guard most likely explains that behavior. In practical terms, BPDU Guard is used to protect ports that are expected to face ordinary endpoints, not other switches. If BPDUs appear on such a port, the device treats that as a serious topology-policy violation and shuts the port down.

This is different from features that merely influence spanning-tree role choice without fully error-disabling the interface.

Exam trap

Be careful not to confuse BPDU Guard with other spanning tree protection features that do not disable ports upon receiving BPDUs.

Why the other options are wrong

B

Root guard does not error-disable a port; instead, it places the port into a root-inconsistent state if a superior BPDU is received, preventing the port from becoming a root port. It is used to enforce the root bridge location, not to disable ports upon BPDU reception.

C

Port security restricts the number of MAC addresses learned on a port and can error-disable the port if a violation occurs (e.g., too many MAC addresses). It does not react to BPDUs; its focus is on MAC address learning, not spanning-tree BPDUs.

D

DHCP snooping is a security feature that filters DHCP messages and can error-disable a port if a DHCP violation occurs (e.g., rogue DHCP server). It does not inspect or react to BPDUs, which are layer 2 spanning-tree frames.

34
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.

35
PBQeasy

You are connected to SW1 via the console. SW1 is a Layer 2 switch with an access port G0/1 connected to a server. The network administrator has noticed that the server is sending BPDUs, which could cause network instability. You need to configure PortFast and BPDU Guard on port G0/1 to prevent BPDU-related issues and ensure the port transitions to forwarding state immediately.

Network Topology
G0/1ServerSW1

Hints

  • •PortFast enables immediate transition from blocking to forwarding state.
  • •BPDU Guard disables the port if a BPDU is received.
  • •These features are typically applied to access ports connected to end devices.
A.interface G0/1 spanning-tree portfast spanning-tree bpduguard enable
B.interface G0/1 spanning-tree portfast spanning-tree guard root
C.interface G0/1 spanning-tree portfast spanning-tree bpdufilter enable
D.interface G0/1 spanning-tree portfast spanning-tree bpduguard default
AnswerA
solution
! SW1
interface GigabitEthernet0/1
spanning-tree portfast
spanning-tree bpduguard enable

Why this answer

PortFast allows an access port to bypass STP listening/learning states, providing immediate connectivity. BPDU Guard protects the network by shutting down the port if a BPDU is received, preventing potential loops from unauthorized switches.

Exam trap

Cisco exams often test the exact syntax for STP features. Remember that BPDU Guard uses 'enable' at the interface level, while BPDU Filter uses 'enable' as well. Root Guard uses 'guard root'.

Do not confuse these or use global commands on interfaces.

Why the other options are wrong

B

The specific factual error is confusing Root Guard with BPDU Guard. Root Guard is used to enforce the root bridge position, not to protect against BPDUs.

C

The specific factual error is that BPDU Filter silently drops BPDUs instead of taking action, which can allow loops to form if an unauthorized switch is connected.

D

The specific factual error is using the global configuration command on an interface. The global command enables BPDU Guard on all PortFast-enabled ports, but the question asks to configure it on a specific port.

36
MCQmedium

Why is BPDU Guard commonly enabled on PortFast-enabled access ports?

A.To make STP root election happen faster
B.To disable STP permanently on access ports
C.To err-disable a port if it receives unexpected BPDUs
D.To allow only one MAC address on the access port
AnswerC

BPDU Guard is a protective feature used with PortFast on access ports to prevent loops from unauthorized BPDUs. If the port receives any BPDU, which should not occur on an end-node connection, the switch immediately err-disables the interface to stop potential bridging loops. This safeguards the network from misconfigured or malicious devices.

Why this answer

PortFast ports are meant for end devices, not for switches. BPDU Guard protects the LAN by shutting down a PortFast port that unexpectedly starts receiving BPDUs, which usually means an unauthorized switch was connected.

Exam trap

Don't confuse BPDU Guard with PortFast or BPDU filtering; each has distinct roles.

Why the other options are wrong

A

BPDU Guard is a security feature that err-disables a port upon receiving BPDUs; it does not accelerate root election. Root election speed is influenced by STP timers and bridge priorities, not BPDU Guard.

B

BPDU Guard does not disable STP permanently; it only reacts to BPDU reception by err-disabling the port. STP remains active on other ports, and the port can be re-enabled after the violation is resolved.

D

Limiting MAC addresses on a port is the function of port security, not BPDU Guard. BPDU Guard specifically monitors for BPDU frames and takes action if any are received.

37
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.

38
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.

39
MCQhard

A network administrator notices that a switch port connecting to an end-user workstation is flapping between up and down states. The port is configured with PortFast and BPDU Guard. The workstation is replaced with a small unmanaged switch that begins sending BPDUs. What is the expected result on the switch port?

A.The port enters the err-disabled state because BPDU Guard detects the BPDU on a PortFast-enabled port.
B.The port transitions to the blocking state but remains administratively up.
C.The port remains in the forwarding state and simply logs a syslog message about the BPDU.
D.The port automatically becomes a trunk and negotiates with the unmanaged switch.
AnswerA

BPDU Guard is designed to shut down a PortFast-enabled port if it receives a BPDU, which indicates an unauthorized switch is connected. When the unmanaged switch sends BPDUs, the port violates the guard condition and transitions to err-disabled, protecting the spanning-tree topology from potential loops.

Why this answer

BPDU Guard protects PortFast ports by err-disabling them when a BPDU is received. A PortFast port is meant for end hosts, so BPDUs indicate an unauthorized switch, and the guard action prevents a potential Layer 2 loop. The port becomes err-disabled rather than blocking, and it stays down until an administrator recovers it or err-disable recovery is configured.

Exam trap

The trap here is believing BPDU Guard blocks the port in STP terms, when it actually places the interface into the err-disabled state.

40
MCQeasy

What problem does Spanning Tree Protocol solve in a switched network?

A.IP address exhaustion
B.Layer 2 switching loops
C.Slow DNS lookups
D.Weak wireless encryption
AnswerB

Spanning Tree Protocol (IEEE 802.1D) eliminates Layer 2 switching loops by placing redundant switch ports in a blocking state, leaving a single active loop-free path between hosts. Without STP, broadcast frames cycle endlessly, creating broadcast storms, MAC address flapping, and duplicated unicast frames that severely degrade the switching fabric. Redundant links remain available and are activated automatically if the primary path fails.

Why this answer

STP prevents Layer 2 loops by blocking redundant paths when necessary, which avoids broadcast storms and MAC table instability.

Exam trap

Avoid confusing STP with technologies like EtherChannel, IPsec, or QoS, which address different network concerns.

Why the other options are wrong

A

Spanning Tree Protocol (STP) operates at Layer 2 and has no mechanism to manage or allocate IP addresses; IP address exhaustion is addressed by protocols like DHCP or IPv6 transition technologies.

C

DNS lookups are application-layer processes that rely on IP connectivity and name resolution servers; STP does not influence DNS performance or resolution speed.

D

Wireless encryption is a security feature implemented at the data link layer (e.g., WPA2/3) and is unrelated to STP, which deals with physical topology loop prevention.

41
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.

42
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.

43
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.

44
MCQhard

A switch receives superior BPDUs on a port where the design requires that no downstream device ever become the root path for that segment. Which feature is the best fit for that requirement?

AnswerA

Root guard is the correct STP protection mechanism for this scenario. When a port configured with root guard receives a superior BPDU (one advertising a better bridge ID or lower root path cost), it transitions the port to a root-inconsistent state, effectively blocking it. This prevents the port from becoming a root port and stops an unauthorized switch from hijacking the root bridge role, thereby preserving the intended spanning-tree topology.

Why this answer

Root guard is the best fit because it is designed to prevent a port from becoming the path toward a new root bridge when superior BPDUs are received. In practical terms, it protects the intended STP topology by keeping that port from taking on a root-related forwarding role when the design says it should not.

This is different from BPDU Guard, which is more commonly used on edge ports to disable them entirely if BPDUs appear. Root guard is about protecting topology roles, not just edge-port assumptions.

Exam trap

A common exam trap is selecting BPDU guard instead of root guard because both involve BPDU handling. BPDU guard disables a port immediately upon receiving any BPDU, which is suitable for edge ports but not for ports where topology control is required. Root guard, on the other hand, only blocks ports that receive superior BPDUs, allowing normal BPDUs from the current root bridge.

Confusing these features can lead to incorrect answers, as BPDU guard does not protect the root path role but rather protects against unauthorized devices on edge ports.

Why the other options are wrong

B

BPDU guard is incorrect because it disables a port upon receiving any BPDU, which is suitable for edge ports but does not control root path roles or topology changes.

C

Port security is unrelated to STP root path control; it manages MAC address access on a port and does not affect BPDU processing or root bridge election.

D

DHCP snooping protects against rogue DHCP servers by filtering DHCP messages and does not interact with STP or root bridge election mechanisms.

45
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.

46
PBQhard

You are connected to a multilayer switch MLS1. Configure Root Guard on switchport GigabitEthernet 0/1 (connected to an unauthorized switch) so that if a superior BPDU is received, the port is blocked instead of causing a topology change. Also enable Loop Guard on uplink GigabitEthernet 0/2 (connected to the root bridge) to prevent unidirectional link issues. Finally, enable BPDU Guard on PortFast-enabled access port GigabitEthernet 0/3 (connected to a host) so that if a BPDU is received, the port goes err-disabled. After configuration, a superior BPDU is received on G0/1 and the port is blocked; a BPDU is received on G0/3 and the port goes err-disabled. Verify these protections are active.

Hints

  • •Root Guard is configured per interface under interface configuration mode using 'spanning-tree guard root'.
  • •Loop Guard is configured per interface using 'spanning-tree guard loop'.
  • •BPDU Guard is enabled on PortFast ports with 'spanning-tree bpduguard enable'.
A.Root Guard on G0/1, Loop Guard on G0/2, BPDU Guard on G0/3
B.Root Guard on G0/1, UplinkFast on G0/2, BPDU Guard on G0/3
C.BPDU Guard on G0/1, Loop Guard on G0/2, Root Guard on G0/3
D.Root Guard on G0/1, Loop Guard on G0/2, PortFast on G0/3
AnswerA
solution
! MLS1
interface GigabitEthernet0/1
spanning-tree guard root
interface GigabitEthernet0/2
spanning-tree guard loop
interface GigabitEthernet0/3
spanning-tree portfast
spanning-tree bpduguard enable

Why this answer

Root Guard (spanning-tree guard root) on G0/1 places the port in the root-inconsistent state when a superior BPDU arrives, so the unauthorized switch cannot become root. Loop Guard (spanning-tree guard loop) on the uplink G0/2 prevents a port from moving to forwarding when BPDUs stop arriving (unidirectional link). BPDU Guard (spanning-tree bpduguard enable) on PortFast port G0/3 err-disables the port if a BPDU is received.

To restore G0/3, remove the BPDU source and use shutdown followed by no shutdown. Verify with show spanning-tree inconsistentports and show interfaces status err-disabled.

Exam trap

Trap: Mixing up which protection goes where. Root Guard is for ports that should never become root (e.g., facing unauthorized switches). Loop Guard is for ports that are alternate or root ports (uplinks).

BPDU Guard is for PortFast-enabled access ports. Also, remember that BPDU Guard triggers err-disable, while Root Guard triggers root-inconsistent (blocking) state.

Why the other options are wrong

B

UplinkFast is not designed to detect or prevent unidirectional links; it only accelerates failover.

C

The protections are applied to the wrong ports: BPDU Guard should be on access ports, Root Guard on ports facing potential rogue switches, and Loop Guard on uplinks.

D

PortFast does not prevent BPDU reception; it only skips the listening and learning states. Without BPDU Guard, the port would still process BPDUs and could become a root port.

47
MCQhard

Exhibit: SW2 receives superior BPDUs on both uplinks. One uplink becomes the root port and the other becomes alternate. Which factor is considered first when SW2 chooses the root port?

A.Lowest local interface MAC address
B.Lowest root path cost
C.Highest duplex setting
D.Lowest configured VLAN number
AnswerB

The spanning-tree root port election first compares the cumulative root path cost advertised in each received BPDU. The port with the lowest root path cost to the root bridge is selected as the root port, because it offers the most efficient shortest path toward the root. Only when costs are equal does STP proceed to other tie-breakers such as the sender bridge ID and sender port ID.

Why this answer

STP chooses the best path to the root bridge based first on the lowest root path cost. If the cost ties, it then checks the sender bridge ID and sender port ID as tie-breakers.

Exam trap

Remember that STP prioritizes root path cost first, not bridge or port IDs. Misunderstanding the order of evaluation can lead to incorrect answers.

Why the other options are wrong

A

This option is wrong because the selection of the root port is based on the lowest root path cost, not the local interface MAC address. The MAC address is not a factor in determining the root port in the Spanning Tree Protocol (STP) process.

C

This option is wrong because the selection of the root port in Spanning Tree Protocol (STP) is based on the lowest root path cost, not the duplex settings of the interfaces. Duplex settings do not influence the port selection process in STP.

D

The lowest configured VLAN number is not a factor in determining the root port in Spanning Tree Protocol (STP). The selection process prioritizes path cost, not VLAN configuration.

48
MCQmedium

Which spanning-tree port role receives the best BPDU toward the root bridge on a nonroot switch?

A.Designated port
B.Alternate port
C.Root port
D.Disabled port
AnswerC

The root port is the switch port with the lowest path cost to the root bridge, making it the interface that receives the best BPDU (lowest root ID, lowest cost, etc.) on a non-root switch. It is the only port role that actively forwards traffic toward the root bridge, and its selection is based on superior spanning tree information. This port is the single forwarding path to the root, which directly matches the question's requirement of receiving the best BPDU toward the root.

Why this answer

The root port is the port on a nonroot switch with the lowest path cost to the root bridge.

Exam trap

Be careful not to confuse port roles. Remember, the root port is specifically for receiving the best BPDU toward the root bridge, not for forwarding or redundancy.

Why the other options are wrong

A

The designated port is responsible for forwarding traffic to and from a network segment and does not receive the best BPDU toward the root bridge; instead, it sends BPDUs to other ports. Therefore, it cannot be the correct answer for identifying the port role that receives the best BPDU on a nonroot switch.

B

The alternate port does not receive the best BPDU toward the root bridge; instead, it serves as a backup path to the root bridge when the primary path fails. It is in a blocking state and does not forward traffic.

D

A Disabled port does not participate in the Spanning Tree Protocol (STP) and does not receive any BPDUs, making it incapable of receiving the best BPDU toward the root bridge.

49
Multi-Selectmedium

Which TWO of the following statements accurately describe the configuration and behavior of Root Guard, Loop Guard, and BPDU Guard in Rapid PVST+ environments?

Select 2 answers
A.Root Guard, when enabled on a port, prevents that port from becoming the root port by placing it in a root-inconsistent state if a superior BPDU is received.
B.Root Guard automatically shuts down the port when a superior BPDU is received, similar to BPDU Guard.
C.Loop Guard, when enabled, disables a port if BPDUs are no longer received on it, preventing a unidirectional link failure.
D.BPDU Guard, when enabled, puts the port in an errdisable state if a BPDU is received, which is typically used on access ports to prevent unauthorized switches from connecting.
E.BPDU Guard places the port in a blocking state (loop-inconsistent) when a BPDU is received, similar to Loop Guard.
AnswersA, D

Root Guard, enabled on a designated port, does not prevent the switch from receiving a superior BPDU; instead, it reacts by moving the port into a root-inconsistent state, which blocks all traffic on that port while the superior BPDU continues to arrive. Once the superior BPDUs stop, the port automatically returns to its normal designated role. This behavior keeps an unauthorized switch from becoming the root bridge, but it does not disable the port or require manual intervention.

Why this answer

Root Guard prevents a port from becoming a root port by placing it in a root-inconsistent (blocking) state upon receiving a superior BPDU, protecting the root bridge placement. Option D is correct because BPDU Guard errdisables a port upon receiving a BPDU, a feature typically applied to access ports to block unauthorized switches. Option B is wrong: Root Guard does not shut down the port; it places it in a blocked state, unlike BPDU Guard's errdisable action.

Option C is wrong: Loop Guard does not disable a port when BPDUs stop being received; instead, it moves the port to a loop-inconsistent (blocking) state to guard against unidirectional link failures. Option E is wrong: BPDU Guard errdisables ports, whereas the loop-inconsistent blocking state is used by Loop Guard or Root Guard, not BPDU Guard.

Exam trap

Cisco often tests the distinction between 'shutdown' (errdisable) and 'blocking' (inconsistent state) — candidates confuse BPDU Guard's errdisable behavior with Root Guard's or Loop Guard's blocking behavior, leading them to incorrectly select Option B.

Why the other options are wrong

B

Root Guard does not shut down the port; it places the port in a root-inconsistent state, which effectively blocks traffic but does not disable the port. BPDU Guard, on the other hand, errdisables the port.

C

Loop Guard does not disable the port; it places the port into a loop-inconsistent state, blocking traffic on that port until BPDUs are received again. The port remains administratively up.

E

BPDU Guard errdisables the port, not just blocks it. Loop Guard uses a loop-inconsistent state, which is different from errdisable. BPDU Guard is a more severe reaction.

50
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.

51
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.

52
MCQhard

A switch should disable an edge port immediately if a BPDU is received on it. Which feature is intended for that specific behavior?

AnswerA

BPDU Guard is correct because it is specifically designed to protect edge ports configured with PortFast. When a BPDU is received on such a port, BPDU Guard immediately places the port into the error-disabled state, preventing an unexpected switch from creating a Layer 2 loop. This action is immediate and automatic, requiring manual re-enabling or errdisable auto-recovery, which matches the behavior described in the question.

Why this answer

The feature is BPDU Guard. In plain language, the administrator is treating the port as an end-device-only edge interface and wants the switch to react aggressively if it ever sees spanning-tree control traffic there. BPDU Guard does exactly that: if a BPDU appears on a protected edge port, the switch places the interface into an err-disabled state to help prevent accidental loops or rogue switch connections.

This is different from root guard and loop guard, which solve other spanning-tree control problems. BPDU Guard is the specific answer when the requirement is “if you ever hear a BPDU here, shut the port down quickly.”

Exam trap

A common exam trap is confusing BPDU Guard with Root Guard or Loop Guard. Candidates may incorrectly select Root Guard because it also deals with BPDUs, but Root Guard only blocks ports from becoming root ports and does not disable the port immediately. Loop Guard protects against unidirectional link failures and does not shut down ports upon BPDU receipt.

Another mistake is thinking UDLD handles BPDU protection; however, UDLD only detects unidirectional physical link failures and is unrelated to STP BPDU processing. Understanding that BPDU Guard uniquely disables edge ports upon BPDU detection is critical to avoid this trap.

Why the other options are wrong

B

Loop Guard is incorrect because it protects against unidirectional link failures by preventing a port from transitioning to forwarding when BPDUs stop, but it does not disable a port upon BPDU receipt.

C

Root Guard is incorrect because it prevents a port from becoming a root port by blocking superior BPDUs but does not disable the port immediately when a BPDU is received on an edge port.

D

UDLD is incorrect because it detects unidirectional physical link failures and does not interact with BPDU processing or disable ports based on BPDU reception.

53
PBQhard

You are connected to multilayer switch MLS1. MLS1 was configured to be the root bridge for VLAN 1, but SW2 (priority 4096) is the intended root. Remove MLS1's root-bridge configuration for VLAN 1 so that MLS1 returns to the default priority, and configure Gi0/2, which connects to a host, with PortFast and BPDU Guard.

Network Topology
Gi0/0Gi0/0Gi0/1Gi0/1Gi0/2Gi0/2Gi0/2SiMLS1SW1SW2Host

Hints

  • •A root primary configuration appears in the running-config as a spanning-tree vlan priority command.
  • •Use no spanning-tree vlan 1 priority 24576 to return to the default priority.
  • •Gi0/2 needs spanning-tree portfast and spanning-tree bpduguard enable.
A.On MLS1, remove the VLAN 1 priority command (spanning-tree vlan 1 priority 24576) to return to the default priority; on Gi0/2, configure 'spanning-tree portfast' and 'spanning-tree bpduguard enable'.
B.On MLS1, set the VLAN 1 priority to 0; on Gi0/2, configure 'spanning-tree portfast' and 'spanning-tree bpduguard enable'.
C.On MLS1, remove the VLAN 1 priority command; on Gi0/2, configure 'spanning-tree portfast' and 'spanning-tree bpdufilter enable'.
D.On MLS1, remove the VLAN 1 priority command; on Gi0/2, configure 'spanning-tree portfast' and 'spanning-tree guard root'.
AnswerA
solution
! MLS1
configure terminal
no spanning-tree vlan 1 priority 24576
interface GigabitEthernet0/2
spanning-tree portfast
spanning-tree bpduguard enable
end

Why this answer

MLS1 is the root for VLAN 1 because its priority was lowered to 24576 (the result of spanning-tree vlan 1 root primary appears in the configuration as a priority command), which beats the default 32768 but SW2 should be root with 4096. Removing that command with 'no spanning-tree vlan 1 priority 24576' returns MLS1 to the default 32768, so SW2 wins the election. Gi0/2 faces a host, so enable PortFast and BPDU Guard on it: spanning-tree portfast and spanning-tree bpduguard enable.

Exam trap

Trap: Candidates may forget that the root bridge is determined by lowest priority. They might set the wrong switch to lower priority or use incorrect recovery methods like reloading or removing BPDU Guard.

Why the other options are wrong

B

Priority 0 makes MLS1 root, not SW2.

C

BPDU filter is not BPDU Guard.

54
MCQhard

A non-root switch has two uplinks toward the root bridge. One path has a lower total STP cost than the other. What role will the lower-cost uplink have?

A.Alternate port
B.Root port
C.Designated port
D.Disabled port
AnswerB

The root port is selected on each non-root bridge by comparing received BPDUs; the port with the lowest cumulative root path cost (with tie-breaking rules) becomes the root port, placing it in the forwarding state. This is the port that provides the single best path toward the root bridge, carrying all upstream traffic. Since the non-root switch has two uplinks, the one with the lower cost to the root is the root port.

Why this answer

On a non-root switch, the port with the lowest path cost toward the root bridge becomes the root port. The higher-cost uplink would become an alternate (blocked) port. A designated port is found on the upstream switch toward this switch, not on the non-root switch itself.

A disabled port is administratively shut down, which does not apply here.

Exam trap

Remember, the root port is determined by the lowest path cost to the root bridge, not by any other criteria.

Why the other options are wrong

A

The higher-cost uplink becomes an alternate (blocked) port, not the lower-cost one.

C

A designated port exists on the upstream switch toward this switch, not on the non-root switch.

D

A disabled port is administratively shut down, not a port with a lower STP cost.

55
MCQhard

A switch port connected to an end host is configured with both PortFast and BPDU Guard. What is the most likely outcome if a small switch is connected there and starts sending BPDUs?

A.The port is error-disabled by BPDU Guard.
B.The port automatically becomes the root port.
C.The port converts into a trunk for the attached switch.
D.The port ignores the BPDU because PortFast disables STP entirely.
AnswerA

BPDU Guard places a PortFast-enabled port into err-disabled state the moment it receives a BPDU, since PortFast ports should only face end hosts. Connecting a switch generates BPDUs, triggering immediate shutdown, satisfying the stem's requirement to prevent loops and rogue switch attachment.

Why this answer

BPDU Guard places the port into an error-disabled state upon receiving a BPDU, because PortFast defines the port as an edge port that should never receive BPDUs. Option B is incorrect because receiving a BPDU does not automatically make a port a root port; root port selection depends on bridge ID and path cost, and BPDU Guard prevents further STP processing by disabling the port. Option C is incorrect because a port cannot convert to a trunk solely by receiving a BPDU; trunking requires manual configuration or Dynamic Trunking Protocol (DTP).

Option D is incorrect because PortFast does not disable STP entirely; it only speeds up initial convergence, and BPDU Guard actively responds to BPDUs by error-disabling the port.

Exam trap

Remember, BPDU Guard is about protection, not ignoring or processing BPDUs. It disables the port to prevent loops.

Why the other options are wrong

B

This option is wrong because a port configured with PortFast and BPDU Guard will not automatically become the root port when it receives BPDUs; instead, it will be error-disabled due to BPDU Guard's protective mechanism.

C

This option is incorrect because a port configured with PortFast and BPDU Guard does not convert to a trunk when receiving BPDUs; instead, BPDU Guard will disable the port to prevent potential loops.

D

This option is incorrect because PortFast does not disable Spanning Tree Protocol (STP) entirely; it only allows the port to transition to the forwarding state immediately without waiting for STP convergence. BPDU Guard will still take effect if BPDUs are received on a PortFast-enabled port.

56
MCQhard

A network engineer notices that an uplink port on a distribution switch has moved to a root-inconsistent state and is blocking traffic. The port is configured with Root Guard and is connected to a new access switch. The new access switch has a lower bridge priority than the current root bridge. What is the most likely cause?

A.BPDU Guard has errdisabled the port because a BPDU was received on an access port.
B.BPDU Filter is blocking inbound BPDUs, causing the switch to fail to detect the topology change and isolate the port.
C.Root Guard has placed the port into root-inconsistent state because the new switch advertised a superior BPDU.
D.Loop Guard has detected a unidirectional link and placed the port in a blocking state to prevent a loop.
AnswerC

Root Guard is designed to prevent the port from becoming a root port. Upon receiving a superior BPDU (lower bridge ID), it places the port in root-inconsistent state, effectively blocking traffic. This directly matches the symptom described.

Why this answer

Root Guard is configured on the uplink port of the distribution switch. When the new access switch advertises a superior BPDU (lower bridge priority than the current root bridge), Root Guard places the port into a root-inconsistent state to prevent the distribution switch from accepting the new switch as the root bridge. This blocks traffic on that port to protect the spanning-tree topology.

Exam trap

Cisco often tests the distinction between Root Guard and BPDU Guard, where candidates confuse the root-inconsistent state with an errdisable state or assume any BPDU-related protection will errdisable the port.

Why the other options are wrong

A

Candidates mistakenly equate BPDU Guard with any BPDU-induced blocking, but the state 'root-inconsistent' is specific to Root Guard.

B

Candidates may think that filtering BPDUs leads to port isolation, but BPDU Filter would not trigger a protective state like root-inconsistent.

D

Candidates often confuse Loop Guard and Root Guard because both can cause inconsistent states, but Loop Guard triggers loop-inconsistent, not root-inconsistent, and is triggered by BPDU loss, not receipt of superior BPDUs.

57
MCQhard

After connecting a new switch to interface GigabitEthernet1/0/1 on a distribution switch, a network engineer notices that the interface is in err-disable state. The engineer checks the configuration and finds that spanning-tree portfast and spanning-tree bpduguard enable are applied to the interface. What is the most likely cause of the err-disable state?

A.BPDU Guard was incorrectly enabled on a port that should be a trunk link.
B.The connected switch is sending BPDUs with a lower bridge priority.
C.Spanning-tree PortFast is enabled on a port that connects to another switch.
D.The port is configured as an access port, but should be a trunk.
AnswerC

PortFast skips the listening and learning STP states and is designed for end hosts. When combined with BPDU Guard, the switch was instructed to disable the port upon receiving any BPDU. The downstream switch naturally sends BPDUs, causing BPDU Guard to react and place the port in err-disable. Removing PortFast (and leaving BPDU Guard alone, or disabling BPDU Guard on that link) would resolve the issue.

Why this answer

PortFast is designed for end-host ports that should not receive BPDUs. When PortFast is enabled on a port connecting to another switch, the switch will immediately transition the port to forwarding state, but if it then receives a BPDU from the connected switch, BPDU Guard will error-disable the port. This is the most common cause of err-disable state when both PortFast and BPDU Guard are configured on an inter-switch link.

Exam trap

Cisco often tests the misconception that BPDU Guard alone causes err-disable, but the trap here is that PortFast must be enabled for BPDU Guard to trigger err-disable on a port receiving BPDUs from another switch.

Why the other options are wrong

A

Candidates often associate BPDU Guard exclusively with access ports and assume configuring it on a trunk is itself a misconfiguration, overlooking that PortFast is the real culprit.

B

Students may confuse root bridge placement with BPDU Guard operation, thinking that a BPDU from a superior switch might cause a port to be disabled, when in fact BPDU Guard is content-agnostic.

D

Candidates may think that because a link between switches should be a trunk, the access mode misconfiguration is the root cause. However, they miss the fact that BPDU Guard acts on the BPDU regardless of the port mode, and the real misconfiguration is PortFast.

58
MCQhard

A switch should automatically disable any access port that receives a BPDU from an attached device. Which feature directly provides that behavior?

AnswerC

BPDU Guard is the correct answer because it is specifically designed to protect access ports, which should operate as edge ports in a spanning-tree domain. When an access port with BPDU Guard enabled receives any BPDU, the switch immediately places the port into the err-disabled state, effectively shutting it down to prevent a potential switching loop or unauthorized switch connection. This behavior directly matches the requirement of automatically disabling an access port that receives BPDUs.

Why this answer

BPDU Guard is designed for edge ports that should never see BPDUs. If a BPDU arrives, the port is placed into an err-disabled state to protect the topology. Root Guard and Loop Guard solve different STP problems.

Exam trap

A common exam trap is confusing BPDU Guard with Root Guard or Loop Guard. Candidates may incorrectly select Root Guard because it involves BPDUs and port blocking, but Root Guard only prevents a port from becoming a root port and does not err-disable the port. Loop Guard is often mistaken as it protects against unidirectional link failures but does not disable ports on BPDU receipt.

The key distinction is that BPDU Guard immediately disables the port upon receiving any BPDU, which is the behavior the question describes. Misunderstanding these differences can lead to incorrect answers.

Why the other options are wrong

A

Root Guard prevents a port from becoming a root port if superior BPDUs are received, maintaining the root bridge position, but it does not err-disable the port upon BPDU receipt. Therefore, it does not fulfill the requirement to disable access ports that receive BPDUs.

B

Loop Guard protects against unidirectional link failures by preventing a port from transitioning to forwarding state if BPDUs stop arriving on non-designated ports. It does not disable ports upon receiving BPDUs, so it does not meet the behavior described in the question.

D

PortFast is a feature that allows ports to transition quickly to forwarding state, bypassing the usual STP listening and learning states. It does not disable ports upon receiving BPDUs and therefore does not provide the behavior described.

59
PBQhard

You are connected to SW1 in a Rapid-PVST+ network where SW1 is the root bridge for VLAN 10. Port Gi0/1 is an edge port with PortFast and BPDU Guard. A user connected an unmanaged switch to the port, which sent BPDUs, and the port went err-disabled. The device has been removed. Recover the port immediately while keeping PortFast and BPDU Guard enabled.

Network Topology
Gi0/0Gi0/0Gi0/2Gi0/0Gi0/1SW1SW2SW3Host

Hints

  • •An err-disabled port must be shut down and then brought back up.
  • •Do not remove BPDU Guard just to recover the port; it protects the edge port.
  • •Verify with show interfaces gigabitEthernet 0/1 status.
A.On Gi0/1 enter shutdown and then no shutdown, leaving PortFast and BPDU Guard configured
B.On Gi0/1 enter no spanning-tree bpduguard enable and then no shutdown
C.On Gi0/1 enter no spanning-tree portfast followed by shutdown and no shutdown
D.On Gi0/1 enter only no shutdown
AnswerA
solution
! SW1
interface gigabitEthernet 0/1
shutdown
no shutdown

Why this answer

An err-disabled port stays down until it is bounced: issuing shutdown followed by no shutdown on the interface clears the err-disabled state. no shutdown alone does not clear it. Because the device that sent BPDUs has been removed, PortFast and BPDU Guard should stay configured so the edge port remains protected against future BPDUs. Removing BPDU Guard or PortFast would only weaken the edge-port protection.

Exam trap

The exam trap is that candidates may focus on recovering the port (shutdown/no shutdown) but forget to address why the BPDU was received. Simply re-enabling BPDU Guard or reapplying PortFast will not prevent recurrence. The key is to ensure the connected device is not sending BPDUs, either by removing it or reclassifying the port.

How to eliminate wrong answers

Option A is wrong because disabling BPDU Guard violates the requirement that BPDU Guard must be enabled on all edge ports. Option B is wrong because re-enabling PortFast and BPDU Guard does not stop the BPDU source; the port will go err-disabled again. Option C is wrong because Root Guard does not prevent BPDU Guard from triggering; it is a different feature.

Option D is correct because it addresses the root cause by ensuring no BPDUs are received on the edge port, allowing BPDU Guard to remain enabled and the port to stay operational.

60
PBQhard

You are connected to SW3. Port Gi0/3 connects to a PC and must be an edge port. A small unmanaged switch was previously plugged into Gi0/3 and sent BPDUs, so BPDU Guard err-disabled the port. The device has been removed. Enable PortFast on Gi0/3, keep BPDU Guard, and recover the port.

Network Topology
G0/1G0/1G0/2G0/1G0/2G0/2G0/3SW3SW1SW2PC

Hints

  • •The err-disabled port must be manually recovered with shutdown/no shutdown.
  • •PortFast is configured at the interface level.
  • •BPDU Guard is also configured at the interface level using 'spanning-tree bpduguard enable'.
A.interface g0/3, spanning-tree portfast, shutdown, no shutdown
B.interface g0/3, spanning-tree portfast, no shutdown
C.interface g0/3, spanning-tree portfast, end, copy running-config startup-config
D.interface g0/3, spanning-tree portfast, shutdown
AnswerA
solution
! SW3
interface GigabitEthernet0/3
spanning-tree portfast
shutdown
no shutdown

Why this answer

PortFast is missing on the edge port, so enable it with spanning-tree portfast; BPDU Guard is already configured and must stay. An err-disabled port is only recovered by bouncing it: shutdown followed by no shutdown. Without the bounce the port stays err-disabled.

Exam trap

A common trap is forgetting that err-disabled ports require a manual shutdown/no shutdown cycle to recover. Simply enabling BPDU Guard or saving the configuration does not restore the port. Always remember to reset the interface after correcting the cause.

How to eliminate wrong answers

Option B is incorrect because it only issues 'no shutdown' without first shutting down the interface; the port remains err-disabled. Option C is incorrect because saving the configuration does not affect the operational state. Option D is incorrect because it only shuts down the interface without bringing it back up.

Option A is correct because it includes both the configuration commands and the full recovery cycle (shutdown followed by no shutdown).

61
PBQhard

You are connected to multilayer switch MLSW1 running Rapid PVST+. Gi0/1 connects to an end-user port with PortFast and BPDU Guard; a BPDU from a device that has since been removed placed it in the err-disabled state. Configure MLSW1 so that it is the root bridge for VLAN 10 with a priority of 4096, and recover the interface.

Network Topology
G0/1 to PCG0/2 to MLSW3 G0/1G0/2 to MLSW3 G0/1G0/2 to MLSW1 G0/3SiMLSW2SiMLSW1SiMLSW3

Hints

  • •Check the current root priority and adjust with 'spanning-tree vlan <vlan> priority <value>'.
  • •An err-disabled interface can be recovered by administrative shutdown and no shutdown.
  • •Look at the spanning-tree topology to find which port is blocking; it will be in 'ALT' role with 'BLK' state.
A.spanning-tree vlan 10 priority 4096; interface GigabitEthernet0/1; shutdown; no shutdown
B.spanning-tree vlan 10 root primary; interface GigabitEthernet0/1; shutdown; no shutdown
C.spanning-tree vlan 10 priority 4096; interface GigabitEthernet0/1; no shutdown
D.spanning-tree vlan 10 priority 4000; interface GigabitEthernet0/1; shutdown; no shutdown
AnswerA
solution
! MLSW1
spanning-tree vlan 10 priority 4096
interface gigabitEthernet 0/1
shutdown
no shutdown

Why this answer

To make MLSW1 the root bridge, lower its VLAN 10 priority to 4096 with spanning-tree vlan 10 priority 4096 (priorities must be multiples of 4096). The current root has priority 24586 (24576 plus VLAN 10), so 4096 will win. The err-disabled port is recovered by shutdown followed by no shutdown; no shutdown alone does not clear it.

Exam trap

Remember that 'spanning-tree vlan <vlan> root primary' sets priority to 24576, not a custom value. Also, err-disabled recovery requires a shutdown followed by no shutdown. Always use 'show spanning-tree vlan <vlan>' to verify port roles, not 'show interfaces status' or 'show running-config'.

How to eliminate wrong answers

Option B is wrong because 'root primary' sets priority to 24576, not 4096, and 'no shutdown' alone won't recover err-disabled. Option C is wrong because 'no shutdown' alone doesn't recover err-disabled, and 'show interfaces status' doesn't show STP roles. Option D is wrong because 'show running-config' doesn't show STP blocking ports.

Option A is correct because it uses the exact priority 4096, properly recovers the interface, and uses the correct verification command.

62
MCQmedium

Why is PortFast typically enabled on switch ports connected to end devices?

A.To let end-device ports reach forwarding state more quickly
B.To make access ports participate in OSPF
C.To convert all access ports into trunks
D.To disable Ethernet addressing on PCs
AnswerA

PortFast on switch ports connected to end devices (like PCs, printers, servers) allows the port to transition directly from blocking to forwarding state, bypassing the listening and learning states of Spanning Tree Protocol (STP). This is crucial because STP normally takes 30 seconds (or 50 seconds in older implementations) to converge, which can cause delays in DHCP or bootp requests. Since end devices are typically not a loop, PortFast safely accelerates this process, enabling immediate connectivity.

Why this answer

PortFast is enabled so access ports connected to end devices can move to forwarding more quickly instead of waiting through the normal spanning-tree listening and learning transitions. In plain language, it helps a user’s PC, printer, or similar endpoint start communicating sooner after the link comes up. That can reduce delays at startup and prevent certain device timeout problems.

PortFast is not intended as a loop-prevention mechanism by itself, and it should not normally be used carelessly on links to other switches. That is why it is commonly paired with BPDU Guard on edge ports. The correct answer is the one focused on faster transition for end-device access links rather than on unrelated routing or VLAN functions.

Exam trap

Do not confuse PortFast with disabling spanning-tree or improving routing; it specifically speeds up access port transitions.

Why the other options are wrong

B

This option is incorrect because PortFast does not enable access ports to participate in OSPF; OSPF is a routing protocol that requires Layer 3 interfaces, while PortFast is a feature for Layer 2 switch ports.

C

This option is wrong because PortFast does not convert access ports into trunk ports; it is designed to bypass the Spanning Tree Protocol (STP) listening and learning states to allow end devices to connect more quickly.

D

Disabling Ethernet addressing on PCs is not related to the function of PortFast, which is designed to expedite the transition of switch ports to the forwarding state. PortFast does not alter how Ethernet addressing operates on connected devices.

63
PBQhard

You are connected to R1, a Catalyst 3650 running IOS-XE. Gi1/0/1 connects to downstream switch R2 and has Root Guard; Gi1/0/2 is the uplink to the core and has Loop Guard; Gi1/0/3 is a PortFast access port with BPDU Guard. R2 was misconfigured with a lower bridge priority than the root and sent superior BPDUs, so Root Guard put Gi1/0/1 in root-inconsistent state; R2's priority has now been corrected. Separately, an unmanaged switch plugged into Gi1/0/3 triggered BPDU Guard and has been removed. Which actions on R1 restore normal operation while keeping the protections?

Network Topology
Gi1/0/1Gi1/0/2Gi1/0/3R1R2Core SwitchHost

Hints

  • •Root Guard should be on the port that is designated, not receiving superior BPDUs.
  • •Loop Guard should be on the port that is a root port or alternate root port.
  • •An err-disabled port must be manually recovered with shutdown/no shutdown.
A.Keep Root Guard on Gi1/0/1 and Loop Guard on Gi1/0/2; bounce Gi1/0/3 with shutdown then no shutdown. Gi1/0/1 recovers automatically once R2 stops sending superior BPDUs.
B.Remove Root Guard from Gi1/0/1 to restore forwarding, and bounce Gi1/0/3 with shutdown then no shutdown.
C.Keep Root Guard and Loop Guard, and on Gi1/0/3 issue only no shutdown.
D.Keep Root Guard and Loop Guard, remove spanning-tree bpduguard enable from Gi1/0/3, and issue no shutdown.
AnswerA
solution
! R1
interface GigabitEthernet1/0/3
shutdown
no shutdown

Why this answer

Root Guard worked as designed: R2 sent superior BPDUs and Gi1/0/1 was placed in root-inconsistent state. The fix is on R2 (already done), and Root Guard recovers the port automatically once the superior BPDUs stop, so it should not be removed. Loop Guard on the uplink is functioning correctly and is not inconsistent.

Gi1/0/3 is err-disabled because of BPDU Guard and stays down until the port is bounced with shutdown and no shutdown.

Exam trap

Be careful not to confuse the purpose of Root Guard and Loop Guard. Root Guard is for designated ports, Loop Guard is for root/alternate ports. Also, remember that an err-disabled port requires a shutdown/no shutdown sequence to recover, not just no shutdown.

Why the other options are wrong

B

Issuing only 'no shutdown' will not recover an interface from the err-disabled state caused by BPDU Guard; it must be administratively shut down first with 'shutdown', then re-enabled with 'no shutdown'.

C

The verification step checks Root Guard on Gi1/0/1 and Loop Guard on Gi1/0/2, which is the original incorrect configuration before the swap; after the fix, Root Guard should be on Gi1/0/2 and Loop Guard on Gi1/0/1.

D

The verification step incorrectly states that Loop Guard is active on Gi1/0/2. After swapping the configurations, Loop Guard is now on Gi1/0/1, not Gi1/0/2, so this option validates the wrong port.

64
MCQhard

A network engineer notices that a new switch, SW3, was connected to port GigabitEthernet0/1 on SW1, but the port immediately went into an err-disabled state. The network uses Rapid PVST+ with BPDU Guard enabled globally on all access ports. The engineer checks the logs and sees 'bpduguard error detected' messages. What is the most likely cause of the err-disabled state?

A.The port is configured as an access port, but BPDU Guard should be disabled on all access ports.
B.A BPDU was received on port GigabitEthernet0/1, triggering BPDU Guard.
C.Configure Root Guard on the interface to prevent the err-disabled state.
D.Enable Loop Guard on the interface to prevent the err-disabled state.
AnswerB

BPDU Guard is a security feature that deliberately places a port into an err-disabled state when a BPDU is received on a port where BPDU Guard is enabled, typically on an access port configured with PortFast. The port GigabitEthernet0/1 transitioning to err-disabled indicates that it received an unexpected BPDU, which suggests another switch was connected to that port. By immediately error-disabling the port, BPDU Guard prevents the unauthorized device from participating in spanning tree and disrupting the topology. This explanation directly matches the observed behavior and is the correct root cause.

Why this answer

The err-disabled state is caused by BPDU Guard triggering when a BPDU is received on an access port. Option A is incorrect because BPDU Guard is intentionally enabled on access ports to prevent unauthorized switches from joining the network. Option C is wrong because Root Guard prevents a port from becoming the root, not from receiving BPDUs.

Option D is wrong because Loop Guard prevents loops on blocked ports in case of unidirectional links, not relevant to BPDU reception.

Exam trap

Cisco often tests the confusion between BPDU Guard, Root Guard, and Loop Guard; candidates may incorrectly attribute the err-disable to Root Guard or Loop Guard, but the true cause is receiving a BPDU on a BPDU-Guard-enabled port.

Why the other options are wrong

A

BPDU Guard is designed to be enabled on access ports to protect against unauthorized switches, so disabling it on all access ports would defeat its purpose.

C

Root Guard prevents a port from becoming the root bridge, but does not block BPDU reception that causes err-disable with BPDU Guard.

D

Loop Guard detects and prevents loops on blocked ports due to unidirectional links, not related to the BPDU Guard err-disable mechanism.

65
Drag & Dropmedium

Drag and drop the following steps into the correct order to recover a PortFast access port that was err-disabled by a BPDU Guard violation. Diagnose first, then remove the cause, then recover the port.

Drag or tap steps into the slots.

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

Why this order

First confirm that the port is err-disabled (show interfaces status err-disabled). Then remove the cause by disconnecting the unauthorized device that sent BPDUs. Only then enter interface configuration mode and bounce the port with shutdown followed by no shutdown.

Recovering before removing the cause would err-disable the port again immediately.

Exam trap

Candidates often confuse the port roles for Root Guard and Loop Guard, or think that disabling the protection feature will recover an err-disabled port. Remember: Root Guard is for designated ports, Loop Guard for non-designated, and BPDU Guard for PortFast. Err-disabled recovery requires manual reset or global errdisable recovery configuration.

66
MCQhard

A port connected to an end host is configured with PortFast and BPDU Guard. What is the most likely result if a small unmanaged switch is connected and starts sending BPDUs?

A.The port is error-disabled by BPDU Guard.
B.The port automatically becomes the root port.
C.The port is converted into a trunk.
D.The port ignores the BPDU because PortFast disables STP entirely.
AnswerA

BPDU Guard is a PortFast enhancement that places the port into the errdisable state whenever a BPDU is received on an edge port. Since PortFast assumes the port connects to an end host, any incoming BPDU signals a potential bridging loop or switch misconfiguration. The switch immediately shuts down the port to protect the spanning-tree topology, overriding any normal STP processing that might otherwise occur.

Why this answer

The most likely result is that the port is placed into an err-disabled state by BPDU Guard. In practical terms, PortFast tells the switch to treat the interface like an edge port for a normal endpoint, which is why it starts forwarding quickly. BPDU Guard protects that assumption. If the port suddenly receives a spanning-tree BPDU, the switch treats that as a sign that the port is no longer connected to a simple end device.

This combination is common in enterprise access-layer design because it improves user startup time while still protecting the topology. The correct answer is the one that describes the port being shut down automatically when BPDUs appear unexpectedly.

Exam trap

Remember, BPDU Guard disables the port, it doesn't use spanning-tree states like blocking or learning.

Why the other options are wrong

B

This option is wrong because a port configured with PortFast and BPDU Guard will not automatically become the root port when it receives BPDUs; instead, it will be error-disabled due to BPDU Guard's protection mechanism.

C

This option is wrong because a port configured with PortFast does not automatically convert to a trunk port when it receives BPDUs; instead, it remains in access mode. BPDU Guard will cause the port to be error-disabled upon receiving BPDUs, preventing any trunking behavior.

D

This option is wrong because PortFast does not disable Spanning Tree Protocol (STP) entirely; it merely allows the port to transition to the forwarding state immediately without participating in STP calculations. BPDUs are still processed, and BPDU Guard will take action if they are received.

67
Drag & Dropmedium

Drag and drop the following steps into the correct order to enable PortFast and BPDU Guard on a switch access port, starting from privileged EXEC mode. Set the port to access mode before enabling PortFast, then enable BPDU Guard.

Drag or tap steps into the slots.

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

Why this order

Enter global configuration mode, select the interface, set it to access mode, enable PortFast, and then enable BPDU Guard, which is an interface-level command. Interface commands must be entered after selecting the interface, and ending configuration mode before the last command would make it invalid.

Exam trap

The trap is that candidates may think the order of configuring the guards is arbitrary, but the question explicitly requires a specific sequence. Pay close attention to the order in which features are listed in the stem.

68
MCQmedium

An engineer wants users to get fast link-up on access ports but also wants the switch to disable a port if another switch is connected and sends BPDUs. Which combination of features best meets that requirement?

C.Root Guard and VTP pruning
D.Port security and CDP
AnswerA

PortFast bypasses the spanning-tree listening and learning states, allowing a host-facing access port to transition directly to forwarding and deliver immediate link-up. BPDU Guard complements this by shutting the port in an error-disabled state if any BPDU is received, which blocks an accidental or rogue switch connection while preserving the fast-start behavior for legitimate hosts. Together they form the standard Cisco edge-port hardening pair.

Why this answer

PortFast and BPDU Guard are the classic edge-port combination for this requirement. PortFast helps a user-facing interface begin forwarding quickly so a PC or phone does not wait through the normal spanning-tree transition delay. BPDU Guard adds protection by monitoring that same port for BPDUs.

If a switch is accidentally or intentionally connected and starts participating in spanning tree, BPDU Guard reacts by disabling the port to protect the Layer 2 topology. In plain language, users get quick connectivity when the port is used correctly, but the network still protects itself against someone plugging in a switch where only an endpoint should exist. That is exactly what the requirement asks for.

Exam trap

Avoid confusing BPDU Guard with other guard features like Root Guard or Loop Guard, which serve different purposes.

Why the other options are wrong

B

DHCP snooping and DAI (Dynamic ARP Inspection) do not address the requirement of disabling a port upon receiving BPDUs; they focus on protecting against rogue DHCP servers and ARP spoofing, respectively.

C

Root Guard and VTP pruning do not address the requirement of quickly enabling access ports and disabling them upon receiving BPDUs. Root Guard is used to prevent a port from becoming a root port, while VTP pruning optimizes VLAN traffic, neither of which directly manage port states based on BPDU reception.

D

Port security and CDP do not provide the necessary functionality to disable a port when BPDUs are received. Port security can limit the number of MAC addresses but does not specifically address BPDU handling.

69
MCQhard

A new switch with the default bridge priority (32768) and a lower MAC address than every existing switch is added to the network. The engineer expected the new switch to become the STP root bridge, but the existing root bridge remains the root. What is the most likely reason?

A.The new switch is running PVST+ while the existing switches use Rapid PVST+
B.PortFast is enabled on the new switch's uplink ports
C.The existing root bridge has a bridge priority lower than the default value of 32768
D.The new switch was added with a bridge priority of 4096
AnswerC

If the existing root bridge’s priority is less than 32768 (e.g., 4096 or 0), its Bridge ID is lower than the new switch’s default 32768 + lower MAC. STP always elects the switch with the lowest Bridge ID as the root bridge. Thus, despite the new switch’s lower MAC, the manually lowered priority keeps the existing switch as root.

Why this answer

The existing root bridge has a bridge priority lower than the default value of 32768, so even though the new switch has the default priority, its lower MAC address does not make it the root. STP elects the root bridge based on the lowest bridge ID (priority + MAC address). Since the existing root already has a lower priority, it remains the root.

The new switch's lower MAC address only becomes a tiebreaker when priorities are equal, which is not the case here.

Exam trap

Cisco often tests the misconception that a lower MAC address alone can cause a root bridge change, but the trap here is that candidates forget the bridge priority is compared first, so a switch with default priority cannot outrank an existing root with a manually lowered priority.

Why the other options are wrong

A

Candidates may think that STP version incompatibility disrupts root election, but both versions use the same BPDU format and root election rules.

B

PortFast affects port transition time, not root election.

D

Candidates may confuse the symptom and think that a low priority on the new switch causes the problem, but this would make the new switch the root, not another switch.

70
PBQeasy

You are connected to SW1, a Layer 2 switch. The network administrator wants to prevent unauthorized switches from being connected to access ports. Port G0/1 is an access port in VLAN 10. You need to configure BPDU Guard on this port to protect against STP loops caused by rogue switches. Additionally, enable PortFast for immediate transition to forwarding. Configure it on this port only, without changing the behavior of other ports.

Hints

  • •PortFast should be applied to access ports to reduce STP convergence time.
  • •BPDU Guard disables the port if a BPDU is received.
  • •Both commands are under the interface configuration.
A.SW1(config-if)# spanning-tree portfast SW1(config-if)# spanning-tree bpduguard enable
B.SW1(config)# spanning-tree portfast default SW1(config)# spanning-tree bpduguard default
C.SW1(config-if)# spanning-tree portfast SW1(config-if)# spanning-tree guard root
D.SW1(config-if)# spanning-tree portfast SW1(config-if)# spanning-tree bpduguard disable
AnswerA
solution
! SW1
interface GigabitEthernet0/1
spanning-tree portfast
spanning-tree bpduguard enable

Why this answer

PortFast allows an access port to skip STP listening/learning and transition immediately to forwarding. BPDU Guard protects against STP loops by error-disabling the port if a BPDU is received, which would indicate an unauthorized switch connection.

Exam trap

Be careful to distinguish between interface-level and global commands for PortFast and BPDU Guard. Also, remember that BPDU Guard uses 'bpduguard enable' (not 'disable') and is different from Root Guard ('guard root').

Why the other options are wrong

B

The specific factual error is that global commands affect all ports, not a single interface.

C

The specific factual error is confusing Root Guard with BPDU Guard; they serve different purposes.

D

The specific factual error is using the 'disable' keyword instead of 'enable' to activate BPDU Guard.

71
MCQeasy

Which STP port state on a classic 802.1D switch listens for BPDUs and prepares to participate in the topology, but does not yet learn MAC addresses?

A.Listening
B.Learning
C.Forwarding
D.Disabled
AnswerA

In the classic 802.1D listening state, a port is still blocked from forwarding user data, but it is actively listening to incoming BPDUs to determine the network topology. During this 15-second forward-delay interval, the switch does not learn MAC addresses from the frames it receives, and it cannot send user traffic. Only after this state does the port move to learning.

Why this answer

In classic STP, the listening state processes BPDUs and waits before learning begins. The learning state is when the switch starts populating the MAC table.

Exam trap

Do not confuse the listening state with the learning state; remember that listening involves BPDU processing without MAC address learning.

Why the other options are wrong

B

In the listening state, a switch port listens for BPDUs but does not learn MAC addresses. The learning state is the next step where the port begins to learn MAC addresses from incoming frames while still not forwarding traffic.

C

In the Forwarding state, the switch port has already learned MAC addresses and is forwarding data frames, whereas the question specifies a state that does not yet learn MAC addresses.

D

The Disabled port state does not listen for BPDUs, learn MAC addresses, or forward frames; it is administratively shut down and has no participation in STP topology.

72
MCQhard

Refer to the exhibit. An engineer configured PortFast on interface GigabitEthernet0/1, which connects to a hypervisor server that does not run spanning tree. However, the port still stays in the listening state for the forward delay period before it forwards traffic. Based on the output, what is the most likely cause?

A.The port is configured as a trunk, so PortFast is not active.
B.BPDU Guard is enabled on the port, causing it to block.
C.The forward delay timer is set too high, and PortFast cannot override it.
D.The server is sending BPDUs, causing the port to lose its PortFast state.
AnswerA

The plain 'spanning-tree portfast' command takes effect only on access ports. The exhibit shows the port operating as a trunk, so PortFast is not applied and the port goes through listening and learning as normal. For trunks to servers or hypervisors, use 'spanning-tree portfast trunk' or 'spanning-tree portfast edge trunk' on newer releases.

Why this answer

The plain 'spanning-tree portfast' command takes effect only on access ports. The exhibit shows GigabitEthernet0/1 configured and operating as a trunk, so PortFast is ignored and the port goes through the normal listening and learning states. The detail output also lacks the 'The port is in the portfast mode' line.

Exam trap

Cisco often tests the misconception that PortFast works on any port type, but the trap here is that PortFast is only effective on access ports, and trunk ports automatically disable PortFast regardless of configuration.

Why the other options are wrong

B

The port is not in an err-disabled state; BPDU Guard causes the port to be shut down, not to stay in listening.

C

Misunderstanding that PortFast bypasses timers completely on access ports; the high forward delay is irrelevant if PortFast were active.

D

The assumption that the server is sending BPDUs is contradicted by the output showing zero BPDUs received.

73
Drag & Dropmedium

Drag and drop the following steps into the correct order to configure and recover from a BPDU guard violation on a PortFast-enabled access port in RSTP.

Drag or tap steps into the slots.

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

Why this order

Configure PortFast and BPDU guard on the access port. Then trigger a violation by connecting an unauthorized switch, which causes the port to error-disable. Diagnose by checking the error-disabled status.

To recover, first remove the offending device, then cycle the port with shutdown and no shutdown; otherwise the port will immediately go error-disabled again.

Exam trap

Do not confuse the order: configuration must precede the violation. Also, recovery requires removing the rogue switch before bouncing the interface; failing to do so will cause the port to trip again.

74
MCQeasy

Which STP role identifies the port on a non-root switch that has the best path back to the root bridge?

A.Designated port
B.Root port
C.Alternate port
D.Disabled port
AnswerB

The root port is the single port on a non-root switch that has the lowest root path cost to the root bridge, making it the switch's best path toward the root. It is determined by examining received BPDUs, comparing root path cost, then sender bridge ID, then sender port ID. This port is placed in the forwarding state and is the only port that actively forwards traffic toward the root, ensuring a loop-free topology.

Why this answer

The root port is the single port on a non-root switch that provides the lowest-cost path toward the root bridge. Designated ports forward away from the root for a segment, and alternate ports are backup paths.

Exam trap

A frequent exam trap is mistaking the designated port for the root port. While both forward traffic, the designated port is selected per LAN segment to forward frames away from the root bridge, not necessarily providing the best path back to the root. Another trap is confusing the alternate port with the root port; alternate ports are backup paths kept in blocking state and do not forward traffic unless the root port fails.

Candidates often overlook that the root port is unique per non-root switch and always represents the lowest-cost path to the root bridge, which is the key to answering this question correctly.

Why the other options are wrong

A

Designated ports are selected for each LAN segment to forward traffic away from the root bridge, but they do not represent the best path back to the root bridge on a non-root switch. Therefore, this option is incorrect.

C

Alternate ports serve as backup paths and remain in a blocking state unless the root port fails. They do not identify the best path back to the root bridge, so this option is incorrect.

D

Disabled ports do not participate in STP forwarding or path selection and are not related to identifying the best path back to the root bridge, making this option incorrect.

75
PBQhard

You are connected to SW1, a multilayer switch that is not the STP root for VLAN 10; its root port is G0/2 to the core. G0/1 is a trunk to an access switch and is a designated port. Configure Root Guard on G0/1, Loop Guard on the uplink G0/2, and BPDU Guard on the PortFast access port G0/3. Afterwards, the access switch starts sending superior BPDUs on G0/1, and a rogue switch is connected to G0/3 and sends BPDUs. What are the resulting port states?

Network Topology
G0/1: designatedG0/2: root portG0/3: PortFastSW1Access SwitchCore SwitchEnd Device

Hints

  • •Root Guard is applied on ports that should never become root; use 'spanning-tree guard root'.
  • •Loop Guard prevents alternate or root ports from becoming designated when BPDUs stop; use 'spanning-tree guard loop' on uplinks.
  • •BPDU Guard combined with PortFast err-disables a port upon BPDU reception; enable with 'spanning-tree bpduguard enable' under the interface.
A.G0/1 is in root-inconsistent state (blocked); G0/3 is in err-disabled state.
B.G0/1 stays in forwarding state and only logs a message; G0/3 is in err-disabled state.
C.G0/1 is in root-inconsistent state (blocked); G0/3 stays forwarding because PortFast ignores BPDUs.
D.G0/1 is in err-disabled state; G0/3 is in root-inconsistent state.
AnswerA
solution
! SW1
interface GigabitEthernet0/1
spanning-tree guard root
interface GigabitEthernet0/2
spanning-tree guard loop
interface GigabitEthernet0/3
spanning-tree bpduguard enable

Why this answer

Root Guard on the designated port G0/1 places the port in root-inconsistent state (blocked for that VLAN) when superior BPDUs arrive, and it recovers when they stop. BPDU Guard on PortFast port G0/3 err-disables the port as soon as a BPDU is received. Loop Guard on the root port G0/2 protects against loss of BPDUs and plays no part here.

Exam trap

Do not confuse the states caused by Root Guard (root-inconsistent) and BPDU Guard (err-disable). Also, remember that Root Guard is applied to designated ports, not root or alternate ports.

Why the other options are wrong

B

Root Guard uses a specific 'root-inconsistent' state, not the generic 'blocking' state.

C

BPDU Guard triggers err-disable, not blocking. Blocking is an STP state, not an error state.

D

Root Guard and BPDU Guard have different effects: root-inconsistent vs. err-disable. Mixing them up is a common error.

Page 1 of 2 · 77 questions totalNext →

Ready to test yourself?

Try a timed practice session using only STP questions.