A city hall lobby runs a Linux-based self-service kiosk that must join the staff WLAN with a saved network profile. While planning client support, how should the municipal technician treat Linux?
Select an answer to reveal the explanation.
Short Explanation
Think of Linux on that lobby kiosk like another radio in the fleet—same WLAN job, different dashboard. The technician still builds a network profile and security settings; Linux is on the supported OS list, not a weird exception. Treat it as a normal client OS family when the city asks what you can configure.
Full Explanation
CWTS client objectives include Linux among the operating system families technicians must be ready to support for WLAN configuration awareness. A municipal Linux kiosk still needs an appropriate wireless profile and security settings to join the intended SSID. Excluding Linux or forcing unrelated virtualization steps confuses platform support with optional architecture choices. At technician depth, recognize Linux as a supported client OS and configure it accordingly.