A regional hospital discovers a FortiGate control gap during a segmentation review: two equal-cost WAN next hops exist but FortiGate currently installs only one of them; additionally, administrators want eligible equal-cost paths to be used by supported routing and session selection. Which targeted correction should the team implement?
Configure eligible equal-cost static routes and confirm FortiOS ECMP settings and compatibility. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. This corrects the FortiGate behavior described by the specific equal-cost multipath routes fault.
The proposed setting concerns administrative distance backup, not the actual source of failure. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. It would leave the cited symptom unresolved.
This correction targets blackhole route for fail-closed traffic. A blackhole route can provide safe fallback forwarding when an intended more-specific path disappears. It does not repair the stated equal-cost multipath routes condition: two equal-cost WAN next hops exist but FortiGate currently installs only one of them.
Changing this could help when the fault is default route gateway, because a default route supplies forwarding for destinations without a more specific route. Here the evidence instead identifies equal-cost multipath routes; the recommended correction addresses that dependency.
The research institute team is verifying its fix for an incident where two equal-cost WAN next hops exist but FortiGate currently installs only one of them. Which specific observation most convincingly demonstrates the required FortiGate behavior?
The routing table contains the expected equal-cost routes and test flows use supported path selection. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. This is directly observable evidence for the equal-cost multipath routes requirement, rather than a generic appliance-health indicator.
This verifies a different control: blackhole route for fail-closed traffic. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. The stated incident requires evidence of its own packet, identity or policy behavior.
A result about policy route precedence can be true while the equal-cost multipath routes defect persists. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. It does not validate the tested dependency.
That observation is a useful test for missing return route, but not decisive proof of equal-cost multipath routes. Successful routed connectivity depends on both outbound forwarding and a usable return path. The recorded acceptance check must demonstrate the actual requirement.
After a post-upgrade smoke test, administrators correct a problem where administrators want eligible equal-cost paths to be used by supported routing and session selection. Which test result should their acceptance record contain?
The routing table contains the expected equal-cost routes and test flows use supported path selection. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. This is directly observable evidence for the equal-cost multipath routes requirement, rather than a generic appliance-health indicator.
This verifies a different control: administrative distance backup. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. The stated incident requires evidence of its own packet, identity or policy behavior.
That observation is a useful test for missing return route, but not decisive proof of equal-cost multipath routes. Successful routed connectivity depends on both outbound forwarding and a usable return path. The recorded acceptance check must demonstrate the actual requirement.
This verifies a different control: static route wrong next hop. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. The stated incident requires evidence of its own packet, identity or policy behavior.
An auditor reviewing a cloud operations team deployment finds that two equal-cost WAN next hops exist but FortiGate currently installs only one of them. The team claims this is resolved; which concrete evidence would substantiate that claim?
The routing table contains the expected equal-cost routes and test flows use supported path selection. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. This is directly observable evidence for the equal-cost multipath routes requirement, rather than a generic appliance-health indicator.
A result about longest prefix match can be true while the equal-cost multipath routes defect persists. IP route selection prefers the most-specific matching prefix before other selection criteria. It does not validate the tested dependency.
That observation is a useful test for static route wrong next hop, but not decisive proof of equal-cost multipath routes. Static routes need viable forwarding next hops on appropriate interfaces. The recorded acceptance check must demonstrate the actual requirement.
A result about missing return route can be true while the equal-cost multipath routes defect persists. Successful routed connectivity depends on both outbound forwarding and a usable return path. It does not validate the tested dependency.
If a factory network leaves the following FortiGate issue unresolved—two equal-cost WAN next hops exist but FortiGate currently installs only one of them—what is the most direct operational or security consequence?
Traffic may remain concentrated on one link despite redundant equal-cost capacity. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. The described exposure follows from leaving the equal-cost multipath routes dependency unresolved.
That risk is associated with static route wrong next hop rather than the failing equal-cost multipath routes dependency. Static routes need viable forwarding next hops on appropriate interfaces. The present scenario establishes a different causal exposure.
It would be a concern if default route gateway were misconfigured. Here ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. The selected alternative does not follow from the observed fault.
This describes a separate missing return route failure. Successful routed connectivity depends on both outbound forwarding and a usable return path. It does not identify the most direct consequence of leaving equal-cost multipath routes unresolved.
During a partner connectivity test, engineers discover that administrators want eligible equal-cost paths to be used by supported routing and session selection. What specific failure risk follows if the underlying fault remains?
Traffic may remain concentrated on one link despite redundant equal-cost capacity. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. The described exposure follows from leaving the equal-cost multipath routes dependency unresolved.
This describes a separate longest prefix match failure. IP route selection prefers the most-specific matching prefix before other selection criteria. It does not identify the most direct consequence of leaving equal-cost multipath routes unresolved.
That risk is associated with default route gateway rather than the failing equal-cost multipath routes dependency. A default route supplies forwarding for destinations without a more specific route. The present scenario establishes a different causal exposure.
It would be a concern if static route wrong next hop were misconfigured. Here ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. The selected alternative does not follow from the observed fault.
A post-incident review at an e-commerce platform identifies that two equal-cost WAN next hops exist but FortiGate currently installs only one of them. The same control is still uncorrected. Which exposure should the risk register record?
Traffic may remain concentrated on one link despite redundant equal-cost capacity. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. The described exposure follows from leaving the equal-cost multipath routes dependency unresolved.
This describes a separate blackhole route for fail-closed traffic failure. A blackhole route can provide safe fallback forwarding when an intended more-specific path disappears. It does not identify the most direct consequence of leaving equal-cost multipath routes unresolved.
It would be a concern if default route gateway were misconfigured. Here ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. The selected alternative does not follow from the observed fault.
This describes a separate longest prefix match failure. IP route selection prefers the most-specific matching prefix before other selection criteria. It does not identify the most direct consequence of leaving equal-cost multipath routes unresolved.
At an international service desk running FortiOS 7.6, a private prefix should never escape through the public default route if its dedicated tunnel becomes unavailable. Which configuration or investigative change most directly resolves this issue?
Add a carefully scoped blackhole route with suitable preference for the protected prefix. A blackhole route can provide safe fallback forwarding when an intended more-specific path disappears. This corrects the FortiGate behavior described by the specific blackhole route for fail-closed traffic fault.
This correction targets longest prefix match. IP route selection prefers the most-specific matching prefix before other selection criteria. It does not repair the stated blackhole route for fail-closed traffic condition: a private prefix should never escape through the public default route if its dedicated tunnel becomes unavailable.
Changing this could help when the fault is default route gateway, because a default route supplies forwarding for destinations without a more specific route. Here the evidence instead identifies blackhole route for fail-closed traffic; the recommended correction addresses that dependency.
This correction targets missing return route. Successful routed connectivity depends on both outbound forwarding and a usable return path. It does not repair the stated blackhole route for fail-closed traffic condition: a private prefix should never escape through the public default route if its dedicated tunnel becomes unavailable.
During a planned cutover, after a VPN route withdrawal, traffic for a confidential network risks following a less-specific Internet route. What should the FortiGate administrator change to meet the stated requirement?
Add a carefully scoped blackhole route with suitable preference for the protected prefix. A blackhole route can provide safe fallback forwarding when an intended more-specific path disappears. This corrects the FortiGate behavior described by the specific blackhole route for fail-closed traffic fault.
Changing this could help when the fault is administrative distance backup, because static route distance helps choose between competing route sources with the same destination prefix. Here the evidence instead identifies blackhole route for fail-closed traffic; the recommended correction addresses that dependency.
The proposed setting concerns equal-cost multipath routes, not the actual source of failure. A blackhole route can provide safe fallback forwarding when an intended more-specific path disappears. It would leave the cited symptom unresolved.
This correction targets missing return route. Successful routed connectivity depends on both outbound forwarding and a usable return path. It does not repair the stated blackhole route for fail-closed traffic condition: after a VPN route withdrawal, traffic for a confidential network risks following a less-specific Internet route.
A financial services branch discovers a FortiGate control gap during a partner connectivity test: a private prefix should never escape through the public default route if its dedicated tunnel becomes unavailable; additionally, after a VPN route withdrawal, traffic for a confidential network risks following a less-specific Internet route. Which targeted correction should the team implement?
Add a carefully scoped blackhole route with suitable preference for the protected prefix. A blackhole route can provide safe fallback forwarding when an intended more-specific path disappears. This corrects the FortiGate behavior described by the specific blackhole route for fail-closed traffic fault.
This correction targets longest prefix match. IP route selection prefers the most-specific matching prefix before other selection criteria. It does not repair the stated blackhole route for fail-closed traffic condition: a private prefix should never escape through the public default route if its dedicated tunnel becomes unavailable.
Changing this could help when the fault is equal-cost multipath routes, because eCMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. Here the evidence instead identifies blackhole route for fail-closed traffic; the recommended correction addresses that dependency.
The proposed setting concerns administrative distance backup, not the actual source of failure. A blackhole route can provide safe fallback forwarding when an intended more-specific path disappears. It would leave the cited symptom unresolved.
The multi-site university team is verifying its fix for an incident where a private prefix should never escape through the public default route if its dedicated tunnel becomes unavailable. Which specific observation most convincingly demonstrates the required FortiGate behavior?
During tunnel loss the restricted prefix is discarded rather than forwarded through the generic default route. A blackhole route can provide safe fallback forwarding when an intended more-specific path disappears. This is directly observable evidence for the blackhole route for fail-closed traffic requirement, rather than a generic appliance-health indicator.
That observation is a useful test for default route gateway, but not decisive proof of blackhole route for fail-closed traffic. A default route supplies forwarding for destinations without a more specific route. The recorded acceptance check must demonstrate the actual requirement.
A result about equal-cost multipath routes can be true while the blackhole route for fail-closed traffic defect persists. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. It does not validate the tested dependency.
That observation is a useful test for policy route precedence, but not decisive proof of blackhole route for fail-closed traffic. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. The recorded acceptance check must demonstrate the actual requirement.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
