Question 180
A security analyst investigates this Fortinet environment: A FortiGate receives a more-specific destination route from a dynamic routing peer and users are surprised it wins over the SD-WAN default. Before changing policy, which diagnostic observation should be collected first?
Explanation
Correct Answer
The first diagnostic step is to inspect the longest-prefix match, route source, and installed forwarding entry for the destination. The critical symptom is that a FortiGate receives a more-specific destination route from a dynamic routing peer and users are surprised it wins over the SD-WAN default. This narrows the failing policy, inspection or management stage before an administrator changes unrelated settings. Once verified, the appropriate next action is to correct the intended specific route or the advertised prefix instead of broadening generic internet steering; jumping straight to that change without checking the stated evidence increases the chance of a misleading result.
Incorrect Answers
Inspect route-table lookup, active static routes, and the required SD-WAN zone next-hop design. The alternative concerns routing-table lookup, active static routes, and the required SD-WAN zone next-hop design, not inspecting the longest-prefix match, route source, and installed forwarding entry for the destination.
Correlate the routing table, policy-route evaluation, SD-WAN rule match, and session debug trace. This assesses correlate the routing table, policy-route evaluation, SD-WAN rule match, and session debug trace; it does not determine the reported condition—a FortiGate receives a more-specific destination route from a dynamic routing peer and users are surprised it wins over the SD-WAN default.
Compare policy-route lookup, SD-WAN rules, and the effective route for a guest test flow. The case-specific requirement is inspecting the longest-prefix match, route source, and installed forwarding entry for the destination, which that option does not establish.