Question 680
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A branch adds a second private subnet but leaves SASE-integrated routing limited to the old prefix. Which ongoing control best prevents the same issue from recurring?
Explanation
Correct Answer
In this situation, a branch adds a second private subnet but leaves SASE-integrated routing limited to the old prefix. The relevant technical mechanism is: A new LAN prefix is not implicitly reachable through existing overlay advertisements. The most direct diagnostic or implementation action is: Update only the authorized subnet routes and protected-access policy scope. A useful verification is: Users can reach both approved internal subnets without gaining access to others. An ongoing safeguard is: Synchronize private-network changes with SASE route inventory. 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
The suggested review tracks a different technical risk: Broad route advertisements may expand possible network reachability beyond intended least privilege. Here the sustained control must address: A new LAN prefix is not implicitly reachable through existing overlay advertisements. Choose “Synchronize private-network changes with SASE route inventory”.
That safeguard is relevant to: A tunnel cannot connect when its current cloud peer is blocked by upstream egress policy. The current failure instead follows from: A new LAN prefix is not implicitly reachable through existing overlay advertisements. Its prevention measure is “Synchronize private-network changes with SASE route inventory”.
This routine guards against another mechanism: Coarse geographic restrictions may conflate legitimate travel with unapproved locations. The recurring exposure in the current case is: A new LAN prefix is not implicitly reachable through existing overlay advertisements. The matching preventive check is “Synchronize private-network changes with SASE route inventory”.