What should you record when a system failure occurs?
Record the symptom, when it began, affected users or devices, recent changes, exact error text or code, and tests already performed.
Study Safe Troubleshooting Practices with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.
What should you record when a system failure occurs?
Record the symptom, when it began, affected users or devices, recent changes, exact error text or code, and tests already performed.
Why change only one variable at a time?
Change one variable at a time and retest after each change. This helps identify which change affected the problem.
What kind of action should you prefer before a reset?
Prefer reversible actions, such as reconnecting, restarting, or restoring a known setting, before resets or repairs that remove configuration.
When should you verify whether a repair worked?
Retest after each change, then verify that the repair resolves the original issue.
What should you do before changing policy-controlled settings on a managed device?
If a device is organization-managed, stop before changing policy-controlled settings and contact the administrator.
Which timing detail should you document for a failure?
Record when the symptom began. Its timing can be considered alongside recent changes and other evidence.
What should you record to establish a failure's scope?
Record which users or devices are affected to help establish the failure's scope.
What recent history should you capture during troubleshooting?
Record recent changes, since they may be relevant when diagnosing the failure.
How should you document an error message?
Capture the exact error text or code rather than relying on a vague paraphrase.
Why record tests already performed?
Record the tests already performed so troubleshooting can account for what has been tried.
Name a reversible action to try before a configuration-removing reset.
Reconnect, restart, or restore a known setting before considering a reset or repair that removes configuration.
What should guide the size and risk of a repair?
Avoid broad resets or privilege changes without evidence; make the smallest safe change supported by what you know.
Focused study of installation failures, crashes and application compatibility.
Focused study of recognition, isolation and remediation workflow concepts.
Focused study of mobile OS, application, connectivity and synchronization problems.