Question 340
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A company uses a rule matching a public CDN IP range that changes frequently and finds business SaaS traffic no longer matches. Which ongoing control best prevents the same issue from recurring?
Explanation
Correct Answer
In this situation, a company uses a rule matching a public CDN IP range that changes frequently and finds business SaaS traffic no longer matches. The relevant technical mechanism is: Static addressing can be too brittle for rapidly changing cloud destinations. The most direct diagnostic or implementation action is: Use an appropriate supported application or internet-service destination criterion where feasible. A useful verification is: Traffic to current sanctioned SaaS endpoints follows the intended steer even after CDN address changes. An ongoing safeguard is: Audit SaaS detection rules after major provider changes. 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
That safeguard is relevant to: Broad destination classifications can fail to identify the specific application required. The current failure instead follows from: Static addressing can be too brittle for rapidly changing cloud destinations. Its prevention measure is “Audit SaaS detection rules after major provider changes”.
This routine guards against another mechanism: Application-based steering depends on identification data that may change over time. The recurring exposure in the current case is: Static addressing can be too brittle for rapidly changing cloud destinations. The matching preventive check is “Audit SaaS detection rules after major provider changes”.
That safeguard is relevant to: Member-probe reachability can differ from application route reachability. The current failure instead follows from: Static addressing can be too brittle for rapidly changing cloud destinations. Its prevention measure is “Audit SaaS detection rules after major provider changes”.