Which Troubleshooting Step Involves Checking Logs for Recent Changes?
Short answer
A Identify the problem.
Question
Key Takeaways
This question tests your knowledge of the six-step troubleshooting model, with the common trap being confusion between initial information gathering and later theory testing phases.
CompTIA Network+ N10-009 troubleshooting methodology places log review and change detection in the initial information-gathering phase. Community consensus strongly confirms that checking logs belongs to the Identify the Problem step.
Common mistake: Option C is frequently chosen because candidates assume log analysis only validates hypotheses, whereas CompTIA classifies it under initial symptom identification and data collection.
Expert Analysis
Why the Answer Is Correct
The first step of the CompTIA troubleshooting methodology is to identify the problem, which heavily relies on systematic information gathering. During this phase, technicians review system logs, monitor network traffic, and interview users to detect patterns, errors, or recent configuration changes. Checking logs aligns directly with collecting baseline data and understanding the scope of the issue before forming hypotheses.
Why the Other Options Are Wrong
Testing a theory (Option C) occurs after you have already gathered initial data and formulated a likely cause; at that stage, you actively isolate variables rather than just reviewing historical logs. Establishing a plan of action (Option D) focuses on risk assessment and implementation steps, not diagnostic data collection. Documenting findings (Option B) happens exclusively at the end of the process to record resolutions and lessons learned.
Community Comment Notes
The majority of voters correctly selected Option A, noting that log reviews are fundamental to the initial information-gathering phase. One highly voted comment highlighted that looking for what has changed is a classic symptom identification technique used early in troubleshooting. While another commenter suggested Option C, official CompTIA training materials consistently categorize log analysis under the first step to prevent premature theorizing.
Official Reference
These links open the official vendor documentation in a new tab.
Exam Strategy
Memorize the exact sequence of the six-step troubleshooting model and associate specific actions like log reviews, ping tests, or rollback plans with their corresponding phases. Practice mapping real-world scenarios to each step to avoid mixing up information gathering with hypothesis validation.
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
HeatSquad77 👍 3 Answered AA. Identify the problem. Explanation: Identify the problem is the first step in the troubleshooting methodology. During this step, you gather information about the issue, which may include checking logs for recent changes or any abnormal system behavior. This helps in understanding the scope of the problem and identifying potential causes.
-
escomgmt 👍 1C. Test the theory to determine cause. In the troubleshooting methodology, when you're testing the theory to determine the cause of a problem, you would typically check logs for recent changes to help identify potential causes of the issue. Checking logs is part of the diagnostic process to verify your theory or gather further insights into the problem.
-
LibPekin 👍 1 Answered AA. Identify the problem sample, looking for what has changed.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All N10-009 Questions
Access 100 questions with complete answers and detailed explanations.
View Full N10-009 Practice Test →