Timedora
Free Online Flashcard Deck

Safe Troubleshooting Practices Free Online Flashcards

Study Safe Troubleshooting Practices with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.

12 cards
01
Front

What should you record when a system failure occurs?

Back

Record the symptom, when it began, affected users or devices, recent changes, exact error text or code, and tests already performed.

02
Front

Why change only one variable at a time?

Back

Change one variable at a time and retest after each change. This helps identify which change affected the problem.

03
Front

What kind of action should you prefer before a reset?

Back

Prefer reversible actions, such as reconnecting, restarting, or restoring a known setting, before resets or repairs that remove configuration.

04
Front

When should you verify whether a repair worked?

Back

Retest after each change, then verify that the repair resolves the original issue.

05
Front

What should you do before changing policy-controlled settings on a managed device?

Back

If a device is organization-managed, stop before changing policy-controlled settings and contact the administrator.

06
Front

Which timing detail should you document for a failure?

Back

Record when the symptom began. Its timing can be considered alongside recent changes and other evidence.

07
Front

What should you record to establish a failure's scope?

Back

Record which users or devices are affected to help establish the failure's scope.

08
Front

What recent history should you capture during troubleshooting?

Back

Record recent changes, since they may be relevant when diagnosing the failure.

09
Front

How should you document an error message?

Back

Capture the exact error text or code rather than relying on a vague paraphrase.

10
Front

Why record tests already performed?

Back

Record the tests already performed so troubleshooting can account for what has been tried.

11
Front

Name a reversible action to try before a configuration-removing reset.

Back

Reconnect, restart, or restore a known setting before considering a reset or repair that removes configuration.

12
Front

What should guide the size and risk of a repair?

Back

Avoid broad resets or privilege changes without evidence; make the smallest safe change supported by what you know.