Which configuration best isolates guest traffic from internal resources?

Which configuration best isolates guest traffic from internal resources?

• A. Captive portal
• B. Geofencing
• C. Guest network
• D. WEP

Answer: (C)

The idea being tested is how to separate guest devices from the internal network so guests can access the internet but cannot reach internal resources. The best way is to configure a dedicated guest network—a separate SSID that maps to its own subnet or VLAN, with its own firewall rules and sometimes NAT. This setup ensures guest traffic is isolated from the internal network: the guest subnet is protected by access controls that block attempts to reach internal servers, while still allowing internet access. Often a captive portal is used on this network to require authentication, but isolation is achieved by keeping guests on a separate network and enforcing rules between that network and the internal one. The other options don’t provide this isolation by themselves. A captive portal is just a login gateway and, if not paired with proper network separation, doesn’t guarantee isolation. Geofencing relates to location-based behavior, not network isolation. WEP is an old, insecure security standard and has nothing to do with isolating guest traffic from internal resources.

The idea being tested is how to separate guest devices from the internal network so guests can access the internet but cannot reach internal resources. The best way is to configure a dedicated guest network—a separate SSID that maps to its own subnet or VLAN, with its own firewall rules and sometimes NAT. This setup ensures guest traffic is isolated from the internal network: the guest subnet is protected by access controls that block attempts to reach internal servers, while still allowing internet access. Often a captive portal is used on this network to require authentication, but isolation is achieved by keeping guests on a separate network and enforcing rules between that network and the internal one.

The other options don’t provide this isolation by themselves. A captive portal is just a login gateway and, if not paired with proper network separation, doesn’t guarantee isolation. Geofencing relates to location-based behavior, not network isolation. WEP is an old, insecure security standard and has nothing to do with isolating guest traffic from internal resources.