
Module 1 Checkpoint and Lab: Classify the Fault
Where you are: Module 1 — Introduction to Troubleshooting · Checkpoint · Based on Chapter 1 of Dr. Tahseen Al Doori's Troubleshooting Essentials.
Recap
Troubleshooting is the systematic process of identifying, diagnosing and resolving problems in a system so that it returns to normal operation. It answers what is actually wrong?, so it comes before repair (correcting a known fault) and differs from maintenance (planned prevention). Trial and error wastes time, can create new faults, leaves no record and starts from nothing next time; a structured method replaces luck with logic and brings speed, safety, repeatability and knowledge. Problems usually fall into six categories (hardware, network, software, account and access, user and process, environmental), and the category suggests where to start. Downtime has real financial, operational and reputational costs, so faster, more reliable fixes matter.
Checkpoint quiz
A loose RAM module is found to be the reason a laptop will not boot. The module is then reseated. Which activity is the reseating?
Which list gives the four benefits of a structured method named in the book?
Staff report that an online ordering task keeps producing the wrong totals, but the software works correctly when the procedure is followed. Which category fits best?
Sam restarts, changes two network settings and reinstalls an app; the fault disappears. A week later a different connection fails. Which weakness of trial and error does this best illustrate?
A shop's till system is down for three hours. Which response describes the cost of downtime most completely?
Lab: Classify the Fault
Goal. Practise the core skills of Module 1 on realistic reports: separate troubleshooting from repair and maintenance, classify problems, choose a starting point and estimate downtime cost.
Safe setup. This is a paper or spreadsheet exercise. You do not need to touch, open or change any device. Work alone or in pairs. Allow 45–60 minutes.
The reports (fictional):
- "My laptop smells hot and turns itself off during video calls."
- "None of us can get online since this morning — the whole office."
- "It says my password has expired and won't let me in."
- "The accounts app closes as soon as I open last month's file."
- "Our new receptionist's bookings keep appearing on the wrong day."
- "The warehouse scanner only drops its connection when it rains."
- "The projector shows a blue screen saying No signal."
- "Access denied when I open the HR folder — I could open it last week."
- "The router was replaced yesterday; today printers can't be found."
- "The server room fan has been making a grinding noise for a week."
Steps.
- Copy the table below and add one row per report.
- For each report, choose the category and write a one-line reason based on the symptom.
- Write where you would start: the first group of causes you would check.
- Mark any report where a second category is plausible, and name it.
- For reports 1, 8 and 10, write one sentence each describing a troubleshooting action, a repair action and a maintenance action that could have prevented the problem.
- Choose one report and estimate the downtime cost for a small business, using illustrative figures and separating countable costs from hard-to-measure ones.
- Finally, write two sentences explaining which report you would deal with first and why, referring to scale and cost.
| # | Category | Reason | Start here | Second category? |
|---|---|---|---|---|
| 1 |
What to record. The completed table; the three troubleshooting–repair–maintenance triples; your cost estimate with working; your prioritisation note.
Completion criteria.
- All ten reports have a category with a reason drawn from the symptom, not a guess.
- At least three reports are identified as plausibly belonging to a second category.
- The three triples clearly separate investigation, correction and prevention.
- The cost estimate shows its working and labels its figures as illustrative.
- The prioritisation note mentions how many people are affected and the cost of delay.
Safety reminder. Several reports (overheating, grinding noises) involve hardware. In real life, these are observed and reported, not opened, unless you are trained and authorised. Never ask anyone for their password when handling account problems; use the approved reset process.
Answers explained
- b — Once the cause is known, correcting it is repair. Finding the loose module was troubleshooting; maintenance is planned prevention; documentation records the work.
- a — These are the book's four benefits. Luck and intuition are what a structured method replaces; maintenance, repair and backup are activities, not benefits.
- c — The technology works when the procedure is followed, so the fault lies in training or procedure. Nothing suggests hardware, network or environmental causes.
- d — Random changes can create new faults, and because nothing was recorded, nobody connects the new failure to the earlier changes. The other options are not weaknesses the book describes.
- b — The book lists lost sales, idle staff, missed deadlines and damaged reputation. A fee or parts price is only part of the cost, and fixing a fault later does not undo the cost of the downtime.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 1 (§1.1–1.4) and Chapter 1 review questions; safety guidance from §7.5, §8.6 and §10.4
