Question 590
A FortiOS 7.6 team examines: Two routes share a gateway but the destination is inside only the more-specific network. Select TWO complementary choices: the most appropriate corrective action AND the specific evidence confirming success.
Explanation
Correct Answers
The reported FortiOS 7.6 condition is: Two routes share a gateway but the destination is inside only the more-specific network. The targeted administrative response is: Inspect the FortiGate routing table and choose the most specific eligible destination prefix before reviewing route preference. The relevant failure risk is: A broad default route cannot override an installed more-specific matching prefix solely because its interface is healthy. Validate with: A test destination uses the expected longest-prefix route and packet output agrees with the selected next hop.
For the observed situation (Two routes share a gateway but the destination is inside only the more-specific network), the most specific acceptance evidence is: A test destination uses the expected longest-prefix route and packet output agrees with the selected next hop. It validates the recommended response: Inspect the FortiGate routing table and choose the most specific eligible destination prefix before reviewing route preference. This addresses the documented risk: A broad default route cannot override an installed more-specific matching prefix solely because its interface is healthy.
Incorrect Answers
Sd-wan rule order and route interaction (4.2) addresses another technical failure: A matching SD-WAN rule cannot guarantee a working connection if candidate routes or the zone firewall policy are absent. The case states: Two routes share a gateway but the destination is inside only the more-specific network. The most direct paired action and test is: Inspect the FortiGate routing table and choose the most specific eligible destination prefix before reviewing route preference.
Sd-wan members and zones (4.2) would demonstrate or implement: SD-WAN member status, zone membership and a controlled flow agree with the approved path selection. This case instead tests Longest-prefix match and route lookup; the choice measures or changes another part of the system.
Sd-wan lowest-cost versus measured quality (4.2) would demonstrate or implement: Choosing solely by cost without an acceptable SLA can degrade services, while ignoring price can waste expensive WAN capacity. The required paired action and test concerns Longest-prefix match and route lookup; a passing result for this alternative could leave that requirement unresolved.