Question 850
At a distributed branch estate, a test team is validating a change after this incident: A new SASE tunnel is established over one ISP, but FortiGate monitoring treats its health as equivalent to the underlying Internet link and fails to detect cloud-gateway reachability loss. What evidence most directly verifies the intended outcome?
Explanation
Correct Answer
The cloud-path SLA fails on gateway outage while the physical ISP can remain up. This evidence directly tests the intended corrective action: Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions. It confirms the failure mechanism—Carrier link health and cloud security gateway availability are distinct signals.—has been addressed in the actual affected flow.
Incorrect Answers
The same restricted test category receives the required action across both protected access modes. This would verify resolution of a different case: An employee receives a SASE secure Internet policy from the cloud while branch local traffic uses a different direct Internet security profile, creating inconsistent URL blocks. It does not show that the reported issue was fixed or that its intended action—Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions.—worked.
A protected test subnet cannot bypass FortiSASE while documented exceptions function. This would verify resolution of a different case: An administrator activates a branch-to-SASE tunnel but leaves a broad local firewall bypass permitting protected subnets to egress directly. It does not show that the reported issue was fixed or that its intended action—Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions.—worked.
The authenticated tunnel reestablishes and test user sessions appear in cloud inspection logs. This would verify resolution of a different case: A new FortiSASE tunnel uses the branch's obsolete public IP as its remote peer after an ISP replacement, leaving site traffic uninspected. It does not show that the reported issue was fixed or that its intended action—Create an appropriate service-relevant health monitor for the cloud path and associate it with steering decisions.—worked.