CH 1: Saftey and Professionalism Flashcards

1
Q

Troubleshooting Theory:
core 1: (220-1001)

Consideration

A

Always consider corporate policies, procedures, and impacts before implementing changes.

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

Troubleshooting Theory:
core 1: (220-1001)

First step - question the user

inquire regarding environmental or infrastructure changes

A

Identify the problem

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

Troubleshooting Theory:
core 1: (220-1001)

Look at system logs

A

To identify problems

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

Troubleshooting Theory:
core 1: (220-1001)

Step 2: Establish a theory of probable cause

A

Question the obvious

Look from airplane mode

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

Troubleshooting Theory:
core 1: (220-1001)

Step 3: Test the theory to determine the cause

A

Take it out of airplane mode and walah

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

Troubleshooting Theory:
core 1: (220-1001)

Step 3a: If the theory isn’t confirmed, re-establish a new one

A

Look at the problem from a different angle.

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

Troubleshooting Theory:
core 1: (220-1001)

Step 3b: Escalate the issue, if necessary

A

Call in for some help.

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

Troubleshooting Theory:
core 1: (220-1001)

Step 4: Establish a plan of action to both resolve the problem and to implement a solution.

A

Keep looking - until the user is happy

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

Troubleshooting Theory:
core 1: (220-1001)

Step 5: Verify full system functionality and, if applicable, implement preventative measures.

A

Tell the user to take pc out of airplane mode and check for other things if necessary

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

Troubleshooting Theory:
core 1: (220-1001)

Step 6: Documentation

A

Document findings, actions and outcomes

add to list of Lessons Learned

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

Troubleshooting Theory:
core 1: (220-1001)

Step 1: Identify

A

Identify Problem

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

Troubleshooting Theory:
core 1: (220-1001)

Step 2: Theory

A

Establish a theory of probable cause

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

Troubleshooting Theory:
core 1: (220-1001)

step 3: Test

A

Test the theory to determine cause

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

Troubleshooting Theory:
core 1: (220-1001)

Step 4: Plan

A

Establish a plan of action to resolve the problem and implement a solution

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

Troubleshooting Theory:
core 1: (220-1001)

Step 5: Verify

A

Verify full system functionality and, if applicable, implement preventive measures.

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

Troubleshooting Theory:
core 1: (220-1001)

Step 6: Document

A

Document findings, actions and outcome

17
Q

Troubleshooting Theory:
core 1: (220-1001)

ITTPVD -

I’d theorize that Test Plans Verify Documentation

A

ITTPVD

18
Q

What item is not likely to found in a tech’s toolkit

A

EMP - Electromagnetic Pulse - not a tool - it is a cause of problems

19
Q

A tech might use a voltage tester or or this tool to check power coming out of a wall socket

A

Voltmeter used to test wall power.

20
Q

The first step in troubleshooting is

A

Identify the problem

21
Q

After a problem is solved what is the appropriate next step.

A

Take preventative measures (including teaching the customer how to avoid the problem in the future).

22
Q

Replacing components

A

its part of problem solving - not something done after the problem is solved

23
Q

You need to identify a problem BEFORE

A

you SOLVE it

24
Q

Teaching jargon to customers

A

while fun is not necessary