Examkin

Question

Difficulty: MediumTroubleshooting Methodology

A systems administrator is responding to an incident where a corporate database server suddenly lost network access to its storage area network (SAN). Place the following administrative actions in the correct sequential order according to the standard CompTIA troubleshooting methodology, from earliest step to latest step.

  1. 1Review SAN switch error logs and interview network storage users to gather detailed symptoms.
  2. 2Formulate a hypothesis that a recent switch firmware update corrupted the Fibre Channel port configuration.
  3. 3Roll back the Fibre Channel port configuration settings on a test port to confirm whether storage communication is restored.
  4. 4Record the root cause, configuration changes, and resolution details in the enterprise ticketing system.

Answer

The correct order follows the standard troubleshooting workflow: first gathering symptoms, followed by formulating a cause theory, testing that theory, and finally documenting the resolution.
The correct sequence adheres strictly to the CompTIA troubleshooting framework: 1. Identify the problem (gathering symptoms and logs), 2. Establish a theory of probable cause (hypothesizing corrupt configurations), 3. Test the theory to determine cause (rolling back settings on a test port), and 6. Document findings, actions, and outcomes (updating the ticketing system).

Step-by-Step Solution

1
Identify the problem by gathering symptoms and questioning users.
System logs and user accounts reveal specific port communication error messages.
Troubleshooting cannot begin effectively without fully identifying the scope and symptoms of the issue.
2
Establish a theory of probable cause.
Corrupt Fibre Channel port configurations from a recent update are hypothesized as the root cause.
Formulating a targeted theory directs testing efforts efficiently.
3
Test the theory to determine the exact cause.
Rolling back settings on a test port confirms the configuration issue was responsible.
Testing validates whether the hypothesis is correct before implementing full-scale changes.
4
Document findings, actions, and outcomes.
The ticketing system and internal wiki are updated with the issue breakdown and fix.
Proper documentation ensures organizational memory and assists future troubleshooting.

Key Concept

CompTIA 6-Step Troubleshooting Methodology
Estimated Time:1m 30s
Rate this question

Topics

Troubleshooting Methodology

More questions from this topic