Question 800
An architect analyzes this issue: A team adds a steering bypass for one captive portal hostname but accidentally bypasses all HTTPS destinations. Which operational or security exposure is most important to avoid?
Explanation
Correct Answer
This hazard is more relevant than general operational concerns because bypass lists need narrow verified criteria so security stays active for other traffic. Apply the limited change: Restrict the bypass to approved captive-portal dependencies and validate scope.
Incorrect Answers
The related but distinct situation is “A FortiClient endpoint on hotel Wi-Fi connects to SASE but the original hotel captive portal cannot be reached for initial sign-in”. This hazard is more relevant than general operational concerns because captive portal prerequisites may require a tightly scoped pre-tunnel steering exception. For the stated problem, “A broad bypass can nullify cloud inspection for most browser traffic” addresses the central condition.
This option serves the scenario “A team plans to disable network lockdown because a remote support tool fails to connect during device remediation”. This hazard is more relevant than general operational concerns because support exceptions should be narrowly scoped and compatible with the intended lockdown posture. The present scenario is distinguished by “A broad bypass can nullify cloud inspection for most browser traffic”.
This alternative does not match the described failure pattern. It concerns a security engineer gives the same private application permission to fully managed laptops and unknown personal tablets; the focused result here is: A broad bypass can nullify cloud inspection for most browser traffic.