15.01.2024 Views

CompTIA A+ Certification All-in-One Exam Guide

  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Troubleshooting Methodology

An effective troubleshooting methodology follows a set of steps to diagnose

and fix a computer. Troubleshooting methodology includes talking to users to

determine how and when the problem took place, determining a cause,

testing, verification, and documentation. Techs use a number of good

troubleshooting methodologies. Luckily for those taking the CompTIA A+

220-1001 certification exam, CompTIA clearly defines their vision of

troubleshooting methodology:

5.1 Given a scenario, use the best practice methodology to resolve

problems

1. Identify the problem

• Question the user and identify user changes to computer and

perform backups before making changes

• Inquire regarding environmental or infrastructure changes

• Review system and application logs

2. Establish a theory of probable cause (question the obvious)

• If necessary, conduct external or internal research based on

symptoms

3. Test the theory to determine cause

• Once the theory is confirmed, determine the next steps to

resolve problem

• If theory is not confirmed re-establish new theory or escalate

4. Establish a plan of action to resolve the problem and implement

the solution

5. Verify full system functionality and, if applicable, implement

preventive measures

6. Document findings, actions, and outcomes

Identify the Problem

There’s a reason you’re standing in front of a computer to repair it:

something happened that the user of the computer has identified as “not

good” and that’s why you’re here. First, you need to identify the problem by

talking to the user. Get the user to show you what’s not good. Is it an error

code? Is something not accessible? Is a device not responding?

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!