Question 280
After resolving A security team claims a successful SASE response because the cloud policy says block, even though logs show requests never reached the cloud, which evidence would establish that the requirement was met?
Explanation
Correct Answer
This is the specific acceptance result for the remediation: Confirm traffic steering into the POP and test an actual blocked request. It tests the underlying dependency: Enforcement requires traffic reach the inspection service and match the intended policy.
Incorrect Answers
The option would apply to “For this FortiSASE or SD-WAN problem, A SASE policy change coincides with an increase in denied SaaS requests but reporting omits policy revision identifiers”. The check verifies the actual business or network path after the step: Correlate rule version and change timestamp with user session denial trends. This question instead requires “The test request arrives at the cloud and is denied by the expected policy”.
The related but distinct situation is “An application team sees traffic logs but no SLA member-change events after an outage”. An effective postchange test must exercise the intended path. For the stated problem, “The test request arrives at the cloud and is denied by the expected policy” addresses the central condition.
This is a nearby Fortinet issue, not the current one. It deals with a branch session log identifies source and destination but no application name because inspection classified it as unknown. The correct answer to the stated case is: The test request arrives at the cloud and is denied by the expected policy.