300-430 · Question #105
The security policy mandates that only controller web management traffic is allowed from the IT subnet. In testing, an engineer is trying to connect to a WLAN with Web Authentication for guest…
The correct answer is D. The implemented CPU ACL on the controller is blocking HTTP/HTTPS traffic from the guest. The issue is likely caused by the CPU ACL on the controller, which is blocking HTTP/HTTPS traffic from the guest clients. When a WLAN with Web Authentication is used, the wireless client's browser is redirected to a web page for authentication. If the CPU ACL is configured to…
Question
The security policy mandates that only controller web management traffic is allowed from the IT subnet. In testing, an engineer is trying to connect to a WLAN with Web Authentication for guest users, but the page is timing out on the wireless client browser. What is the cause of this issue?
Options
- AWeb Authentication Redirect is supported only with Internet Explorer, and the client is using
- BThe DNS server that is configured on the controller is incorrect
- CWeb Authentication Redirect is not supported with CPU ACLS.
- DThe implemented CPU ACL on the controller is blocking HTTP/HTTPS traffic from the guest
How the community answered
(48 responses)- A10% (5)
- B21% (10)
- C4% (2)
- D65% (31)
Explanation
The issue is likely caused by the CPU ACL on the controller, which is blocking HTTP/HTTPS traffic from the guest clients. When a WLAN with Web Authentication is used, the wireless client's browser is redirected to a web page for authentication. If the CPU ACL is configured to only allow controller web management traffic from the IT subnet, it may inadvertently block the necessary HTTP/HTTPS traffic for the Web Authentication process, leading to a timeout on the wireless
Topics
Community Discussion
No community discussion yet for this question.