Lesson 1 Chapter 4 - Troubleshooting Flashcards

1
Q

What are the 3 basic troubleshooting steps?

A
  1. Have the right tools for the job
  2. Backup critical files before repair work
  3. Troubleshoot according to best practices (analyze, test, complete)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are FRUs and what does it stand for?

A

FRU = Field Replaceable Units

Spare parts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are 7 good troubleshooting items to carry?

A
  1. Digital multimeter
  2. USB network adapter
  3. RAM sticks (DDR2-4, DIMM and SO-DIMM forms)
  4. PCIe video card
  5. Desktop power supply
  6. ESD wrap
  7. Thermal paste
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What does ESD stand for?

A

Electrostatic Discharge

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

In terms of maintenance and troubleshooting, what should you always make sure you do first? (2)

A

Backup critical files before troubleshooting, and make sure the computers you’re in charge of are continuously backed up

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What happens if you run into a partially functional system where you’ll have to reinstall OS but you still have access to the hard drive?

A

Backup essential information

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the 4 things that should be backed up?

A
  1. emails
  2. favorites
  3. personal documents
  4. anything that isn’t backed up regularly on a server
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What’s a recovery environment available on Windows called?

A

System Recovery Options

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Define the 6 best practice methodology steps for troubleshooting

A
  1. Identify the problem, give an estimated time to repair
  2. Establish a theory of probable cause (question the obvious)
  3. Test the theory to determine the cause
  4. Establish a plan of action to resolve issue and implement it
  5. Verify full system functionality, implement preventative measures
  6. Document findings, actions, and outcomes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are 5 questions you can ask the user in your initial fact-finding analysis in the first step of troubleshooting?

A
  1. When did it start?
  2. Is it intermittent or constant?
  3. If it’s intermittent do you notice a pattern or situation of when it’s more likely to occur?
  4. Have you noticed anything unusual in your work area like environmental or infrastructure changes?
  5. Do you remember anything happening right before the problem started?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

How do you view system/application log files on Windows?

A

Event Viewer Utility

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What 5 questions can you ask yourself to establish a theory of probable cause to narrow down the differential diagnosis?

A
  1. Is it a hardware or software issue?
  2. If it’s software, is it an application issue or an OS issue?
  3. Does the issue happen in only one application?
  4. Does the issue happen system-wide no matter the applications running?
  5. Did I check the system/application log files using the Event Viewer utility?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the 2 main points in establishing a plan of action?

input, options

A
  1. When you have options, need to do some critical thinking and get the end user’s input if necessary (like install new hardware or not?)
  2. Let the customer know about their options (repair vs replace, cost-benefit analysis)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

How do you verify system functionality after implementing a repair/fix?

A

Don’t just walk away, make sure the user can accomplish all their main tasks and put the system through its paces

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are the 5 things to include in troubleshooting documentation?

A
  1. What is the problem
  2. Summary of the solution
  3. Space where work performed can be itemized
  4. Hours spent resolving the issue
  5. List parts that were replaced
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are 2 questions to ask yourself when trying to identify the problem?

A
  1. What can it be?
  2. Do I understand the nature of the problem? Do I need more user input?