Question 340
At Bluehaven Telecom, an infrastructure review by the carrier access engineering group is evaluating customer support tool reachability across a metropolitan customer service network after an audit of cloud access (FT-D-10-02). The review finds that a broad endpoint bypass list sends a sensitive SaaS application outside the FortiSASE inspection path. Any correction must respect this operating requirement: service management data cannot cross tenant boundaries. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that a broad endpoint bypass list sends a sensitive SaaS application outside the FortiSASE inspection path. Replace broad bypass entries with the smallest approved destination exceptions as part of Bluehaven Telecom's customer support tool reachability update (FT-D-10-02), while enforcing the constraint that service management data cannot cross tenant boundaries. A successful implementation must be checked rather than assumed: In a controlled a metropolitan customer service network acceptance test, A protected SaaS test remains cloud inspected while a documented exception bypasses only where allowed; the outcome is recorded under Bluehaven Telecom's rollout (FT-D-10-02). The technical reason is that Steering exceptions should be narrow because they can bypass inspection.
Incorrect Answers
The source case reports that a broad endpoint bypass list sends a sensitive SaaS application outside the FortiSASE inspection path. The offered alternative is useful for: Digital experience monitoring complements traffic logs with endpoint and path measurements. In this case the decisive mechanism is: Steering exceptions should be narrow because they can bypass inspection. The specific action is “Replace broad bypass entries with the smallest approved destination exceptions; confirm the dependent routing state”.
The source case reports that a broad endpoint bypass list sends a sensitive SaaS application outside the FortiSASE inspection path. This option would change the control governed by: Network lockdown enforces intended policy when secure connectivity becomes unavailable. That does not resolve the present failure, where steering exceptions should be narrow because they can bypass inspection. The applicable response is “Replace broad bypass entries with the smallest approved destination exceptions; confirm the dependent routing state”.
The source case reports that a broad endpoint bypass list sends a sensitive SaaS application outside the FortiSASE inspection path. The offered alternative is useful for: ZTNA private access evaluates per-application authorization instead of broad network reachability. In this case the decisive mechanism is: Steering exceptions should be narrow because they can bypass inspection. The specific action is “Replace broad bypass entries with the smallest approved destination exceptions; confirm the dependent routing state”.