FirstTry

Objective 5.2

N10-009

Given a scenario, troubleshoot common cabling and physical interface issues.

Objective 5.2 sits in Network Troubleshooting, which carries 24% of the Network+ exam. The questions below are original, written from the official objective title above, and each explanation cites the CompTIA page it rests on.

Objective title verbatim from the official objectives. CompTIA exam page ↗

A worked example

Shown solved, with the whole explanation open: this is what every question here carries.

5-2Network Troubleshooting

A technician shuts and reopens this port, and it drops back into the same state within seconds every time. What has to happen first for the port to stay up?

Switch# show interfaces status err-disabledPort      Name      Status            Reason               Err-disabled VlansGi1/0/9             err-disabled      bpduguard %PM-4-ERR_DISABLE: bpduguard error detected on Gi1/0/9, putting Gi1/0/9 in err-disable state
Remove the condition that triggered the detectionCorrect · your answerCorrect. The trigger has to go before reenabling will stick.
Shorten the errdisable recovery interval to 30 secondsA recovery timer only reenables the port on a schedule, and the same detection fires again while the cause is still present.
Clear the interface counters on the affected portClearing counters resets statistics and leaves port state untouched. It is useful for measuring whether errors are still increasing.
Move the port into a separate access VLANA different VLAN changes forwarding, not the reason the protection feature acted on that interface.

Correct.

Checked against cisco.com, August 2026

Concept

A port sitting in the error disabled state was shut by the switch itself after a protection feature fired on something it saw. Bringing the interface back is a second step, and it holds only if whatever the feature reacted to has left the link.

Why A

Cycling the interface does nothing about the traffic the feature is set to act on, so the same detection runs again as soon as the link comes up. Dealing with the offending device or cable first is what makes the port stay in service.

Source

In order to recover a port from the errdisable state, first identify and correct the root problem, and then reenable the port. If you reenable the port before you fix the root problem, the ports just become error disabled again.

Cisco: Recover Errdisable Port State on Cisco IOS Platforms, checked August 2026
#err-disabled#port-status#bpdu-guard#artifact

Now you: objective 5.2 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

5-2Network Troubleshooting

This port feeds a shared hub segment whose users describe transfers as slow. How should the ratio of input errors to input packets on it be read?

Switch# show interfaces fastethernet0/7FastEthernet0/7 is up, line protocol is up (connected)  Half-duplex, 100Mb/s, media type is 10/100BaseTX     2014338 packets input, 402188544 bytes, 0 no buffer     84602 input errors, 61140 CRC, 23462 frame, 0 overrun, 0 ignored     1043 collisions, 0 interface resets

Sample question 2 of 3

5-2Network Troubleshooting

A wall port has never linked since a refit. A technician runs a cable test from the switch and reads the output below. What should be done next?

[admin@CCR] > interface ethernet cable-test ether2      name: ether2    status: no-link cable-pairs: open:4,open:4,open:4,open:4

Sample question 3 of 3

5-2Network Troubleshooting

A switch port shows a climbing jabber counter and users on that segment report dropped sessions. What does that counter record?

Full Network+ question bank coming

We’re writing the complete bank from the official objectives right now. Leave your email and we’ll tell you when it ships, nothing else, ever.

Read the sources

These are the official pages the questions above cite. Reading them is studying the objective from the primary source, which is what the explanations point you toward anyway.

More objectives in Network Troubleshooting