Question 60
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: An operations team enables SD-WAN at several branches by copying identical interface names that do not exist at every site. Which ongoing control best prevents the same issue from recurring?
Explanation
Correct Answer
In this situation, an operations team enables SD-WAN at several branches by copying identical interface names that do not exist at every site. The relevant technical mechanism is: A shared logical design cannot substitute for per-appliance physical interface identity. The most direct diagnostic or implementation action is: Apply device-specific interface mappings and validate each site before provisioning. A useful verification is: Each branch uses only its real connected transports and shows expected member state. An ongoing safeguard is: Version site-specific onboarding parameters and review drift. 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
The suggested review tracks a different technical risk: A competing physical-interface route can bypass the intended aggregate SD-WAN path. Here the sustained control must address: A shared logical design cannot substitute for per-appliance physical interface identity. Choose “Version site-specific onboarding parameters and review drift”.
That safeguard is relevant to: An implicit fallback strategy cannot express every application-specific security or routing restriction. The current failure instead follows from: A shared logical design cannot substitute for per-appliance physical interface identity. Its prevention measure is “Version site-specific onboarding parameters and review drift”.
This routine guards against another mechanism: Unassigned interfaces are not candidates for a zone-targeted SD-WAN rule. The recurring exposure in the current case is: A shared logical design cannot substitute for per-appliance physical interface identity. The matching preventive check is “Version site-specific onboarding parameters and review drift”.