Question 490
A Fortinet SD-WAN/FortiSASE operations team encounters the following situation: An internal app uses long-lived HTTPS sessions, but users see sporadic failures after the SPA resource connector is updated and the team checks only DNS. After the correction is implemented, which observable result most specifically proves this incident was resolved?
Explanation
Correct Answer
This result directly tests whether the observed failure has cleared: An internal app uses long-lived HTTPS sessions, but users see sporadic failures after the SPA resource connector is updated and the team checks only DNS. It confirms the targeted change, Inspect the secure private access resource connection, policy evaluation and session path during the update, rather than a healthy but unrelated component. The technical cause under test is: Name resolution does not prove end-to-end SPA session continuity through the updated connector.
Incorrect Answers
That observation verifies a different Deploy cloud-delivered secure services condition, namely: A SaaS administrator sees that the application responds but cannot tell which access policy was applied to two user groups. It could be true even if the current failure persists. In this case the decisive evidence is tied to: Name resolution does not prove end-to-end SPA session continuity through the updated connector.
That observation verifies a different Deploy cloud-delivered secure services condition, namely: A region's primary SASE security PoP suffers a service interruption and the monitoring team does not know whether clients are reconnecting elsewhere. It could be true even if the current failure persists. In this case the decisive evidence is tied to: Name resolution does not prove end-to-end SPA session continuity through the updated connector.
That observation verifies a different Deploy cloud-delivered secure services condition, namely: A private claims system sits behind an on-premises FortiGate, but the SASE cloud policy references it without any configured authorized SPA route. It could be true even if the current failure persists. In this case the decisive evidence is tied to: Name resolution does not prove end-to-end SPA session continuity through the updated connector.