220-1101 - Hardware and Network Troubleshooting (29% of the exam) - Section 5.1

Apply the best practice methodology to resolve problems, following the ordered CompTIA troubleshooting steps from identifying the problem through documenting findings.

Apply the six-step CompTIA troubleshooting methodology in order: identify the problem, establish a theory of probable cause, test the theory, establish and implement a plan of action, verify full system functionality with preventive measures, and document findings, actions, and outcomes. Recognise that escalating or backing up data may be required before changes, and never skip verification or documentation.

Troubleshooting methodologyTheory of probable causeVerify functionalityDocument findings

Practice question for this objective

Free sampleHardware and Network Troubleshootingeasy

Priya, a help desk technician, has just confirmed with a caller that a printer sometimes drops offline when a nearby microwave runs. Following the CompTIA six-step methodology, what should she do immediately after identifying the problem?

AMove the printer to a wired connection and confirm the fault is gone
BEstablish a theory of probable cause, considering that 2.4 GHz interference may be involved Correct
CDocument the findings, actions taken, and the final outcome in the ticket
DVerify full system functionality and advise the user on preventive measures

After identifying a problem, the next CompTIA methodology step is to establish a theory of probable cause before testing or fixing anything. The CompTIA sequence is fixed: identify the problem, then establish a theory of probable cause. Forming a hypothesis before implementing a fix prevents wasted effort and keeps the diagnosis evidence-driven.

Why A is wrong: Implementing a fix is tempting because it sounds decisive, but a plan of action is step four and cannot precede forming and testing a theory.

Why B is correct: After identifying the problem, the second CompTIA step is to establish a theory of probable cause, and interference is a reasonable hypothesis here.

Why C is wrong: Documentation feels like good discipline, but it is the final CompTIA step and premature before any cause has been established.

Why D is wrong: Verifying functionality matters, but it is step five and applies only after a fix has been implemented, not right after identification.

See more 220-1101 practice questions, answers explained.

Exam traps in Hardware and Network Troubleshooting

Answers that look right on this material and are not. Each one is a distractor from a different question in the 220-1101 bank for this domain.

Establish a fresh theory of probable cause for future faults
Why it is wrong: Forming a new theory is unnecessary because the identified fault has already been fixed and no new symptom is present.
Establish a fresh theory of probable cause in case the same drive drops out again later
Why it is wrong: It sounds thorough, but a theory is only established while a problem is still unresolved; the drive is already detected, so this step does not apply here.
Replace the power supply unit and confirm the shutdowns have stopped
Why it is wrong: Swapping the PSU is a plan-of-action step, and it may well be the fix, but it is premature until a theory is formed and tested; jumping straight to a part swap skips two ordered steps.

Examworthy is not affiliated with or endorsed by CompTIA. Original, blueprint-aligned practice material only.