Public works issues rugged IoT sensors and receipt printers onto the city Wi-Fi. How should those devices be treated as WLAN clients?
Select an answer to reveal the explanation.
Short Explanation
Printers and rugged sensors are still Wi-Fi citizens — just ones with tiny keypads and stubborn firmware. Treat them as specialty clients: get SSID and security right even when the UI is awful. No desktop OS required for a seat at the BSS.
Full Explanation
Specialty devices such as IoT sensors and wireless printers participate as 802.11 clients even when they lack a rich desktop OS or configuration GUI. They still require correct SSID, security mode, and often vendor-specific driver or profile handling. Naming conventions in the SSID string do not create association eligibility by themselves, and technician-level onboarding does not require CWNA predictive survey depth for each printer. Expect limited UI and plan configuration methods accordingly.