A city visitor-center WLAN must show guests an acceptable-use policy and record acceptance before Internet access begins. Which design best meets that goal?
Select an answer to reveal the explanation.
Short Explanation
Think of the captive portal like the turnstile at city hall: you see the rules, tap accept, then you get in. A flyer on the counter does not create a session start, and borrowing staff 802.1X is the wrong door for the public.
Full Explanation
Captive portals are the standard guest-WLAN control for presenting an acceptable-use policy and starting a controlled session after acceptance. Printed notices alone do not enforce acceptance or session start. Putting visitors on staff enterprise authentication mixes trust domains. DNS tricks without a portal do not satisfy AUP-acceptance and onboarding design for public city Wi-Fi.