4.1. Domain 3.0 - Software Troubleshooting

A user calls: "My computer is broken." That's all you get. What do you do?

Think of troubleshooting like medical diagnosis. A doctor doesn't just prescribe random medications—they ask about symptoms, run tests, and narrow down the possibilities. Similarly, you need to isolate whether this is a system-wide failure (the OS itself), an application-specific issue (one program crashing), or an external factor (network connectivity, peripheral problem).

Without systematic troubleshooting, you waste hours swapping parts and reinstalling software. With it, you follow the evidence to the root cause. What happens when you skip the methodology? You might "fix" a symptom while leaving the actual problem in place—only to get called back when it fails again.

This domain covers 23% of the exam and tests your ability to apply the troubleshooting methodology from Phase 1 to real scenarios.