Lesson 03-A Flashcards

1
Q

What is the first step in the troubleshooting process?

A

Identify the problem

This involves establishing the consequence or impact of the issue and listing symptoms.

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

What are the three components of a problem?

A

Causes, symptoms, and consequences

Understanding these components helps in effective troubleshooting.

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

In troubleshooting, why is it important to gather information from the user?

A

Users are often the best source of information about the problem

Asking the right questions can clarify the situation.

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

What should you do before changing system configuration?

A

Perform backups

This ensures data safety before making any changes.

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

What is the purpose of establishing a theory of probable cause?

A

To identify possible causes and guide the troubleshooting process

This helps in focusing the investigation effectively.

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

What should you do if your theory is not confirmed?

A

Re-establish a new theory or escalate

This allows for continued investigation or obtaining further assistance.

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

What are the three generic approaches to resolving an IT problem?

A
  • Repair
  • Replace
  • Workaround

Each approach has its own considerations based on cost and feasibility.

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

When implementing a solution, what should you do after each change?

A

Test after each change

This ensures that the change resolves the issue without introducing new problems.

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

What is the significance of documenting findings, actions, and outcomes?

A

It provides a record for future troubleshooting and demonstrates support department activities

Documentation is crucial for maintaining a knowledge base.

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

What is a ‘known good’ duplicate?

A

A working copy of a cable or device used for testing by substitution

This technique helps in identifying faulty components.

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

What should be included in vendor instructions during troubleshooting?

A

Clear understanding of the steps required

Especially important if disassembly or complex reconfiguration is needed.

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

How can environmental changes affect troubleshooting?

A

They might introduce new problems or complicate existing ones

Awareness of these changes is essential for accurate diagnosis.

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

True or False: The most effective solution is always to fix the original cause of a problem.

A

False

Sometimes addressing the consequences is more practical from a business perspective.

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

Fill in the blank: Troubleshooting begins with a process of _______.

A

[problem-solving]

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

What should you do if you cannot solve a problem yourself?

A

Escalate it

This prevents wasting time and allows for faster resolution.

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

What is the role of preventive measures in troubleshooting?

A

To eliminate factors that could cause the problem to reoccur

This helps in maintaining system stability.

17
Q

What type of information should be consulted during troubleshooting?

A
  • System documentation
  • Installation logs
  • Event logs
  • Diagnostic tools

These sources provide valuable insights into the problem.

18
Q

What should be your next troubleshooting step after identifying the probable cause of a reported problem?

A

Verify the cause and develop a plan to resolve the issue

This step ensures that the identified cause is indeed correct before taking action.

19
Q

Before opening the system case to troubleshoot a computer, what should you check?

A

Ensure the computer is powered off and unplugged

This is critical for safety to prevent electrical shock or damage to components.

20
Q

What should you do if you cannot determine the cause of a problem?

A

Escalate the issue to a higher level of support or consult additional resources

This ensures that the problem is addressed effectively by someone with more expertise.

21
Q

What is your next troubleshooting step after discovering a solution that involves installing a software patch?

A

Test the patch in a controlled environment before widespread deployment

This helps to mitigate potential issues that could arise from the patch.

22
Q

After applying a troubleshooting repair, replacement, or upgrade, what should you do next?

A

Document the changes made and monitor the system for any issues

Documentation is essential for future reference and helps in tracking the effectiveness of the solution.