Question 440
A FortiOS 7.6 team examines: A helpdesk must distinguish a static URL-filter deny from a FortiGuard category deny for a website. Select TWO complementary choices: the most appropriate corrective action AND the specific evidence confirming success.
Explanation
Correct Answers
The reported FortiOS 7.6 condition is: A helpdesk must distinguish a static URL-filter deny from a FortiGuard category deny for a website. The targeted administrative response is: Use precise URL-filter patterns and appropriate FortiGate rule action or precedence to handle approved site exceptions. The relevant failure risk is: A broad URL wildcard or wrongly ordered exception can allow unrelated destinations or block required ones. Validate with: Tests of the exact allowed and denied hostnames show the intended outcome and rule ID in logs.
For the observed situation (A helpdesk must distinguish a static URL-filter deny from a FortiGuard category deny for a website), the most specific acceptance evidence is: Tests of the exact allowed and denied hostnames show the intended outcome and rule ID in logs. It validates the recommended response: Use precise URL-filter patterns and appropriate FortiGate rule action or precedence to handle approved site exceptions. This addresses the documented risk: A broad URL wildcard or wrongly ordered exception can allow unrelated destinations or block required ones.
Incorrect Answers
Ips signature sensor and firewall attachment (3.5) would demonstrate or implement: An IPS profile that is absent from the matched allow rule cannot block a known threat against that traffic. The case states: A helpdesk must distinguish a static URL-filter deny from a FortiGuard category deny for a website. The most direct paired action and test is: Use precise URL-filter patterns and appropriate FortiGate rule action or precedence to handle approved site exceptions.
Ips false-positive exception and tuning (3.5) addresses another technical failure: Globally disabling an IPS category to suppress one suspected false positive can expose unrelated vulnerable services. This choice can be useful for that problem, but it does not establish the Static url filtering and rule precedence control being assessed here.
Application monitoring versus blocking (3.3) would demonstrate or implement: A controlled application session produces the configured log and is blocked only when the authorized rule requires enforcement. This case instead tests Static url filtering and rule precedence; the choice measures or changes another part of the system.