Troubleshooting and Support
Core concepts
Learn a structured method: identify the problem, establish a theory, test the theory, plan and implement a fix, verify full functionality, and document. Know how to gather symptoms through questioning, check logs (Event Viewer, syslog), and use tools like ping, ipconfig/ifconfig, tracert, nslookup, and resource monitors. Understand escalation paths, ticket documentation, and change control. Distinguish hardware, OS, application, and network faults by their symptoms.
Traps in questions
A frequent trap is skipping verification - the correct answer often includes confirming the fix and documenting it, not just applying a change. Another is jumping to a solution before reproducing the problem. Do not confuse symptom with cause: a slow PC may be malware, failing disk, or insufficient RAM. Questions may reward the least invasive step first (check cables, restart service) before reimaging. Also, always consider whether a change requires approval or a rollback plan.
Worked example / rule of thumb
A printer is offline for one user but works for others. Rule of thumb: isolate scope - one user vs many. If only one user is affected, check that user's queue, driver, and connection; if all users are affected, check the print server or network. Narrowing scope by affected population quickly identifies the fault domain.
Exam focus
Expect ordered troubleshooting steps, tool selection, scope isolation, and documentation or escalation requirements.