Device Fundamentals and Information Handling Concepts
This domain tests how well you understand the physical and logical parts of a craftsman information device and how data moves from capture to archive. Expect questions on hardware blocks, boot behavior, storage types, and offline-first information handling.
Core rules and concepts
- A device has four layers: hardware (SoC, RAM, flash, battery, radios, sensors, scan engine), firmware/OS, the line-of-business app, and the synced back-end record.
- RAM is volatile working memory; flash is non-volatile storage. A warm reboot clears RAM but not flash; a factory reset clears user flash.
- Cold boot means power is fully removed and reapplied. Warm boot means an OS restart without power loss.
- Data lifecycle: capture, validate, persist locally, queue, sync, confirm, archive.
- Offline-first designs write to a local queue first, then sync. Each record needs a unique ID and a device timestamp.
- Clock drift breaks ordering, certificate validation, and audit trails, so time sync is part of fundamentals, not setup trivia.
Worked example
A technician scans a machined part in a basement with no signal. The app creates a record with a UUID, a monotonic device timestamp, the operator ID, and the scan payload, then writes it to local flash. On reconnect the queue uploads. Reasoning: local persistence prevents data loss; the UUID prevents duplicate collisions when two devices sync; the timestamp preserves order; the operator ID supports the audit trail. The scan is not "entered" until validation and sync confirmation.
Traps that cost marks
- Treating RAM as storage and assuming a reboot wipes records.
- Equating "synced" with "backed up."
- Ignoring clock drift when explaining sync conflicts.
- Assuming a successful scan is a valid record without field validation.