
Module 5 Checkpoint and Lab: The Five-Minute Sweep
Where you are: Module 5 — Quick-Win Checks · Checkpoint · Based on Chapter 5 of Dr. Tahseen Al Doori's Troubleshooting Essentials.
Recap
Five quick-win checks resolve a large share of everyday faults in minutes, at no cost. Run them first, in order, every time, even when you are sure they are not the cause:
Power and connections are checked from the outside only. Save work before any restart, and power-cycle network equipment in order: modem, wait 60 seconds, router, end device. A restart clears temporary memory, ends stuck processes, reloads drivers and configuration and re-establishes network connections, but it treats the symptom, not the cause. If a quick win has to be repeated, it is a workaround, not a fix, and the root cause must still be found.
Knowledge check
Which list shows the five quick-win checks in the book's order?
Why does the book specify a full restart rather than sleep or hibernation?
A colleague says a meeting-room projector is broken: it is powered on but shows a 'No input' message. The laptop cable is firmly connected. Which check should come next?
Staff cannot sign in to a secure website from one laptop only, and its clock is several days wrong. What is the most likely explanation?
An office printer jams less after it is switched off and on, but the jams come back every day. What is the best description of the power cycle, and what next?
Lab: The Five-Minute Sweep (simulated)
The book has no laboratory exercise for Chapter 5, so this lab is designed for the course. It practises running the five checks in order, quickly and safely.
Goal: locate one planted, harmless fault per round by running the quick-win checks in order, aiming to find each one within five minutes. (The book's time table allows roughly 12 to 15 minutes for the complete sweep; planted faults sit within the checks, so a disciplined sweep finds them sooner.)
Safe setup
- Work in pairs, on a training computer, a virtual machine or a device you own. Never use someone else's work device or shared network equipment.
- The planter introduces one harmless, fully reversible fault while the troubleshooter looks away. Allowed faults: switch off the monitor or a power strip that powers only the training device; half-unplug a monitor, mouse or keyboard cable; turn on airplane mode or switch off Wi-Fi; mute the sound or select the wrong output device; select the wrong default printer; set the system clock to the wrong date; set screen brightness to minimum.
- Not allowed: opening any equipment, deleting files, uninstalling software or updates, changing passwords or accounts, editing system settings you cannot restore, or touching mains wiring.
- Without a second person, use paper scenario cards: the planter writes a fault on a card, and the troubleshooter "asks" the planter for the result of each check.
Steps
- The planter records the planted fault secretly and starts a timer when the troubleshooter begins.
- The troubleshooter writes a one-line problem statement from what the "user" (the planter) reports.
- The troubleshooter runs Check 1 (power) and records what was checked and the result.
- Continue in order with Check 2 (connections), Check 3 (restart, saving any work first), Check 4 (settings and input) and Check 5 (updates, storage and resources), stopping as soon as the fault is found.
- Correct the fault, then verify: repeat the action that originally failed.
- Stop the timer and compare the result with the planter's secret record.
- Swap roles and repeat for at least four rounds, using a different fault each time.
What to record (a simple table per round): the problem statement; each check performed, in order, with its result; the check that found the fault; time taken; how you verified the fix; and whether you were tempted to skip a check, and why.
Completion criteria: at least four rounds completed; every round shows the checks attempted in the correct order with no check skipped; each fault verified as fixed; and a two-sentence reflection on which planted fault was hardest to find and what that teaches about "assuming it can't be that".
Answers explained
- B. Power, connections, restart, settings and input, updates and resources: the physical, quick checks come first. The other options change the order.
- A. Sleep and hibernation are designed to preserve the current state, which is the state a restart needs to clear. Electricity use, updates and temporary files are not the book's reason.
- C. Power is on and the cable is seated, so the next check is settings and input: the projector's selected source. Storage and network equipment are irrelevant, and opening equipment is never a quick win.
- B. The book notes that incorrect clocks break secure websites; a certificate is valid only between two dates, so a badly wrong clock makes it appear invalid. The other options do not explain a one-laptop, clock-related failure.
- C. A quick win that has to be repeated is a workaround. Record it and continue to find the root cause (for example worn rollers or the wrong paper, as Chapter 11 suggests). Closing the ticket or replacing the printer skips the investigation.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 5 (§5.1–5.6, Key Takeaway, Summary and Review Questions), with cross-references to §11.1
