Week 01 vocabulary deck
Technician Foundations
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
- ESD
- Electrostatic discharge is a sudden transfer of static electricity that can damage electronic components. Example: A technician uses an antistatic strap before handling RAM or a motherboard. Do not confuse it with: Do not confuse ESD with a normal electrical short; ESD can damage sensitive parts without obvious sparks.
- POST
- Power-on self-test is the firmware check that runs before the operating system loads. Example: A desktop powers on but stops with a memory error before Windows starts. Do not confuse it with: Do not confuse POST with the operating-system boot process; POST happens first.
- UEFI
- Unified Extensible Firmware Interface is modern system firmware that initializes hardware and starts the boot process. Example: A technician opens UEFI settings to verify boot order and Secure Boot. Do not confuse it with: Do not confuse UEFI with Windows settings; it runs before the operating system.
- service ticket
- A service ticket is the documented record of a user problem, evidence, actions, and outcome. Example: A help-desk request records that a classroom PC has no display and lists the tests performed. Do not confuse it with: Do not confuse a ticket with a guess; it should preserve evidence and work history.
- baseline
- A baseline is a known starting condition used to compare current system behavior. Example: A technician records the normal IP address, gateway, and device status before changing anything. Do not confuse it with: Do not confuse a baseline with a final fix; it is the reference point.
- known-good
- A known-good item is a verified working component, cable, setting, or path used for comparison. Example: A suspected HDMI cable is replaced temporarily with one that is already proven to work. Do not confuse it with: Do not confuse known-good with merely new; new hardware can still be faulty.
- theory
- A troubleshooting theory is a specific, testable explanation for a symptom. Example: The technician proposes that a loose power connector explains why the system will not start. Do not confuse it with: Do not confuse a theory with random trial and error; it must be testable.
- verification
- Verification is the step that proves the fix restored the required function without creating a new problem. Example: After replacing a cable, the technician retests video output and confirms normal operation. Do not confuse it with: Do not confuse verification with seeing one promising sign; the expected service must be tested.
- documentation
- Documentation is the written record of system state, actions, results, and decisions. Example: The technician records the failed test, replacement part, and successful retest in the ticket. Do not confuse it with: Do not confuse documentation with memory; another technician should be able to follow it.
- escalation
- Escalation is transferring a problem to a higher support level when it exceeds authority, scope, or available tools. Example: A student device issue is escalated when the fix requires an administrator-only policy change. Do not confuse it with: Do not confuse escalation with giving up; it is a controlled handoff with evidence.