Skip to content
عربيSign in

Get the app

Study guide · 1.2

Identify, troubleshoot, and resolve technical problems with assistance

Troubleshooting is a structured way to find and fix a technical problem instead of guessing. Knowing the basic steps and how to collect system information lets you solve simple problems yourself and give a support team exactly what it needs for harder ones.

A study feature written by ExamDragon, not part of the real exam. Each heading is one of Certiport's skills for this objective.

1.2.1Identify basic troubleshooting steps

  • Identify the problem: what exactly happens, when it started, what changed and whether it can be repeated.
  • Check the simple causes first: power, cables, Wi-Fi, volume, a full disk, or a signed-out account.
  • Restart the program, then the device; many temporary faults clear after a restart.
  • Change one thing at a time and test after each change, so you know which step fixed it.
  • Search the exact error message on the vendor's support site, and apply pending updates.
  • Write down what you tried and the result, and escalate to IT support when the problem is beyond your access or skill.

Example: A printer stops working for one user only; checking that other users can print shows the printer is fine, and reinstalling that user's printer driver solves it.

1.2.2Obtain system information to support troubleshooting

  • Useful details include the device model, operating system and version, installed memory, free storage and the version of the program that fails.
  • Record the exact wording or code of any error message; a screenshot is often best.
  • Operating systems show this in places such as Settings, About, or a System Information tool; network details such as the IP address come from network settings or a command like ipconfig or ifconfig.
  • Event logs and crash reports record what happened just before a failure.
  • Never send passwords to support; share only the information requested, through the official channel.

Example: Before calling the help desk, a user opens the About page, notes the operating system version and build, and takes a screenshot of the error code shown when the app closes.

Key terms

Troubleshooting
A step-by-step process of finding the cause of a problem and fixing it.
Reproduce
To make a problem happen again on purpose so it can be observed and tested.
Escalate
To pass a problem to someone with more access, authority or expertise.
Event log
A record kept by the operating system or an application of errors, warnings and other events.
Driver
Software that lets the operating system communicate with a piece of hardware.

Easy to confuse

  • Changing several settings at once makes it impossible to know which change helped or caused a new problem.
  • Describing a problem as 'it does not work' without details, messages or steps slows down support.
  • Skipping the obvious checks, such as power or connection, wastes time on complex fixes.

After this guide: You can follow a logical troubleshooting sequence and gather the system information support needs.