On shared AP hardware for a city network, how should employee, guest, and IoT SSIDs be designed?
Select an answer to reveal the explanation.
Short Explanation
Staff, guests, and IoT shouldn’t share one big open living room—and you also shouldn’t invent an SSID per laptop. Segment sensibly, lock down security per role, and keep the SSID count lean so Beacons don’t eat the air. Open employee SSIDs are not an onboarding strategy.
Full Explanation
Multi-SSID design balances isolation (employee vs guest vs IoT security/VLAN needs) against beacon/probe overhead from too many SSIDs on shared radios. Appropriate segmentation with restrained SSID count is the usual CWDP/CWNE guidance. Open corporate SSIDs or per-device SSIDs are inefficient or insecure.