Question 70
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A new branch shows internet access but FortiView has no meaningful per-link data because traffic logging was never enabled on the matching rule. Which observable result would best verify the correction?
Explanation
Correct Answer
In this situation, a new branch shows internet access but FortiView has no meaningful per-link data because traffic logging was never enabled on the matching rule. The relevant technical mechanism is: Traffic forwarding and telemetry generation require separate logging configuration. The most direct diagnostic or implementation action is: Enable suitable policy and SD-WAN event logging for the approved monitoring requirement. A useful verification is: Representative sessions can be traced to the selected WAN member in available logs. An ongoing safeguard is: Include monitoring evidence in operational handover, not only ping success. This is the INTENDED choice for the strongest verification evidence. The issuer documents define the topic and product background, not the truth of this item-level intended key.
Incorrect Answers
This observation would test a different technical dependency: Transport steering and content security are distinct controls that must both be configured. The current issue is governed by: Traffic forwarding and telemetry generation require separate logging configuration. Its decisive check is “Representative sessions can be traced to the selected WAN member in available logs”.
The alternative verifies a different condition: An implicit fallback strategy cannot express every application-specific security or routing restriction. The current case instead depends on: Traffic forwarding and telemetry generation require separate logging configuration. Confirm that “Representative sessions can be traced to the selected WAN member in available logs”.
That test belongs to another control with this basis: Unassigned interfaces are not candidates for a zone-targeted SD-WAN rule. In the current case, the governing reason is: Traffic forwarding and telemetry generation require separate logging configuration. The direct verification is “Representative sessions can be traced to the selected WAN member in available logs”.