Question 980
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A support desk investigates a critical tunnel outage but filters all logs to ordinary internet traffic, missing the relevant overlay events. Which ongoing control best prevents the same issue from recurring?
Explanation
Correct Answer
In this situation, a support desk investigates a critical tunnel outage but filters all logs to ordinary internet traffic, missing the relevant overlay events. The relevant technical mechanism is: An overly narrow log filter can hide the signals needed to diagnose the selected transport. The most direct diagnostic or implementation action is: Expand the query to the applicable tunnel, health-check and SD-WAN event categories. A useful verification is: The outage sequence identifies tunnel or member state changes at the correct time. An ongoing safeguard is: Maintain reusable per-service incident log queries. 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
This routine guards against another mechanism: Long averages can hide brief transport failures and selection churn. The recurring exposure in the current case is: An overly narrow log filter can hide the signals needed to diagnose the selected transport. The matching preventive check is “Maintain reusable per-service incident log queries”.
The suggested review tracks a different technical risk: Aggregate availability can conceal failure of a constituent transport. Here the sustained control must address: An overly narrow log filter can hide the signals needed to diagnose the selected transport. Choose “Maintain reusable per-service incident log queries”.
That safeguard is relevant to: Different log types represent different stages and cannot be summed as identical incidents. The current failure instead follows from: An overly narrow log filter can hide the signals needed to diagnose the selected transport. Its prevention measure is “Maintain reusable per-service incident log queries”.