
Module 14 Checkpoint: Evaluate the Decisions
Where you are: Module 14 — Case Studies and Final Assessment · Checkpoint · Based on Chapter 14 of Dr. Tahseen Al Doori's Troubleshooting Essentials.
Recap
The same seven steps solved four very different problems. In the office without internet, asking whether all devices were affected and following the path (valid address, router reachable, 8.8.8.8 not) placed the fault outside the building; a power-cycle came first, then escalation to the provider. In the slow laptop, Task Manager revealed a cloud-sync tool filling a 97% full disk. In the intermittent Wi-Fi, an occurrence log tied midday drops to a 2.4 GHz microwave. In the late deliveries, splitting the data by courier and product isolated two routes, and a scoped rollback fixed them. The method transfers because it is logic, not technology.
Knowledge check
The first four questions are the book's Chapter 14 review questions turned into practice items; the fifth asks you to evaluate a decision.
Review question 1. In Case Study 1, which single test proved the fault was outside the office network?
Review question 2. Which approach isolated the cause in Case Study 3?
Review question 3. Which further preventive measure best fits Case Study 2?
In Case Study 4, the business moved two routes back to the previous courier. Which technique and principle does this show?
Evaluate the decision. In Case Study 3 the access point was switched to prefer 5 GHz and moved in the same visit. What is the fairest assessment?
Answers explained
- b — Reaching the router but not the internet by IP places the break beyond the router; file sharing only cleared the local network, the power-cycle was a fix attempt, and the power cut was the change, not a test.
- a — Other rooms were unaffected (comparison), and the occurrence log exposed the pattern; there was no cable split, substitution or strip-down in the case.
- d — Monitoring and alerts (Chapter 12) catch a filling disk early; daily restarts are a workaround, a second sync tool adds load, and deleting the shared folder destroys data.
- c — The change that preceded the fault was reversed for the affected routes only; nothing was substituted wholesale or stripped down.
- a — Two changes at once lose the knowledge of which one worked, but both addressed the confirmed cause and two weeks of verification followed; absolutes in b, c and d are wrong.
Exercise: evaluate the decisions
For each case, complete one row of this table in your notes. The first row is started for you.
| Case | One decision that was strong, and why | One thing you would do differently, and why | Isolation technique(s) used |
|---|---|---|---|
| 1 Office without internet | Asked whether all devices were affected: it halved the problem at once | ... | Scoping; follow the path (connectivity sequence) |
| 2 Slow laptop | ... | ... | ... |
| 3 Intermittent Wi-Fi | ... | ... | ... |
| 4 Late deliveries | ... | ... | ... |
Completion criteria: every cell filled; each "differently" suggestion names the chapter principle it applies (for example keep users informed, Chapter 13, or change one thing at a time, Chapter 2).
Lab: Write Your Own Case Study
This lab is the book's Chapter 14 review question 4: write your own case study, using the seven steps, for a problem you have solved.
Goal. Produce a one-page case study in the same shape as the book's, followed by a short evaluation.
Safe setup. Write about a problem you have already solved, technical or not. Do not recreate a fault on a device you depend on to get material. If you want to reproduce a technical fault, use a training machine or a virtual machine. Leave out names, passwords and any personal or confidential details: describe people by role.
Steps.
- Identify. Write the problem statement with the Chapter 4 template: when, who, what, where, how often, the most recent change and any exact error.
- Theory. List two to four probable causes, simplest first.
- Test. Describe each test and its result, including the theories you rejected. Name the isolation technique each test used.
- Plan and implement. State the change, how it could be undone, and whether anyone had to approve it or be escalated to (name the tier).
- Verify. State how you confirmed the fix, with a measurement where possible, and who confirmed it.
- Document and prevent. State what was recorded and one preventive measure from Chapter 12.
- Evaluate. In three to five sentences, say which decision was strongest, what you would do differently now, and why.
What to record. The seven-step case study (around 250–400 words) and the evaluation paragraph.
Completion criteria.
- All seven steps are present, in order, each with a concrete output.
- At least one rejected theory is recorded with its test.
- At least one isolation technique from Chapter 6 is named and correctly applied.
- The verification includes the user's (or stakeholder's) confirmation.
- A preventive measure is linked to the root cause.
- No personal data or passwords appear.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 14 Case Studies 1–4, chapter summary and review questions 1–4, §2.2, §4.6, §6, §12.4, §13
