Lesson-10-Troubleshooting-Methodology

Lesson 10: Troubleshooting & IT Problem Solving

Troubleshooting is the skill of turning “random guessing” into a repeatable process. You’ll learn the CompTIA 6-step method and practice it like a real IT support tech.

Goal: Fix issues systematically Core tool: 6-step method Pro move: document everything Practical: Ticket triage

1) What “Troubleshooting” Really Means

Troubleshooting is a structured process for finding the root cause of a problem and fixing it with the least risk. Good troubleshooting is repeatable: someone else can follow your steps and get the same result.

Common beginner trap: “Try random fixes until it works.” That wastes time and can create new problems.

Core mindset

  • Start simple: power, cables, Wi-Fi, credentials, and scope.
  • Change one thing at a time: otherwise you don’t know what fixed it.
  • Verify: confirm the result before you move on.
  • Document: your notes become the next person’s shortcut.

2) The CompTIA Six-Step Troubleshooting Process

Step Description
Step 1 Identify the problem. Gather symptoms, ask questions, check logs, and confirm scope.
Step 2 Establish a theory. Start with the obvious and most likely causes.
Step 3 Test the theory. Prove/disprove it with a safe test.
Step 4 Plan + implement. Choose the lowest-risk fix first.
Step 5 Verify full functionality and add preventive measures if needed.
Step 6 Document. Symptoms, tests, changes, and outcomes.

Exam tip: “What should you do FIRST?” is often Step 1: gather info and confirm the problem before changing settings.

3) A Simple Troubleshooting Ladder

When you’re not sure where to start, climb from the bottom up:

  • Physical: power, cables, ports, Wi-Fi toggle, airplane mode
  • Device: disk space, CPU/RAM, drivers, permissions
  • Network: Wi-Fi, IP, DNS, router/firewall rules
  • Application: cache, extensions, updates, corrupted profile
  • Account: password, MFA, lockouts, access rights
  • Service/Server: outages, maintenance, backend failures

4) Preventive, Detective, Corrective (Quick Review)

  • Preventive: stops problems (MFA, patching, firewall rules)
  • Detective: detects/alerts (logs, monitoring, IDS)
  • Corrective: fixes damage (restore backup, reimage, replace part)
Real IT: You often detect first (alerts/logs), then correct, then add a preventive change so it doesn’t happen again.

Practical: Ticket Triage Simulator

For each ticket, choose the best category and the best FIRST action. Tickets are hardcoded so they always display.

Progress 0/8
Score 0%
Rule: “First action” should be the safest, fastest check that confirms/denies the likely cause (verify scope, check network basics, try known-good cable, test another browser, verify credentials).

1. “Website says: This site can’t be reached.”

One user can’t reach a website, but coworkers can. They’re on Wi-Fi.

Severity: Medium · ID: T1

Best category

Best FIRST action

Hint: If others can reach it, scope points to the user’s device/network.

2. “Password is correct but login fails.”

User changed phones recently and MFA prompts stopped.

Severity: High · ID: T2

Best category

Best FIRST action

Hint: Correct password + new phone often means MFA enrollment needs fixing.

3. “Printer is offline.”

Shows Offline on one computer, but prints from another.

Severity: Low · ID: T3

Best category

Best FIRST action

Hint: If it prints elsewhere, focus on the affected PC (queue/spooler/printer selection).

4. “PC turns on, no display.”

Fans spin, lights on, but monitor shows “No Signal.”

Severity: High · ID: T4

Best category

Best FIRST action

Hint: Start with monitor input/cable/known-good before suspecting major parts.

5. “App crashes after update.”

A desktop app crashes immediately after updating yesterday.

Severity: Medium · ID: T5

Best category

Best FIRST action

Hint: Check errors/known issues, then roll back or repair safely.

6. “Multiple users: shared drive disappeared.”

Several users can’t access a shared network drive at the same time.

Severity: Critical · ID: T6

Best category

Best FIRST action

Hint: Many users at once usually points to service/server or network changes.

7. “Web page looks broken in Chrome.”

Layout is broken in Chrome but looks fine in Firefox.

Severity: Low · ID: T7

Best category

Best FIRST action

Hint: Different browsers = cache/extensions/settings first.

8. “Laptop is very slow.”

Boot takes 10 minutes and apps lag heavily.

Severity: Medium · ID: T8

Best category

Best FIRST action

Hint: Start with disk space + Task Manager (CPU/RAM/startup apps).

Lesson 10 Quiz (Advanced)

10 questions. Score ≥ 75% to unlock the Next Lesson button.

Progress note: Your score/unlock is saved to this browser only using localStorage. Clearing browser data, using Incognito, or switching devices will reset progress.
Quiz Progress 0/10

Next Lesson

Complete the quiz with a score of 75%+ to unlock.

🔒 Locked — Score 75%+ required
Next Lesson →
Tip: Review the 6-step table and the “First Checks” list, then try again.

Leave a Comment