Question 780
An operations group at a university network resolved: An SD-WAN rule sends traffic toward a FortiSASE tunnel but the tunnel is not part of the configured overlay SD-WAN zone. Which ongoing safeguard should become part of its change process?
Explanation
Correct Answer
Audit tunnel member and zone membership after cloud-branch integration. This control reduces recurrence of the documented mechanism: A tunnel interface is not a selectable SD-WAN service path until correctly included. It creates a repeatable check around the needed response: Add the approved cloud-connected tunnel as a monitored SD-WAN member in the correct zone.
Incorrect Answers
Test cloud tunnel initiation and rebinding under each ISP failure mode. That safeguard addresses another potential failure: A branch has two physical ISP links but the cloud security tunnel is pinned only to the primary interface, preventing SASE traffic from using the backup. It is not the most targeted recurring control for the described cause: A tunnel interface is not a selectable SD-WAN service path until correctly included.
Test private-app reachability and group authorization independently of Internet browsing. That safeguard addresses another potential failure: A company assumes remote FortiClient users can reach branch-only internal apps through the same secure Internet profile without configuring supported private application connectivity. It is not the most targeted recurring control for the described cause: A tunnel interface is not a selectable SD-WAN service path until correctly included.
Include cloud gateway failover tests in SD-WAN resilience acceptance plans. That safeguard addresses another potential failure: A branch integration uses only one FortiSASE cloud gateway despite having a high-availability objective across service locations. It is not the most targeted recurring control for the described cause: A tunnel interface is not a selectable SD-WAN service path until correctly included.