IT FundamentalsA+

CompTIA A+ Troubleshooting Methodology

The CompTIA A+ troubleshooting methodology is a structured 6-step process tested on both 220-1101 and 220-1102 exams. Following a systematic approach prevents technicians from jumping to conclusions, missing root causes, or creating new problems while fixing existing ones. Mastering this methodology is both an exam requirement and the foundation of professional IT support.

7 min

1 sections · 7 exam key points

1 practice questions

The 6-Step CompTIA Troubleshooting Process

Step 1 — Identify the problem: gather information. Ask the user: What exactly is happening? When did it start? Has anything changed recently (updates, new software, hardware)? Has it happened before? Who else is affected? Reproduce the problem if possible. Identify error messages (record exactly). Check environmental factors (power, heat, physical damage). Question the obvious — users don't always volunteer all relevant information.

Step 2 — Establish a theory of probable cause (question the obvious): based on the information gathered, develop the most likely explanation. Start with the simplest/most common causes (cable unplugged, wrong settings, user error) before assuming hardware failure. Consider all possibilities — physical layer (cable, connector), OS, application, configuration, user error. OSI model bottom-up approach for network issues: physical → data link → network → transport → application.

Step 3 — Test the theory to determine the cause: perform a quick, reversible test to confirm or deny your theory. If the theory is confirmed — proceed to fix. If the theory is not confirmed — establish a new theory and test again. Log what you test and what results you get.

Step 4 — Establish a plan of action to resolve the problem and implement the solution: once the cause is confirmed, plan the fix. Consider: backup before making changes, impact on other systems/users, change management process (for enterprise environments). Then implement the solution. Be methodical — change one thing at a time.

Step 5 — Verify full system functionality and implement preventive measures: after the fix, verify the original problem is resolved AND that you haven't created new problems. Test the full workflow, not just the specific symptom. If applicable, implement preventive measures (update firmware, install security updates, configure monitoring).

Step 6 — Document findings, actions, and outcomes: record what the problem was, what caused it, how it was fixed, and what preventive measures were taken. Update the ticketing system with complete notes. Good documentation enables: faster resolution of repeat issues, knowledge base for other technicians, audit trail for compliance, trend analysis to identify systemic problems.

Key exam facts — A+

Step 1: Identify the problem — gather info, ask user, reproduce, check for recent changes
Step 2: Theory of probable cause — simplest/most likely first
Step 3: Test the theory — quick, reversible tests to confirm or deny
Step 4: Plan of action, backup before changes, implement solution
Step 5: Verify full system functionality + implement preventive measures
Step 6: Document findings, actions, outcomes in ticketing system
Never skip documentation — enables future technicians and identifies recurring problems

Common exam traps

Good troubleshooters fix problems without following a formal process

Skipping steps leads to: treating symptoms not root causes (problem recurs), creating new problems while fixing others, wasting time on complex solutions when simple ones would work, and lack of documentation that wastes future troubleshooting time. Experienced technicians follow the methodology quickly and intuitively — but they still follow it

Practice questions — Troubleshooting Methodology

These questions are representative of what you will see on A+ exams. The correct answer and explanation are shown immediately below each question.

Q1.A user reports their computer won't connect to the internet. After verifying the physical cable is connected and the router is online, the technician notices all other devices on the network work fine. Which troubleshooting step is the technician currently performing?

A.Step 4 — Establish a plan of action

B.Step 5 — Verify full system functionality

C.Step 2 — Establishing a theory of probable cause

D.Step 6 — Document findings

Explanation: The technician is gathering evidence and ruling out possibilities to narrow down the probable cause — physical layer is fine (cable connected), network infrastructure is fine (router/other devices work), so the problem is likely isolated to this specific computer's configuration (IP settings, driver, NIC). This systematic elimination of possible causes is Step 2: establishing a theory of probable cause. The likely theory: the computer's TCP/IP configuration is incorrect, the NIC driver has an issue, or a firewall rule is blocking the connection.

Frequently asked questions — Troubleshooting Methodology

When should you escalate a problem instead of continuing to troubleshoot?

Escalate when: the problem requires access, permissions, or skills beyond your authorization level (e.g., server configuration, database changes). The problem has not been resolved after a reasonable troubleshooting effort and your theories are exhausted. The issue involves potential security incident (beyond normal troubleshooting scope — requires security team). The fix requires downtime that must be scheduled. A more experienced technician or specialist has domain expertise that would resolve it faster. Escalation is not failure — knowing when to escalate is a professional skill that saves time and prevents damage from attempting fixes beyond your competency.

Practice this topic

A+practice questions

Test yourself on Troubleshooting Methodology

JT Exams routes you to questions in your exact weak areas — automatically, after every session.

Free practice test Start 7-Day Free Trial

No credit card · Cancel anytime