S22-Troubleshooting Methodology Flashcards

(50 cards)

1
Q

What are the 7 steps in Network Troubleshooting Methodology?

A

1 - Identify Problem
2 - Establish theory of probable cause
3 - Test theory to determine cause
4 - Establish plan to resolve problem
5 - Implement solution or escalate
6 - Verify system functionality & implement preventative measures
7 - Document findings, actions, outcomes, and lessons learned

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

What are some Key information gathering questions you can ask when trying to identify the problem?

A
  • What happened?
  • What was the Status before?
  • What is the status after that?
  • Was there any change in the system?
  • What have you done so far?
  • does anyone else have the same issue?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What should you do at step 1 before proceeding with further troubleshooting steps?

A

Backup The system

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

Step 1 of troubleshooting methodology

A

Identify Problem

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

True or False: The second step in the troubleshooting methodology is to establish a theory of probable cause.

A

True.

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

Fill in the blank: The third step involves __________ the theory to determine if it is valid.

A

testing.

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

What is the fourth step in the network troubleshooting process?

A

Establish a plan of action.

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

What is the fifth step in the troubleshooting methodology?

A

Implement the solution.

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

True or False: The sixth step is to verify full system functionality.

A

True.

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

What is the final step in the network troubleshooting methodology?

A

Document findings, actions, and outcomes.

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

Short Answer: Why is documentation important in the troubleshooting process?

A

It provides a record of the problem and the solution for future reference.

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

Fill in the blank: The first step requires gathering __________ from the user.

A

information.

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

True or False: The theory of probable cause can be based solely on gut feeling.

A

False.

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

What should you do if the initial theory does not resolve the issue?

A

Establish a new theory and retest.

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

Multiple Choice: In which step do you create an action plan?

A

Fourth step.

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

Fill in the blank: When you verify functionality, you should also check __________.

A

user satisfaction.

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

Short Answer: What is the purpose of testing the theory?

A

To confirm whether the identified issue is the cause of the problem.

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

True or False: Documenting the troubleshooting process is only necessary for complex issues.

A

False.

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

What is the key benefit of following a structured troubleshooting methodology?

A

It increases the efficiency and effectiveness of resolving network issues.

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

Fill in the blank: When establishing a theory, consider __________ factors.

A

environmental.

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

Multiple Choice: Which of the following is part of the documentation process?

A

Recording the steps taken.

22
Q

Short Answer: What should you include when documenting findings?

A

Details of the problem, steps taken, and the outcome.

23
Q

True or False: The troubleshooting methodology is a linear process that cannot be revisited.

24
Q

What action should be taken if the solution does not work?

A

Reassess and establish a new theory.

25
Fill in the blank: The process of troubleshooting is often iterative, meaning it may require __________.
revisiting previous steps.
26
True or False: User feedback is irrelevant after implementing a solution.
False.
27
Short Answer: How can you ensure that the problem does not reoccur?
By documenting the solution and monitoring the system.
28
Fill in the blank: Establishing a theory involves analyzing __________.
symptoms.
29
Multiple Choice: What is the main goal of the troubleshooting methodology?
To quickly and effectively resolve network issues.
30
True or False: The troubleshooting methodology can be applied to both hardware and software issues.
True.
31
What should be done before implementing a solution?
Establish a plan of action.
32
Fill in the blank: After verifying system functionality, you must __________ your findings.
document.
33
Multiple Choice: Which of the following is an important aspect of the testing phase?
Monitoring for any recurrence of the issue.
34
True or False: A successful troubleshooting process requires collaboration with users.
True.
35
What is the primary focus during the identification of the problem?
Gathering detailed information about the symptoms.
36
Probable Cause
The most likely cause among all
37
Primary action in step 2 of the troubleshooting methodology?
Research & Inspection to find probably cause
38
Primary action in step 1 of the troubleshooting methodology?
Information gathering
39
Internal Research vs External research
Internal: - Research conducted using internal systems, diagnostic tools and logs External: - research conducted using external documentation over the internet.
40
What is the Top-to-Bottom approach when establishing a theory?
Using the OSI model to troubleshoot starting from layer 7 downward
41
What is the Bottom- Up approach when establishing a theory?
Using the OSI model to troubleshoot starting from layer 1 upward
42
What is the "divide & conquer" approach when establishing a theory?
Conducting troubleshooting starting from the middle of the OSI stack
43
when conducting research on an issue its always good to..?
Question the Obvious
44
What is step 3 in the troubleshooting methodology?
Test the theory
45
What are the 4 possible outcomes of testing your theroy?
- Theory Confirmed - Theory not confirmed - Lack of skills or authority - Inability to solve
46
Step 4 of troubleshooting methodology?
Establish Plan of action
47
Step 5 of troubleshooting methodology?
Implement the solution or Escalate
48
Important considerations when establishing a plan of action
How much resources How much time How much cost potential impacts
49
Step 6 of troubleshooting methodology?
Verify System Functionality & implement preventative measures
50
Step 7 of troubleshooting methodology?
Document, findings, actions and outcomes