Question 770
A deployment engineer must resolve the following case: A hub BGP peer runs on the tunnel interface although the chosen design explicitly requires a stable loopback peering endpoint. What is the most appropriate supported action?
Explanation
Correct Answer
The focused remedy is: Align peer addresses, reachability and route advertisements with the selected loopback design. The underlying dependency is: BGP on loopback and BGP per-overlay have different next-hop and failover assumptions. The acceptance check is: BGP remains established through allowed overlay changes under the documented topology.
Incorrect Answers
This is a nearby Fortinet issue, not the current one. It deals with a large SD-WAN overlay enables BGP additional paths without validating what routes are advertised or accepted. The correct answer to the stated case is: Align peer addresses, reachability and route advertisements with the selected loopback design.
That proposal leaves the central dependency unresolved. The correction is: Align peer addresses, reachability and route advertisements with the selected loopback design. The expected acceptance result is: BGP remains established through allowed overlay changes under the documented topology.
The option would apply to “A branch overlay frequently drops large HTTPS sessions while small ICMP probes succeed”. The corrective step is: Measure effective MTU and apply supported MSS or fragmentation adjustments to the overlay. This question instead requires “Align peer addresses, reachability and route advertisements with the selected loopback design”.