ITForMe Sign in
NET+ N10-009 V9 Network troubleshooting Runs in your browser · no setup Preview · not independently reviewed

Triage three physical-layer failures

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

Estimated13 min
DifficultyIntermediate
Points11
Scenario brief

Copper Finch Logistics has three unrelated tickets after a closet refresh. Treat them independently and use the existing measurements before replacing equipment. No switch configuration changes were scheduled.

Content record

Preview · not independently reviewed

Mapped to CompTIA N10-009 objectives · Internal validation 2026-08-13 · Available as preview practice, but 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. 2.4Explain important factors of physical installations. 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; fiber compatibility, copper wiremap, and PoE evidence were reviewed.

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

01

Inspect the evidence

Use only the information provided to complete the tasks.

Ticket evidence

table
TicketObserved evidenceKnown design
U1 — closet uplinkCloset: 1000BASE-SX 850 nm; core: 1000BASE-LX 1310 nm; link downExisting run is multimode fiber with LC connectors
A17 — access pointSwitch log: power denied; committed 369 W of 370 W; AP requests 25.5 WAP and port support the same PoE standard
C22 — desk cableWiremap: pair 1–2 open at 84 m; other pairs passPermanent link is 86 m and previously supported 1 Gb/s
02

Complete the response

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

01
matching

Match each ticket to the most likely root cause.

3 pts
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.

02
multi select

Select the THREE most directly useful tools or measurements for these tickets.

3 pts
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.

03
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. 1 Identify the ticket, gather baseline evidence, and confirm what changed
  2. 2 Form one evidence-backed probable cause for that ticket
  3. 3 Test the theory with the appropriate meter, status output, or known-good compatible component
  4. 4 Plan impact, implement the narrow repair, and escalate if authorization or design must change
  5. 5 Verify physical status and end-to-end function, then document cause, action, and preventive measure
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?Submit to finish this session and review your feedback. Extra practice is optional.
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