Chapter 12 Flashcards
What is the first step in the troubleshooting process? (12.2.1.1)
Identify the Problem
What is the second step in the troubleshooting process? (12.2.1.1)
Estblish a theroy of probably cause?
What is the third step in the troubleshooting process? (12.2.1.1)
Test the throy to determine the cause.
What is the fourth step in the troubleshooting process? (12.2.1.1)
Estblish a plan of action to resolve the problem and implement it.
What is the fifth step in the troubleshooting process? (12.2.1.1)
Verify full system functionality
What is the sixth step in the troubleshooting process? (12.2.1.1)
Document findings, solutions, and outcomes.
What type of question is:
> “What is the first screen you see when you turn on the computer?” (12.2.1.1)
Open Ended Question
What type of question is:
> “Do you have a USB drive attached?” (12.2.1.1)
Closed Ended Question
If a computer only boots to VGA mode, What is the probable cause and possible solution? (12.2.1.2)
- Probable Cause: Corrupt Video Driver
- Possible Solution: Reinstall Video Driver
If a laptop is having data access errors and is making unusual noises, What is the probable cause and possible solution? (12.4.1.2)
- Probable Cause: Hard Drive has failed
- Possible Solution: Replace the hard drive
If a computer displays this message, What is the probable cause and possible solution? (12.3.1.2)
- Probable Cause: The Same IP address has been assigned to a different computer
- Possible Solution: Give each machine a unique IP address
If computer components are going to fail, they will fail within the first __ hours
20
If a computer can send email but not receive, What is the probable cause and possible solution? (12.3.1.2)
- Probable Cause: The inbox is full
- Possible Solution: Empty the inbox
When is the best time to see this type of error message?
When you are servicing the machine.
According to Cisco, what is a probable cause and solution if an “OS not found” error message is displayed during boot?
- Probable Cause: The MBR is corrupted
- Possible Solution: Boot into the recovery console and fix the boot record.
Other acceptable responses on 12.1.1.2