Question 620
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A mobile worker reports SASE policy not applying, but its FortiClient secure connection is disconnected after sleep recovery. Which ongoing control best prevents the same issue from recurring?
Explanation
Correct Answer
In this situation, a mobile worker reports SASE policy not applying, but its FortiClient secure connection is disconnected after sleep recovery. The relevant technical mechanism is: Cloud policy cannot inspect traffic that never enters the SASE forwarding path. The most direct diagnostic or implementation action is: Restore the client session and verify actual traffic forwarding through the service before evaluating policies. A useful verification is: User traffic appears at the intended enforcement point after reconnection. An ongoing safeguard is: Monitor endpoint connection state and resume behavior. This is the INTENDED choice for the most useful ongoing preventive control. The issuer documents define the topic and product background, not the truth of this item-level intended key.
Incorrect Answers
This routine guards against another mechanism: Stale cached credentials can fail despite healthy FortiSASE service and network transport. The recurring exposure in the current case is: Cloud policy cannot inspect traffic that never enters the SASE forwarding path. The matching preventive check is “Monitor endpoint connection state and resume behavior”.
The suggested review tracks a different technical risk: Successful outbound connection attempts do not prove the complete authentication exchange can return. Here the sustained control must address: Cloud policy cannot inspect traffic that never enters the SASE forwarding path. Choose “Monitor endpoint connection state and resume behavior”.
This routine guards against another mechanism: A single underlay path remains a failure point even with a resilient cloud security service. The recurring exposure in the current case is: Cloud policy cannot inspect traffic that never enters the SASE forwarding path. The matching preventive check is “Monitor endpoint connection state and resume behavior”.