Question 650
In the following Fortinet incident—Branches in a global SD-WAN attempt to use the same shared route preference for regional and interregional services—what concern should the team explicitly mitigate?
Explanation
Correct Answer
This is the most direct failure mode to prevent. Its technical cause or boundary is: Routing priority must distinguish regional reachability from approved interregion transit. Apply the change: Define route origination, preference and fallback across the regional hub topology. The result to verify is: Traffic from each region follows its intended preferred and backup paths.
Incorrect Answers
This option serves the scenario “An architect chooses an internet-only branch breakout design although policy requires data center inspection of regulated traffic”. This hazard is more relevant than general operational concerns because the breakout model must reflect traffic classification and mandated security enforcement points. The present scenario is distinguished by “Ambiguous regional preference can create loops or expensive interregional detours”.
This alternative addresses the separate case “A regional bank connects fifty branches and plans to send every voice call through one distant headquarters hub”. The reason is: A single distant transit point can violate regional latency targets despite healthy branch underlays. The deciding requirement here is “Ambiguous regional preference can create loops or expensive interregional detours”.
The related but distinct situation is “A service provider wants to validate multiregion SD-WAN failover but checks only the FortiManager template status”. The failure exposure comes from the underlying condition: Configuration distribution is distinct from observed operational overlay health. For the stated problem, “Ambiguous regional preference can create loops or expensive interregional detours” addresses the central condition.