Week 18: Technician Service Challenge

Chapter question

Can you take one realistic client environment from intake to verified working state and explain every important decision you made along the way?

Client

You are supporting the fictional Harborview Community Learning Lab.

The lab needs a six-seat technology room for schoolwork, job applications, video meetings, basic media creation, printing/scanning, and staff administration.

The supplied environment includes:

• six desktop workstations;
• one staff laptop;
• one managed mobile device;
• one multifunction printer/scanner;
• one SOHO router/firewall and wireless access point;
• cloud productivity/email/storage service;
• one local practice VM;
• fictional users, tickets, diagrams, screenshots, logs, and configuration state.

Nothing in the capstone requires real credentials, real student records, live malware, external targets, or unrestricted administration.

Client requirements

Your final environment must support:

• normal office and school productivity;
• browser services and video meetings;
• shared printing and scanning;
• wired desktop networking and approved Wi-Fi;
• standard-user daily accounts with an approved admin-support path;
• MFA for staff/cloud accounts;
• endpoint protection and firewall controls;
• appropriate disk/data protection;
• backup and recovery planning;
• safe support procedures;
• documented changes;
• privacy-safe service records.

Five-lesson path

1. Intake, Inventory, and Baseline
2. Configure the Service Environment
3. Diagnose the Seeded Faults
4. Security, Recovery, and Verification
5. Service Record and Technical Briefing

Technician workflow

Use the Week 17 evidence chain throughout the capstone:

client requirement → baseline → service/configuration decision → incident evidence → controlled correction → rollback/recovery → security/privacy review → functional verification → service record → technical briefing

Weekly artifact

Your actual capstone artifact is the Technician Service Challenge service packet, not a slide deck.

Presentation software may help with the final briefing, but it is optional.

Required service packet

• client intake and asset inventory;
• requirement/constraint matrix;
• network/service dependency map;
• configuration/service plan;
• at least three incident records;
• backup/recovery verification;
• security/privacy review;
• final functional verification checklist;
• unresolved-risk/escalation log;
• technician service record;
• technical briefing/defense.

Seeded incidents

Your assigned fault set may include hardware, storage, networking, printer, Windows/application, mobile, security, virtualization, change-management, or backup/recovery problems.

You will not receive objective labels.

Every fault is solvable from supplied evidence.

Approximate time

Five 42-minute periods, 210 instructional minutes.

Final defense standard

You must be able to explain:

1. what the client needed;
2. what the baseline showed;
3. what you configured or recommended;
4. which faults you diagnosed;
5. which evidence mattered most;
6. which alternatives you rejected;
7. how you protected safety, privacy, and authorization;
8. what rollback/recovery path existed;
9. how you verified the final state; and
10. what still needs follow-up or escalation.

Course completion

This capstone is the final proof that you can move from component knowledge to technician performance.

The goal is not to memorize every A+ term. The goal is to support a system responsibly, prove what you changed, and explain why the result works.