Troubleshooting?

Gregory Childers

Well-known member
  • Oct 22, 2019
    668
    1,152
    60,126
    Safety Harbor, FL
    www.linkedin.com
    Troubleshooting is discussed in multiple CompTIA certifications. It's covered in Tech+, A+, Network+, and Cloud+ to name a few.

    What I'd like to know is why are the steps in the troubleshooting methodology different in each of the certifications. I'm teaching Cloud+ this week and there are ten steps. Tech+ and A+ have six steps. Network+ has seven steps. Shouldn't CompTIA be endorsing a consistent troubleshooting methodology across all their certifications? Isn't it more confusing for the learners to unlearn what they've learned when pursuing a new certification?
     
    Coherency / consistency would be a good thing, yeah.

    Sounds like you should be an SME for all of these... or be hired by the new CompTIA, for their over-arching exam design teams.
    Troubleshooting is one area of overlap with multiple CompTIA exams. There are several other topics that are also covered on multiple CompTIA exams.

    CompTIA needs to take a look at the exam objectives for all of its certifications to ensure that any overlapping topics are covered consistently across the board.
     
    Troubleshooting is discussed in multiple CompTIA certifications. It's covered in Tech+, A+, Network+, and Cloud+ to name a few.

    What I'd like to know is why are the steps in the troubleshooting methodology different in each of the certifications. I'm teaching Cloud+ this week and there are ten steps. Tech+ and A+ have six steps. Network+ has seven steps. Shouldn't CompTIA be endorsing a consistent troubleshooting methodology across all their certifications? Isn't it more confusing for the learners to unlearn what they've learned when pursuing a new certification?
    A far better question than what we've been seeing lately, Greg. This one isn't laughably simplistic and can't be answered with a simple Google search.

    So...

    IMAO, I think what's happening here is a product of evolution. As CompTIA has developed certifications over the years, the infamous Troubleshooting Model has gone through iterations where one step gets added, one step deleted. Maybe it's been adapted for specific settings like hardware (A+), networking, or Cloud. But I think somewhere along the line, an SME somewhere said, "Yeah, that's correct, *but* we need to add this one additional step..."

    That's my two denarii, anyway.

    /r
     
    They removed the troubleshooting methodology from the latest Cloud+. They said it's because you really can't have a rigid set of steps and there needs to be more room for flexibility, critical thinking, and intuition.
    Sounds completely plausible, because, at the end, troubleshooting is just as much an art as it is a science.
     
    Troubleshooting is discussed in multiple CompTIA certifications. It's covered in Tech+, A+, Network+, and Cloud+ to name a few.

    What I'd like to know is why are the steps in the troubleshooting methodology different in each of the certifications. I'm teaching Cloud+ this week and there are ten steps. Tech+ and A+ have six steps. Network+ has seven steps. Shouldn't CompTIA be endorsing a consistent troubleshooting methodology across all their certifications? Isn't it more confusing for the learners to unlearn what they've learned when pursuing a new certification?
    I had to ask my self the very same question the time when i was preparing for Tech+ exam..CompTIA A+ its 7 steps while Tech + its 6..
     
    Troubleshooting is discussed in multiple CompTIA certifications. It's covered in Tech+, A+, Network+, and Cloud+ to name a few.

    What I'd like to know is why are the steps in the troubleshooting methodology different in each of the certifications. I'm teaching Cloud+ this week and there are ten steps. Tech+ and A+ have six steps. Network+ has seven steps. Shouldn't CompTIA be endorsing a consistent troubleshooting methodology across all their certifications? Isn't it more confusing for the learners to unlearn what they've learned when pursuing a new certification?
    YES! Thank you Greg. I brought this up when I reviewed the Cloud+ materials before publication. All I can say is that there were different writers.
     
    They removed the troubleshooting methodology from the latest Cloud+. They said it's because you really can't have a rigid set of steps and there needs to be more room for flexibility, critical thinking, and intuition.
    Those were my comments after reviewing the draft. Except for the intuition.
     
    • Like
    Reactions: Jill West