220-1102 CompTIA A+ Troubleshooting Methodology Practice Question
A technician is following the CompTIA A+ troubleshooting methodology to resolve a computer issue. After establishing a theory of probable cause, which step should the technician perform NEXT?
⚠ Common exam trap
Many exam-takers confuse the order of steps, jumping to planning or implementation without first verifying the theory, which can lead to incorrect solutions and wasted time.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Test the theory to determine the cause.
According to the CompTIA A+ troubleshooting methodology, after establishing a theory of probable cause, the next step is to test the theory to determine the actual cause. This ensures the technician validates the hypothesis before moving on to planning or implementing a solution, preventing wasted effort on incorrect fixes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Test the theory to determine the cause.
Why this is correct
In the third step of CompTIA's standard troubleshooting methodology, you validate or refute your working hypothesis by testing the suspected cause in a controlled way—for example, swapping a component with a known-good part, running a diagnostic, or measuring voltages. If the test reproduces and confirms the failure mode, you have isolated the root cause and can confidently move to planning; if not, you return to forming a new theory. This step prevents wasted effort by ensuring the solution actually addresses the underlying problem.
- ✗
Establish a plan of action to resolve the problem.
Why it's wrong here
Establishing a plan of action is the fourth step, not the third, and it only begins after a theory has been tested and confirmed. At step three, you do not yet know the true cause, so planning would be based on an unverified guess. A proper plan here would also need to include step-by-step tasks, potential side effects, and rollback steps—none of which are appropriate until the root cause is proven.
- ✗
Implement the solution.
Why it's wrong here
Implementing the solution is the fifth step, because it requires a confirmed theory and an approved plan before any change is made to the system. Jumping directly to implementation at step three risks replacing parts or changing settings based on a hypothesis that might be wrong, which can introduce new failures and make it harder to identify the actual fault. The correct third-step action is diagnostic verification, not remediation.
- ✗
Document findings, actions, and outcomes.
Why it's wrong here
Documenting findings, actions, and outcomes is the seventh and final step in the CompTIA A+ troubleshooting flow, performed only after you have verified full system functionality and taken steps to prevent recurrence. Placing documentation at step three would be impossible—you have not yet confirmed the cause or recorded the solution. While good technicians document throughout, the formal documentation step is a closure activity, not a diagnostic one.
Visual reference
Go deeper
Related to this question
About these practice questions
This 220-1102 question is part of Courseiva's 925-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1102 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1102 exam.