nerdexam
Cisco

350-401 · Question #197

Refer to the exhibit. An engineer entered the command no spanning-tree bpduguard enable on interface Fa 1/0/7. What is the effect of this command on Fa 1/0/7?

The correct answer is A. It remains in err-disabled state until the shutdown/no shutdown command is entered in the. Disabling BPDU Guard on an interface currently in an err-disabled state does not automatically recover it; the interface will remain err-disabled until it is manually reset using the shutdown followed by no shutdown commands.

Submitted by lukas.cz· Mar 6, 2026Security

Question

Refer to the exhibit. An engineer entered the command no spanning-tree bpduguard enable on interface Fa 1/0/7. What is the effect of this command on Fa 1/0/7?

Exhibits

350-401 question #197 exhibit 1
350-401 question #197 exhibit 2

Options

  • AIt remains in err-disabled state until the shutdown/no shutdown command is entered in the
  • BIt remains in err-disabled state until the errdisable recovery cause failed-port-state command is
  • CIt remains in err-disabled state until the no shutdown command is entered in the interface
  • DIt remains in err-disabled state until the spanning-tree portfast bpduguard disable command is

How the community answered

(58 responses)
  • A
    81% (47)
  • B
    5% (3)
  • C
    3% (2)
  • D
    10% (6)

Why each option

Disabling BPDU Guard on an interface currently in an err-disabled state does not automatically recover it; the interface will remain err-disabled until it is manually reset using the `shutdown` followed by `no shutdown` commands.

AIt remains in err-disabled state until the shutdown/no shutdown command is entered in theCorrect

The `no spanning-tree bpduguard enable` command only disables the BPDU Guard feature for future events on interface Fa 1/0/7; it does not clear the existing err-disabled state, which requires a manual `shutdown` followed by `no shutdown` to recover the port.

BIt remains in err-disabled state until the errdisable recovery cause failed-port-state command is

The `errdisable recovery cause failed-port-state` command is not the correct or standard Cisco IOS command for recovering from a BPDU Guard err-disabled state; the appropriate cause is typically `bpduguard`.

CIt remains in err-disabled state until the no shutdown command is entered in the interface

Simply entering `no shutdown` after a port is err-disabled is often insufficient for recovery; a `shutdown` command is usually needed first to completely reset the interface state before `no shutdown` can bring it back up.

DIt remains in err-disabled state until the spanning-tree portfast bpduguard disable command is

The command `spanning-tree portfast bpduguard disable` is not a valid or appropriate command for recovering an err-disabled port; the correct command for controlling BPDU Guard is `spanning-tree bpduguard enable` or `no spanning-tree bpduguard enable`.

Concept tested: BPDU Guard err-disable recovery

Source: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_55_se/configuration/guide/3560scg/swstp.html#wp1074092

Topics

#BPDU Guard#Err-disabled state#Interface recovery#Spanning Tree Protocol

Community Discussion

No community discussion yet for this question.

Full 350-401 Practice