A civic center lobby SSID will serve the general public. Which public-use practice should the technician follow?
Select an answer to reveal the explanation.
Short Explanation
Public lobby Wi-Fi is not a place to tattoo the staff passphrase on the wall. Use public-oriented controls—portal, OWE, segmentation—not the office PSK for everyone who walks in.
Full Explanation
A civic-center lobby SSID for the general public should avoid sharing the staff PSK on the open lobby air; prefer portal, OWE, and/or segmentation suited to public access. Public-use practice separates casual visitors from staff credential material and staff network paths. Technicians implement public-oriented controls rather than treating the lobby like an extension of the departmental office SSID.
Printing the staff WPA2-Enterprise passphrase on a wall placard fails because Enterprise staff secrets must not become lobby signage, and Enterprise profiles are not walk-up guest tools. Putting every visitor on the staff SSID with the sticky departmental PSK fails by concept: it collapses public and staff trust domains. Disabling encryption and authentication so the lobby matches an insecure 2005 open lab SSID fails modern public-use expectations and exposes traffic to eavesdropping.
Exam caveat: public lobby ≠ staff SOHO. CWTS public-use items punish reuse of staff PSKs and celebrate portal/OWE/segmentation patterns.
Operational check: configure lobby SSID with portal and/or OWE per design; keep staff PSK/Enterprise off placards and off the lobby profile; verify guest VLAN isolation from staff; spot-check that a visitor cannot authenticate with staff credentials by design.