A city field tablet cannot load its WLAN adapter after a help-desk attempt to install an unsigned NIC driver. Group Policy blocks unsigned drivers, and the wireless interface never appears. What best explains the connectivity failure?
Select an answer to reveal the explanation.
Short Explanation
No driver, no radio—like a car with the engine computer unplugged. When policy refuses a badly signed driver, the adapter never shows up, so association never starts. Get an approved signed driver through the proper channel.
Full Explanation
Client connectivity requires a functioning WLAN driver. If operating-system policy blocks installation of an improperly signed driver, the NIC does not initialize and the device cannot scan or associate. The symptom is absence of the wireless interface rather than an authentication reject after beacons are heard. Resolving the issue means installing a policy-compliant signed driver, not changing SSID security or RF channel plans. This maps to Domain 5 driver-related connectivity troubleshooting.