Integrated Technician Scenarios

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

triage: Triage is the rapid first-pass process of determining severity, scope, impact, and the best next action. Example: A technician decides whether one failed PC or an entire classroom network is affected. Do not confuse it with: Do not confuse triage with full root-cause analysis.
scope: Scope describes which users, devices, services, locations, or time periods are affected by a problem. Example: Testing shows only wireless clients are affected while wired clients work. Do not confuse it with: Do not confuse scope with severity; a small issue can still be severe for one critical system.
hypothesis: A hypothesis is a specific testable explanation for observed evidence. Example: The technician predicts that DHCP failure explains an APIPA address and missing gateway. Do not confuse it with: Do not confuse a hypothesis with a conclusion; it still needs testing.
evidence: Evidence is an observed, measured, or documented fact used to support or reject a troubleshooting theory. Example: A valid link light, IP address, event log entry, or failed ping can all be evidence. Do not confuse it with: Do not confuse evidence with assumptions.
root cause: Root cause is the underlying condition that produced the observed problem. Example: A loose uplink cable is identified as the reason several downstream devices lost connectivity. Do not confuse it with: Do not confuse root cause with the most visible symptom.
known-good: A known-good item or state has already been verified as working and is used for comparison. Example: A working patch cable is substituted to isolate a suspected cable fault. Do not confuse it with: Do not confuse known-good with unused or newly purchased.
rollback: Rollback returns a system to a previously known state after a change causes trouble or fails verification. Example: A technician restores the previous configuration after a new setting breaks connectivity. Do not confuse it with: Do not confuse rollback with an arbitrary reset to defaults.
verification: Verification confirms that the intended service works after the corrective action and that the success criteria are met. Example: After repairing DHCP, the client receives an address, gateway, DNS settings, and passes connectivity tests. Do not confuse it with: Do not confuse verification with stopping after the first positive result.
escalation: Escalation is a controlled handoff when the issue exceeds current authority, expertise, tools, or support boundary. Example: A network-core configuration issue is transferred with logs and test results to the network administrator. Do not confuse it with: Do not confuse escalation with abandoning the ticket.
service record: A service record documents the complaint, evidence, actions, changes, outcome, and follow-up. Example: The completed ticket records what failed, what was tested, what changed, and how the fix was verified. Do not confuse it with: Do not confuse a service record with a short note that omits evidence.

Take Week 17 vocabulary quiz →