Device Setup, Configuration, and Initialization
This domain tests the ordered steps that turn a new or reset device into a trusted production tool: provisioning, identity, connectivity, time, application profile, scanner settings, and a recorded baseline. Questions often ask what must happen before enrollment or before the first live transaction.
Core rules and concepts
- Provision in stages: inspect and charge, record asset ID, install approved firmware, enroll in management, apply the role profile, join the network, set time, configure the app, run a test transaction, record the baseline.
- Least privilege: the operator account gets only the menus and data the job requires; admin credentials are not stored on the device.
- Time zone and NTP must be set before certificate-based Wi-Fi or app sign-in, because TLS validity checks depend on the clock.
- Scanner configuration is deliberate: enable only the symbologies in use, set the correct prefix/suffix, and test check-digit behavior. Enabling every symbology raises misread risk.
- Record a baseline: OS build, firmware, app version, profile version, serial number, date, and technician. Changes after baseline need a change log.
Worked example
A new rugged tablet shows a clock three hours behind. The technician is tempted to enroll and configure the app first. Correct order: join NTP, confirm the clock, then enroll and apply the profile. Reasoning: a wrong clock can make a valid certificate appear "not yet valid," causing enrollment or sign-in failures that look like network faults. After enrollment, enable only Code 128 and QR, run a scan into a staging record, confirm it arrives, then record the baseline.
Traps that cost marks
- Treating enrollment as the first step and skipping asset identity.
- Configuring Wi-Fi before time sync and misdiagnosing a certificate error.
- Using one shared admin login for all shifts.
- Leaving all barcode symbologies enabled "just in case."
- Failing to record the baseline, so later drift cannot be proved.