-: In this section of the course, we're going to dive deeper
into the CompTIA troubleshooting methodology.
Now, you might remember from our earlier lesson
all the way back in section one
where we discussed the six steps
of the troubleshooting methodology.
Now, if you don't remember that lesson,
we're going to do a quick review
because I know that was a while ago.
First, identify the problem.
Second, establish a theory.
Third, test the theory.
Fourth, establish a plan of action.
Fifth, verify system functionality
and sixth, documentation.
Now, I know this is a bit of an oversimplification
of the six steps but in this section of the course
we're going to spend one lesson on each of these six steps
so we can explore each one in more depth
because you are going to get several questions on the exam
concerning this six step troubleshooting process
that's going to be written in a lot of different ways.
So this goes beyond just memorizing the six steps
but you also need to understand them.
So, as we move through this section
we're going to be focused on domain five,
hardware and network troubleshooting
as we fully cover objective 5.1.
Objective 5.1 states that given a scenario
you must be able to apply the best practice methodology
to resolve problems.
So, let's get started with our in-depth coverage
of the six-step troubleshooting methodology
in this section of the course.