NET+ N10-009 V9 Network troubleshooting Runs in your browser · no setup Original practice · Review pending

Triage three physical-layer failures

Read optics, wiremap, and PoE evidence; choose the cause, tool, and safe troubleshooting sequence.

Estimated13 min

DifficultyIntermediate

Points11

Content record

Original practice · Review pending

Mapped to CompTIA N10-009 objectives · Internal validation 2026-09-15 · Original ITForMe practice mapped to published objectives; not an official exam question. A named independent subject-matter expert has not yet verified the question and answer key.

Community review →

1.5Compare and contrast transmission media and transceivers. 5.2Given a scenario, troubleshoot common cabling and physical interface issues. 5.5Given a scenario, use the appropriate tool or protocol to solve networking issues. 5.1Explain the troubleshooting methodology.

Show review record and official sources

Method: Mapped to N10-009 media, physical-installation, methodology, and physical-interface troubleshooting objectives; raw fiber, copper wiremap, and PoE measurements plus competing diagnoses were rechecked after difficulty-calibration feedback.

Current-profile check: 2026-08-12 · Next review due 2027-02-08

Inspect the evidence

Use only the information provided to complete the tasks.

Closeout notes and current measurements

table

Ticket	Refresh record	Current observation
U1 — closet uplink	Existing OM3 LC run retained; closet optic changed to GLC-SX-MMD, core optic recorded as GLC-LH-SMD	Both interfaces are enabled but remain down/down; labels show 850 nm on the closet optic and 1310 nm on the core optic
A17 — access point	AP-17 moved from a 15.4 W model to a 25.5 W model; port and AP both advertise 802.3at	show power inline: available=370.0 W, used=369.0 W; Gi1/0/17 mode=auto, state=off, draw=0.0 W, device=Ieee PD, requested=25.5 W
C22 — desk cable	Patch leads test good; permanent link drawing lists an 86 m run to jack C22	Certifier result: FAIL; pair lengths 1-2=84 m, 3-6=86 m, 4-5=86 m, 7-8=86 m; fault distance=84 m

If columns are offscreen, scroll sideways or focus the table and use arrow keys.

Unchanged conditions

list

›U1 connector end faces were cleaned and reseated; neither end records receive light.
›A17 joins the wireless controller normally when powered from a bench injector.
›C22's switch port records no excessive errors on a known-good short cable.

Complete the response

Partial credit is available for matching, ordering, and multi-select tasks.

Changes will save automatically.

matching

Match each ticket to the conclusion best supported by all of its measurements.

3 pts

U1 — fiber uplink → A17 — access point → C22 — copper run →

Need a hint?

Start with the row and choice that have the most distinctive purpose, then use that pair to narrow the rest.

Show another hint

For each remaining pair, explain the relationship in one sentence before selecting it.

multi select

Select the THREE next checks that can confirm the inferred fault before a repair is authorized.

3 pts

Compare both optic part numbers against the supported matrix, then measure transmit and receive power at U1 Review per-port allocation and total supply capacity, then validate A17 with a correctly rated inline tester if needed Repeat the permanent-link certification and inspect the C22 jack and patch-panel termination near the measured distance Survey 2.4 GHz airtime before checking whether A17 can receive operating power Use continuous ping alone to distinguish wavelength, power-allocation, and conductor faults while all three links are down

Need a hint?

Evaluate each option independently against the scenario evidence instead of treating the list as one decision.

Show another hint

Choose only options that directly satisfy the prompt; being generally true is not enough.

ordering

Order the general workflow to resolve one ticket without creating a second fault.

5 pts

Drag the rows or use the arrow buttons to reorder.

1 Identify the ticket, gather baseline evidence, and confirm what changed
2 Form one evidence-backed probable cause for that ticket
3 Test the theory with the appropriate meter, status output, or known-good compatible component
4 Plan impact, implement the narrow repair, and escalate if authorization or design must change
5 Verify physical status and end-to-end function, then document cause, action, and preventive measure

Use this order as my answer

Need a hint?

Identify the prerequisite that must happen first and the verification or documentation that belongs last.

Show another hint

For the middle steps, ask what must already be true before each action can safely happen.

Ready to check your work?Unanswered tasks and matches earn no points. A partial submission is scored and saved in your history.

Persistent progress

Attempt history

Every submission is retained. Starting another attempt never replaces or unlocks the previous one.

No attempts yet

Your first submitted score and detailed answer review will appear here.

Community quality control

Question or answer look wrong?

Proposals and votes help staff prioritize review. They never change the scoring key automatically.

Full review queue →

No community corrections yet

Be the first to flag unclear wording, an answer-key issue, or a source that needs another look.

Propose a correction

Original practice · Review pending

Inspect the evidence

Complete the response

Review your result

Attempt history

Question or answer look wrong?