CompTIA N10-009 Cabling and Hardware Issues Guide

Physical troubleshooting questions are evidence questions. CompTIA wants to know whether you can recognize the clues that point to cable damage, poor termination, transceiver mismatch, or failing hardware before you start blaming routing or services. A link light alone is not enough evidence.

CRC error: A frame-check failure that can indicate corruption on the link or medium.

Optical transceiver: A removable module such as SFP or SFP+ that connects a switch or router interface to fiber media.

Duplex mismatch: A condition where one side of a link uses a different duplex mode than the other, often causing late collisions, errors, or poor performance.

What CompTIA is really testing

The exam usually wants you to separate:

• physical-medium problems from logical-path problems
• interface-counter evidence from user symptom language
• port or optics mismatch from upstream routing failure
• intermittent hardware degradation from total device failure

Symptom-to-layer triage

Read the interface evidence first

1Gi1/0/12 is up, line protocol is up
2input errors 57, CRC 42, frame 9
3output errors 0

What to notice:

• the interface being “up” does not mean the link is healthy
• CRC and frame errors suggest the medium or physical signaling deserves investigation
• this is stronger evidence for a link-quality problem than for a DNS or routing problem

Common physical-layer causes

Copper versus fiber clues

Link lights are only one clue

CompTIA likes this trap:

“The port light is on, so the cable must be fine.”

That is weak reasoning. A port can show link while still producing:

• corruption
• negotiation mismatch
• intermittent drops
• low-quality optical signaling

Practical physical-troubleshooting path

    flowchart TD
	  A["Link or interface issue"] --> B{"Link state"}
	  B -->|Down| C["Check cable seating, power, port, and transceiver presence"]
	  B -->|Up with errors| D["Check counters, termination, signal quality, and mismatch"]
	  D --> E["Swap smallest suspect component"]
	  C --> E
	  E --> F["Retest interface status and counters"]

What to notice:

• link-down and link-up-with-errors are different troubleshooting branches
• counters matter more than user language such as “the network is broken”
• the smallest suspect component should be swapped first to keep the test clean

Small escalation sequence

1. Check interface status and counters.
2. Confirm cable, connector, and transceiver type.
3. Swap the simplest suspect component first.
4. Re-test and compare counters or behavior.

That sequence is stronger than replacing upstream network services when the evidence is still local to the link.

Strong counter-reading habits

Common traps

• assuming link lights prove the physical layer is healthy
• blaming routing when counters point to bad media
• forgetting that transceiver and fiber mismatches are common real-world causes
• changing several physical components at once and losing the true cause

What strong answers usually do

• use counters and interface status before escalating to higher layers
• connect CRC, drops, and negotiation clues to the medium first
• swap the smallest likely component before replacing larger devices
• keep physical evidence separate from user descriptions like “the network is slow”
• separate copper, fiber, and interface-negotiation clues instead of flattening them into one generic hardware bucket

Decision order that usually wins

Physical-layer troubleshooting starts with evidence from the link itself. Rising CRCs, late collisions, flaps, or negotiation problems point toward media, optics, connectors, or duplex. A link light alone is not enough. If the issue started after transceiver or cabling work, suspect compatibility or polarity before higher-layer services. Network+ usually wants you to clear the physical path first when the counters point there.

Quiz

Continue with 5.3 Services, Routing & Switching to keep the domain flow intact.