Maintenance, Troubleshooting, and Basic Fault Resolution
This domain tests tiered fault resolution: what an operator should check, what must be logged, and when to escalate. Expect questions on power, scanning, connectivity, thermal behavior, cleaning, battery care, and reset boundaries.
Core rules and concepts
- Use a fixed sequence: observe the symptom and note any error code, check power and battery seating, check connections and port covers, restart the app, restart the device, check logs, then escalate with evidence.
- Capture the error code, time, device ID, app version, and steps that reproduced the fault before any reset.
- Battery care: avoid deep discharge, avoid charging at extreme temperatures, and use approved chargers. A swollen battery is removed from service and reported, not pressed back into use.
- Clean with approved wipes and water only where the IP rating allows; never use solvents on the scan window or screen. Keep port covers closed in dusty or wet conditions.
- A factory reset is a last resort and requires a confirmed backup or sync. It erases user flash, profiles, and certificates.
Worked example
A device powers on but will not scan. The technician confirms the app is in a scan field, checks that the correct symbology is enabled, cleans the scan window, and restarts the scan service. Reasoning: the fault is localized to the scan path before any network or account theory. If the scan engine still fails after a restart, the technician logs the error code and escalates rather than resetting the device and losing the queue.
Traps that cost marks
- Factory resetting before confirming backup or sync.
- Cleaning the scan window with solvent.
- Ignoring thermal throttling and diagnosing a "slow app."
- Continuing to use a swollen battery.
- Escalating without the error code and reproduction steps.