I'm confused between the test a theory and implement the action steps. If my theory was the power cord was unplugged and I test it by plugging it back in and now everything is handy dandy, what plan am I establishing and implementing??? Or am I just looking at this wrong?
Sometimes the two steps act as one, especially for simple solutions like with what you said The steps are moreso in place for larger scale problems, say for instance malware, identify the problem (say you cant access x software idk) > establish a theory (ermmmm le malware?) > test the theory (confirm le malware) > plan and implement ((plan):determine which antimalware to run, (implement): run it) > etc > etc.. Keep in mind that this is compTIA's troubleshooting process, companies may use their own process that works for them so dont be surprised if you're not deploying this in the field, hope that helps :)
An implementation window I believe. Like say a company says "You have between Tuesday 5pm and 8pm to implement changes/plans. (Hence messages some products send out saying, "expect a downtime between so and so times")
Thank you professor! Good luck to everyone, we've got this!
1:40
I LOVE this.
It is an incredibly scientific way of solving problems. So much so that this pretty much is how Scientific Hypothesis are made.
almost to the promise land
Right behind you
with you
almooost theere
Still got core 2, bb
final stretch, baby
I (Identify)
Enjoy (Establish)
Taking (Test)
Peoples (Plan)
Internet (Implement)
Very (Verify)
Diligently (Document)
Makes it easier to remember
I
Eat
Tasty
People.
I'm
Very
Disgusting.
Thanks for this! Something tells me the exam is going make sure we really know this.
What about evaluate the results is it working
I enjoy taking ppl internet very diligently!
I'm confused between the test a theory and implement the action steps. If my theory was the power cord was unplugged and I test it by plugging it back in and now everything is handy dandy, what plan am I establishing and implementing??? Or am I just looking at this wrong?
Sometimes the two steps act as one, especially for simple solutions like with what you said
The steps are moreso in place for larger scale problems, say for instance malware, identify the problem (say you cant access x software idk) > establish a theory (ermmmm le malware?) > test the theory (confirm le malware) > plan and implement ((plan):determine which antimalware to run, (implement): run it) > etc > etc..
Keep in mind that this is compTIA's troubleshooting process, companies may use their own process that works for them so dont be surprised if you're not deploying this in the field, hope that helps :)
just skip - that's just if it doesn't resolve it
Great video! really helped me remember the troubleshooting process.
What does it mean to receive a "slot from the change control board"?
An implementation window I believe. Like say a company says "You have between Tuesday 5pm and 8pm to implement changes/plans. (Hence messages some products send out saying, "expect a downtime between so and so times")
This is pretty much the scientific method and that makes us all scientists XD
Nice vid Messer
I was expecting this video to explore troubleshooting strategies, like "binary division" etc.
Its CompTIA core 1 bro