A city guest network already runs a legitimate captive portal. What testing-impact caution should guide an assessor's portal-related work?
Select an answer to reveal the explanation.
Short Explanation
Live guest Wi-Fi is full of real people trying to check email—do not turn their splash page into your all-day lab. Use a lab SSID or a narrow RoE window so you do not kneecap visitors. Continuous production thrash, neighbor phishing, or 'twins are impossible' myths are the wrong takeaways.
Full Explanation
When a city guest network already runs a legitimate captive portal, portal-related testing can disrupt guests; use lab SSIDs or tight windows per RoE. Production guest impact is a first-class constraint. Civic assessors should not assume continuous stress testing is harmless or that legitimate portals make twins impossible.
'Production guest portals can be stress-tested continuously with no guest impact' fails because production guest portals cannot be stress-tested continuously with no guest impact. 'Any portal test automatically authorizes phishing kits on neighboring private SSIDs' fails because a portal test does not automatically authorize phishing kits on neighboring private SSIDs. 'Legitimate portals prove rogue twins are impossible, so no lab controls are needed' fails because legitimate portals do not prove rogue twins are impossible or remove the need for lab controls.
Exam caveat: disruption risk can make portal tests out of scope—say so and offer lab alternatives. Operational check: negotiate maintenance windows, prefer isolated lab clones of the guest portal, monitor guest connectivity during any production-adjacent test, and abort on complaints. Document impact controls in the municipal RoE. In municipal wireless operations, record the rationale in the engagement notes so future assessors know which control or technique class was chosen and which failure modes the rejected options would create for city services.