Timedora
Free Online Flashcard Deck

Troubleshooting Evidence and Safe Fixes Free Online Flashcards

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

12 cards
01
Front

What error details should you capture before troubleshooting?

Back

Record the exact error and when it occurred before changing the system.

02
Front

Which software and system details belong in a troubleshooting baseline?

Back

Record the application name and version, installer source, operating-system version, and device configuration.

03
Front

What change history and reproduction information should you capture?

Back

Record recent changes and the steps that reproduce the problem.

04
Front

What diagnostic evidence should be preserved before changing a system?

Back

Preserve relevant installer logs or crash-event details before making changes.

05
Front

What should you prepare before applying a troubleshooting fix?

Back

Assess the risk, back up affected data and configuration, and identify how to undo the change.

06
Front

Where can you test a proposed fix before applying it to production?

Back

Consider testing the fix on a nonproduction device first.

07
Front

What sequence guides a controlled change when an approved process is required?

Back

When required, use an approved change process; controlled changes are proposed, assessed, tested, approved, implemented, and verified.

08
Front

What makes an installation remedy preferable?

Back

Prefer a trusted vendor installer or update, or repair a damaged installation when appropriate.

09
Front

How should evidence guide a dependency or configuration fix?

Back

Correct the specific dependency or configuration identified by evidence.

10
Front

Why should you change only one thing at a time?

Back

Change one thing at a time so you can assess its effect and reverse it if needed.

11
Front

What can verbose logging help diagnose during an MSI installation?

Back

For an MSI installation, verbose logging can help reveal where setup failed.

12
Front

What command enables verbose logging for this MSI installation?

Back

Use `msiexec.exe /i "C:\example.msi" /L*V "C:\package.log"` to enable verbose logging for an MSI installation.