Examkin

Question

Difficulty: MediumCompTIA Troubleshooting Methodology

A network administrator receives multiple alerts indicating severe latency and packet drops across a enterprise wireless network deployment following a software update on the central wireless LAN controller (WLC). Arrange the technician's troubleshooting actions in the correct sequence according to the CompTIA troubleshooting methodology, from first step to last step.

  1. 1Gather network logs from the central WLC and query affected users regarding the specific location and symptoms of the performance degradation.
  2. 2Formulate a hypothesis that a newly introduced radio resource management (RRM) bug in the updated firmware is causing channel overlap and co-channel interference.
  3. 3Execute a spectrum analyzer scan on a isolated test Access Point running the updated firmware to confirm elevated noise floor levels.
  4. 4Draft a change request detailing a step-by-step firmware rollback procedure and identifying potential temporary downtime for connected wireless clients.
  5. 5Conduct RF signal strength heat map tests across all client floors and verify that signal-to-noise ratios have returned to baseline parameters.
  6. 6Update the organizational knowledge base with the firmware issue details, workaround configuration, and vendor bug tracking ID.

Answer

The correct chronological sequence of the CompTIA troubleshooting methodology is: Gather network logs and query affected users (Identify the problem) → Formulate a hypothesis regarding the RRM firmware bug (Establish a theory of probable cause) → Execute a spectrum analyzer scan on a test AP (Test the theory) → Draft a change request and identify potential side effects (Establish a plan of action) → Conduct heat map tests to ensure baseline performance (Verify full system functionality) → Update the organizational knowledge base (Document findings, actions, and outcomes).
The correct order follows CompTIA's official standard methodology: 1. Identify the problem (gather logs and user feedback), 2. Establish a theory of probable cause (hypothesize firmware/RRM issue), 3. Test the theory (use spectrum analyzer on a test AP), 4. Establish a plan of action and identify potential effects (draft change request and rollback plan), 5. Verify full system functionality (run RF heat map tests to verify baseline metrics), and 6. Document findings, actions, and outcomes (update the organizational knowledge base).

Step-by-Step Solution

1
Identify the problem
Network logs and user interviews define the problem scope and symptoms.
Troubleshooting must begin with gathering facts and defining the issue before assuming a cause.
2
Establish a theory of probable cause
A working hypothesis pointing to RRM firmware channel overlap is established.
Considering recent changes like firmware updates helps form a logical theory.
3
Test the theory to determine cause
Spectrum analysis confirms elevated noise floor on test equipment.
The theory must be verified scientifically before making production changes.
4
Establish a plan of action and identify potential effects
A rollback plan and risk assessment are documented.
Planning ensures changes are controlled and potential side effects are anticipated.
5
Verify full system functionality
RF heat maps verify signal metrics are back to normal standards.
System verification confirms that the resolution actually resolved the original issue completely.
6
Document findings, actions, and outcomes
Knowledge base updated for future reference.
Documentation creates an audit trail and assists future troubleshooting efforts.

Key Concept

CompTIA 7-Step Troubleshooting Methodology
Rate this question

Topics

CompTIA Troubleshooting Methodology

More questions from this topic