N10-005 · Question #315
A user calls the helpdesk to report not being able to access network resources over the company's Wi-Fi connection. During information gathering, the user mentions that the wireless network their…
The correct answer is A. SSID mismatch. An SSID mismatch occurs when the client connects to a different wireless network name than expected, explaining why the user sees a different network name.
Question
A user calls the helpdesk to report not being able to access network resources over the company's Wi-Fi connection. During information gathering, the user mentions that the wireless network their computer is signed into is not the same name as it had been previously. Which of the following is the underlying cause?
Options
- ASSID mismatch
- BIncorrect WPA key
- CSignal bounce
- DAntenna placement
How the community answered
(58 responses)- A86% (50)
- B3% (2)
- C2% (1)
- D9% (5)
Why each option
An SSID mismatch occurs when the client connects to a different wireless network name than expected, explaining why the user sees a different network name.
The SSID (Service Set Identifier) is the name that identifies a wireless network. When the user reports the connected network name differs from the previous one, the device has associated with a different SSID - either a misconfigured AP, a neighboring network, or a rogue access point. This is the definition of an SSID mismatch and directly explains the symptom described.
An incorrect WPA key would prevent the user from connecting to the network at all, not cause them to connect to a differently named network.
Signal bounce (multipath interference) degrades signal quality but does not cause a device to connect to a differently named network.
Antenna placement affects signal coverage and strength but does not cause a client to associate with a different SSID.
Concept tested: Wireless SSID mismatch identification
Source: https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/68908-wlan-troubleshoot.html
Topics
Community Discussion
No community discussion yet for this question.