Timedora
Free Online Flashcard Deck

Operating-System Troubleshooting Basics Free Online Flashcards

Study Operating-System Troubleshooting Basics with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.

12 cards
01
Front

What should you document when defining an operating-system failure?

Back

Describe what fails, when it began, how often it occurs, and what the user was doing before changing anything.

02
Front

How should you reproduce a failure before attempting a repair?

Back

When practical, repeat the same steps that caused the failure so you can compare results before and after a repair.

03
Front

Why reproduce a failure using the same steps?

Back

A repeatable failure is easier to compare before and after a repair.

04
Front

What does scoping an operating-system failure involve?

Back

Determine whether it affects one application, the whole system, multiple users, or startup.

05
Front

What should you protect before a repair could overwrite evidence?

Back

Preserve important data and capture relevant logs before repairs that might overwrite evidence.

06
Front

Which recent changes should you note when defining a failure?

Back

Record recent updates, driver installations, configuration edits, or new hardware.

07
Front

What does a failure limited to one application suggest about its scope?

Back

A failure limited to one application suggests a different troubleshooting path from one affecting the whole system.

08
Front

How does a system-wide failure differ in scope from an application-only failure?

Back

A system-wide failure affects the whole system, rather than being limited to one application.

09
Front

What is the basic sequence for operating-system troubleshooting?

Back

Collect evidence, test a likely explanation, make a controlled change, then check whether the failure is resolved.

10
Front

Which circumstances help define an observable failure?

Back

Record what fails, when it began, how often it happens, and what the user was doing.

11
Front

What should you check about the number of affected users?

Back

Check whether the failure affects multiple users; this is one way to assess its scope.

12
Front

When should you preserve important data and capture relevant logs?

Back

Preserve important data and capture relevant logs before a repair that could overwrite evidence.