A weekend civic festival needs temporary Wi-Fi with terms acceptance before access. The design document lists a captive portal SSID. What should the technician configure?
Select an answer to reveal the explanation.
Short Explanation
Temporary event Wi-Fi still follows the design: stand up the captive portal SSID. Painting WEP on the backdrop or minting Enterprise accounts for every festival-goer is not the documented path.
Full Explanation
When a weekend civic festival’s design document lists a captive portal SSID for temporary Wi-Fi with terms acceptance, the technician should configure that documented captive portal SSID so users hit terms or login before browsing. Temporary event WLAN still follows the written design: stand up the portal SSID rather than improvising insecure shortcuts under time pressure.
An open SSID with no portal because festivals never need terms pages fails both policy and the design document. WEP only, with the key painted on the stage backdrop, fails as broken crypto plus public key disclosure. Staff WPA2-Enterprise with RADIUS accounts for every attendee walk-up fails by concept: minting Enterprise identities for transient festival-goers is operationally unrealistic and not the documented public path.
Exam caveat: event Wi-Fi still obeys the design doc. CWTS technicians implement specified public controls; they do not substitute WEP art projects or mass Enterprise account creation.
Operational check: deploy the festival captive portal SSID per design; walk-test association → terms → internet; keep staff Enterprise SSIDs separate; tear down or disable the event SSID after the festival per change control.