Question 960
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A company wants to investigate a slow ERP session but only stores the destination IP, not which SD-WAN member carried it. Which ongoing control best prevents the same issue from recurring?
Explanation
Correct Answer
In this situation, a company wants to investigate a slow ERP session but only stores the destination IP, not which SD-WAN member carried it. The relevant technical mechanism is: Application destination alone cannot establish link path or steering outcome. The most direct diagnostic or implementation action is: Enable appropriate session and SD-WAN metadata logging for the matching policy. A useful verification is: ERP samples can be associated with time, rule, selected member and quality measures. An ongoing safeguard is: Include member-level telemetry in critical-app monitoring baselines. 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: Policy enforcement may terminate traffic before path quality becomes relevant. The current failure instead follows from: Application destination alone cannot establish link path or steering outcome. Its prevention measure is “Include member-level telemetry in critical-app monitoring baselines”.
This routine guards against another mechanism: Local log availability is limited by storage and forwarding configuration. The recurring exposure in the current case is: Application destination alone cannot establish link path or steering outcome. The matching preventive check is “Include member-level telemetry in critical-app monitoring baselines”.
The suggested review tracks a different technical risk: An alert may be generated without stopping the corresponding transfer. Here the sustained control must address: Application destination alone cannot establish link path or steering outcome. Choose “Include member-level telemetry in critical-app monitoring baselines”.