0% found this document useful (0 votes)
2 views

5.3+Questions copy

The document outlines a series of questions related to diagnosing and troubleshooting hardware and software issues. It emphasizes the importance of identifying the problem area, asking specific questions, and applying various troubleshooting methods such as bottom-up, top-down, divide-and-conquer, follow-the-path, and spot-the-differences. Additionally, it highlights the value of documenting problems and solutions for future reference.

Uploaded by

john.arnold6001
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views

5.3+Questions copy

The document outlines a series of questions related to diagnosing and troubleshooting hardware and software issues. It emphasizes the importance of identifying the problem area, asking specific questions, and applying various troubleshooting methods such as bottom-up, top-down, divide-and-conquer, follow-the-path, and spot-the-differences. Additionally, it highlights the value of documenting problems and solutions for future reference.

Uploaded by

john.arnold6001
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Name: Period: Date:

5.3 Questions – Type your own answers NO copy and paste or AI.
1. What is the purpose and output from a diagnosis? You identify the general area or
subsection of which the problem is most likely to be contained
2. What kinds of questions can you ask to diagnose a hardware issue? If there are any
noticeable differences from how the computer normally acts (look, smell, sound)
3. What kinds of questions can you ask to diagnose a software issue? Is the problem
specific to one application, is it fixed by restarting, was it possibly due to an update
4. How does troubleshooting differ from diagnosis? Troubleshooting is the act of
attempting to solve the problem identified by the diagnosis.
5. How are hardware and software components arranged from top-to-bottom for
troubleshooting purposes? Operating System: Apps; Device Drivers: Apps;
Motherboard: Video, Network, Memory, CPU; Storage: Hard Disk, CD Drive, USB;
Power: Supply, Cables
6. How do you apply "bottom-up" troubleshooting? Look at hardware then software
7. How do you apply "top-down" troubleshooting? Look at software then hardware
8. How do you apply "divide-and-conquer" troubleshooting? Test whether issue is top or
bottom
9. How do you apply "follow-the-path" troubleshooting? Follow movement of data to find
problem
10. How do you apply "spot-the-differences" troubleshooting? Compare to a working
computer to find the problem
11. What is a hypothesis? A guess at what is causing the problem
12. Why is it a good idea to document your problem and final solution? It can help others
who have the same problem

You might also like