350-901 · Question #74
A client device fails to see the enterprise SSID, but other devices are connected to it. What is the cause of this issue?
The correct answer is A. The hidden SSID was not manually configured on the client. When a client cannot see an SSID that other devices can connect to, the SSID is configured as hidden and the client has not been manually configured with the network name.
Question
Exhibit
Options
- AThe hidden SSID was not manually configured on the client.
- BThe broadcast SSID was not manually configured on the client.
- CThe client has incorrect credentials stored for the configured hidden SSID.
- DThe client has incorrect credentials stored for the configured broadcast SSID.
How the community answered
(38 responses)- A95% (36)
- B3% (1)
- D3% (1)
Why each option
When a client cannot see an SSID that other devices can connect to, the SSID is configured as hidden and the client has not been manually configured with the network name.
A hidden SSID does not broadcast its network name in beacon frames, so it is invisible to passive scanning clients; the client must be manually configured with the exact SSID name and security settings to discover and connect to the network, which has not been done in this scenario.
A broadcast SSID advertises itself in beacons and would be visible to all clients automatically without manual configuration, so failure to manually configure it is not a valid cause for the client not seeing it.
Incorrect credentials would still allow the client to see and attempt to join the SSID; the issue here is that the SSID is not visible at all, not that authentication is failing.
Incorrect credentials for a broadcast SSID would result in authentication failure after the SSID is discovered, not in the SSID being invisible to the client.
Concept tested: Hidden SSID manual client configuration requirement
Source: https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/68015-broadcast-ssid.html
Topics
Community Discussion
No community discussion yet for this question.