Examkin

Question

Difficulty: Very hardCompTIA Troubleshooting Methodology

A enterprise network administrator receives multiple urgent tickets reporting intermittent database connection timeouts immediately following an after-hours core switch firmware upgrade. Place the following troubleshooting steps in the exact chronological sequence mandated by the official CompTIA Network+ Troubleshooting Methodology, starting with the earliest step and ending with the final step.

  1. 1Interview affected database administrators, examine core switch syslog messages, and replicate the packet loss on a test client to precisely define the scope and symptoms.
  2. 2Develop a hypothesis considering OSI Layer 2 issues, questioning whether the firmware upgrade reset the native VLAN configuration on the 802.1Q trunk links.
  3. 3Capture network traffic on a test port using a packet analyzer to verify if database VLAN traffic is dropping due to tagged/untagged frame mismatch.
  4. 4Draft a change management ticket outlining trunk configuration steps and roll-back procedures, obtain approval, and reconfigure the trunk's native VLAN.
  5. 5Perform automated database query tests across all client subnets to confirm stability, and enforce configuration compliance checks on switch ports.
  6. 6Log the root cause, configuration changes, and verification test results in the organization's centralized ticketing system and knowledge base.

Answer

The correct sequence follows the official 6-step CompTIA Troubleshooting Methodology: 1. Identify the problem (information gathering, symptoms, duplication), 2. Establish a theory of probable cause (question obvious, OSI model approach), 3. Test the theory to determine cause, 4. Establish a plan of action to resolve the problem and implement the solution, 5. Verify full system functionality and implement preventive measures, 6. Document findings, actions, and outcomes.
The CompTIA Troubleshooting Methodology defines a strict six-step linear order: Step 1 is identifying the problem (gathering information, interviewing users, checking logs, replicating symptoms); Step 2 is establishing a theory of probable cause; Step 3 is testing the theory to determine cause; Step 4 is establishing a plan of action and implementing the solution; Step 5 is verifying full system functionality and implementing preventive measures; Step 6 is documenting findings, actions, and outcomes.

Step-by-Step Solution

1
Identify the Problem
Information gathered from user interviews, switch logs, and symptom replication on a test client.
Before forming hypotheses or taking administrative action, the technician must clearly define the problem scope and reproduce symptoms.
2
Establish a Theory of Probable Cause
Formulate a hypothesis regarding trunk native VLAN reset during firmware update.
Technicians must evaluate possible causes using top-to-bottom or bottom-to-top OSI methods while questioning the obvious.
3
Test the Theory to Determine Cause
Packet capture confirms untagged frame drops caused by native VLAN mismatch.
The theory must be empirically tested before making infrastructure or configuration modifications.
4
Establish a Plan of Action and Implement Solution
Draft change request, evaluate risk, acquire approval, and apply configuration fix.
Changes must be planned to minimize secondary impacts before implementing the fix.
5
Verify Full System Functionality & Implement Preventive Measures
Execute query benchmarks across subnets and deploy compliance monitoring.
System-wide operation must be confirmed working post-fix, followed by proactive measures to avoid recurrence.
6
Document Findings, Actions, and Outcomes
Record event lifecycle details in ITSM platform and update knowledge repository.
Formal documentation ensures knowledge retention and provides reference data for future operational incidents.

Key Concept

CompTIA 6-Step Troubleshooting Methodology
Rate this question

Topics

CompTIA Troubleshooting Methodology

More questions from this topic