Technician Service Challenge

Say the definition before you flip. Use the example and distinction to repair fuzzy terms, then take the separate vocabulary quiz.

Vocabulary lab

Flip the idea, not just the card

Explain the term before you reveal the back. Then compare your explanation with the definition, example, and warning.

Read all terms without animation

intake: Intake is the structured collection of the client's reported problem, requirements, constraints, and initial evidence. Example: The technician records which Harborview services are failing before changing the environment. Do not confuse it with: Do not confuse intake with diagnosis; intake gathers the starting information.
inventory: Inventory is the verified list of systems, devices, services, and relevant identifiers in an environment. Example: The technician lists desktops, laptop, mobile device, printer, router, AP, cloud services, and VM. Do not confuse it with: Do not confuse inventory with a network diagram; inventory lists assets while a diagram shows relationships.
baseline: A baseline is the documented known starting state used to compare later observations and changes. Example: The technician records normal addresses, service states, and expected dependencies before fault injection. Do not confuse it with: Do not confuse a baseline with the final repaired state.
dependency map: A dependency map shows which components or services rely on others to function. Example: The print workflow shows client, DNS, network path, printer service, and device dependencies. Do not confuse it with: Do not confuse a dependency map with a simple device list.
configuration: Configuration is the set of settings that determine how a system or service behaves. Example: The technician records router, Wi-Fi, VM, printer, and security settings for the client environment. Do not confuse it with: Do not confuse configuration with hardware inventory.
seeded fault: A seeded fault is an intentionally introduced problem used for controlled troubleshooting practice. Example: The capstone includes a wrong gateway and a stopped service for students to diagnose. Do not confuse it with: Do not confuse a seeded fault with an uncontrolled real-world outage.
recovery point: A recovery point is a known state or saved copy that can be used to restore a system after a failed change or incident. Example: A VM snapshot or configuration backup is created before a risky modification. Do not confuse it with: Do not confuse a recovery point with successful verification after the change.
risk: Risk is the combination of likelihood and impact associated with a threat, failure, or change. Example: The technician ranks a single-user inconvenience lower than a change that could interrupt every client device. Do not confuse it with: Do not confuse risk with a confirmed incident; risk can exist before an event occurs.
service record: A service record is the final evidence trail of the issue, tests, actions, results, and client-facing outcome. Example: The capstone packet includes the original complaint, troubleshooting evidence, fixes, verification, and unresolved risks. Do not confuse it with: Do not confuse the service record with the technical briefing; one is the durable record and the other is the presentation.
technical briefing: A technical briefing is a concise explanation of system state, findings, decisions, evidence, risks, and next steps for an audience. Example: The student explains the Harborview environment, seeded faults, fixes, and remaining recommendations to a review panel. Do not confuse it with: Do not confuse a briefing with reading the entire service record aloud.

Take Week 18 vocabulary quiz →