Question 190
A Fortinet SD-WAN/FortiSASE operations team encounters the following situation: A hub advertises internal IP space to spokes using a summary that accidentally includes a prohibited management subnet. After the correction is implemented, which observable result most specifically proves this incident was resolved?
Explanation
Correct Answer
This result directly tests whether the observed failure has cleared: A hub advertises internal IP space to spokes using a summary that accidentally includes a prohibited management subnet. It confirms the targeted change, Constrain advertisements and route-map prefix filters to authorized service networks, rather than a healthy but unrelated component. The technical cause under test is: Route aggregation is broader than the intended reachability policy.
Incorrect Answers
That observation verifies a different Configure SD-WAN routing condition, namely: A disaster-recovery branch has member static routes but no valid default route for DNS resolvers outside any VPN prefix. It could be true even if the current failure persists. In this case the decisive evidence is tied to: Route aggregation is broader than the intended reachability policy.
That observation verifies a different Configure SD-WAN routing condition, namely: A spoke's BGP neighbor is established but route next hops for learned application prefixes are unreachable over the selected overlay. It could be true even if the current failure persists. In this case the decisive evidence is tied to: Route aggregation is broader than the intended reachability policy.
That observation verifies a different Configure SD-WAN routing condition, namely: A branch imports a service route from its overlay and accidentally advertises it back to the same BGP domain, creating unstable alternate paths. It could be true even if the current failure persists. In this case the decisive evidence is tied to: Route aggregation is broader than the intended reachability policy.