Question 750
During follow-up testing at a corporate headquarters, the original fault was: A new IPsec tunnel is added as an SD-WAN member yet the remote LAN gateway replies through a third-party cloud path because route advertisement is asymmetric. Which measured result demonstrates recovery rather than an unrelated improvement?
Explanation
Correct Answer
Packet captures show forward and return traffic traversing the intended approved overlay. This evidence directly tests the intended corrective action: Reconcile remote prefix advertisements and return routing to create a supported symmetric path. It confirms the failure mechanism—Asymmetric return routing may invalidate stateful security or NAT expectations.—has been addressed in the actual affected flow.
Incorrect Answers
After subsequent FortiManager installs the route table retains the intended overlay prefix path. This would verify resolution of a different case: A FortiGate has the correct SD-WAN zone route for corporate VPN but FortiManager installs a conflicting stale prefix route during configuration synchronization. It does not show that the reported issue was fixed or that its intended action—Reconcile remote prefix advertisements and return routing to create a supported symmetric path.—worked.
Syslog reaches the approved destination through its documented service path without altering user steering. This would verify resolution of a different case: A FortiGate sends firewall-originated syslog through a nonpreferred management route while user sessions correctly follow SD-WAN, leading staff to blame an SD-WAN rule. It does not show that the reported issue was fixed or that its intended action—Reconcile remote prefix advertisements and return routing to create a supported symmetric path.—worked.
Failure of the first ISP sends sessions through the second member with successful return traffic. This would verify resolution of a different case: An admin adds a route to an SD-WAN zone but leaves one member without its required gateway or health check, causing failover to an unusable next hop. It does not show that the reported issue was fixed or that its intended action—Reconcile remote prefix advertisements and return routing to create a supported symmetric path.—worked.