During a weekend failover rehearsal, failover planning requires one next hop to remain standby until the preferred route is removed. What should the FortiGate administrator change to meet the stated requirement?
Configure the primary static route with a better administrative distance than the backup route. Static route distance helps choose between competing route sources with the same destination prefix. This corrects the FortiGate behavior described by the specific administrative distance backup fault.
Changing this could help when the fault is static route wrong next hop, because static routes need viable forwarding next hops on appropriate interfaces. Here the evidence instead identifies administrative distance backup; the recommended correction addresses that dependency.
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 administrative distance backup condition: failover planning requires one next hop to remain standby until the preferred route is removed.
Changing this could help when the fault is policy route precedence, because fortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. Here the evidence instead identifies administrative distance backup; the recommended correction addresses that dependency.
An international service desk discovers a FortiGate control gap during a configuration recovery exercise: a FortiGate uses two default routes but a backup ISP is currently preferred over the primary; additionally, failover planning requires one next hop to remain standby until the preferred route is removed. Which targeted correction should the team implement?
Configure the primary static route with a better administrative distance than the backup route. Static route distance helps choose between competing route sources with the same destination prefix. This corrects the FortiGate behavior described by the specific administrative distance backup fault.
The proposed setting concerns longest prefix match, not the actual source of failure. Static route distance helps choose between competing route sources with the same destination prefix. It would leave the cited symptom unresolved.
This correction targets policy route precedence. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. It does not repair the stated administrative distance backup condition: a FortiGate uses two default routes but a backup ISP is currently preferred over the primary.
The proposed setting concerns equal-cost multipath routes, not the actual source of failure. Static route distance helps choose between competing route sources with the same destination prefix. It would leave the cited symptom unresolved.
The distributed engineering campus team is verifying its fix for an incident where a FortiGate uses two default routes but a backup ISP is currently preferred over the primary. Which specific observation most convincingly demonstrates the required FortiGate behavior?
With both links healthy routing selects primary, and after its removal the standby becomes eligible. Static route distance helps choose between competing route sources with the same destination prefix. This is directly observable evidence for the administrative distance backup requirement, rather than a generic appliance-health indicator.
That observation is a useful test for blackhole route for fail-closed traffic, but not decisive proof of administrative distance backup. A blackhole route can provide safe fallback forwarding when an intended more-specific path disappears. The recorded acceptance check must demonstrate the actual requirement.
This verifies a different control: static route wrong next hop. Static route distance helps choose between competing route sources with the same destination prefix. The stated incident requires evidence of its own packet, identity or policy behavior.
A result about policy route precedence can be true while the administrative distance backup defect persists. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. It does not validate the tested dependency.
After an incident-response triage, administrators correct a problem where failover planning requires one next hop to remain standby until the preferred route is removed. Which test result should their acceptance record contain?
With both links healthy routing selects primary, and after its removal the standby becomes eligible. Static route distance helps choose between competing route sources with the same destination prefix. This is directly observable evidence for the administrative distance backup requirement, rather than a generic appliance-health indicator.
A result about static route wrong next hop can be true while the administrative distance backup defect persists. Static routes need viable forwarding next hops on appropriate interfaces. It does not validate the tested dependency.
That observation is a useful test for missing return route, but not decisive proof of administrative distance backup. 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: blackhole route for fail-closed traffic. Static route distance helps choose between competing route sources with the same destination prefix. The stated incident requires evidence of its own packet, identity or policy behavior.
An auditor reviewing a multi-site university deployment finds that a FortiGate uses two default routes but a backup ISP is currently preferred over the primary. The team claims this is resolved; which concrete evidence would substantiate that claim?
With both links healthy routing selects primary, and after its removal the standby becomes eligible. Static route distance helps choose between competing route sources with the same destination prefix. This is directly observable evidence for the administrative distance backup requirement, rather than a generic appliance-health indicator.
A result about longest prefix match can be true while the administrative distance backup defect persists. IP route selection prefers the most-specific matching prefix before other selection criteria. It does not validate the tested dependency.
This verifies a different control: blackhole route for fail-closed traffic. Static route distance helps choose between competing route sources with the same destination prefix. The stated incident requires evidence of its own packet, identity or policy behavior.
A result about default route gateway can be true while the administrative distance backup defect persists. A default route supplies forwarding for destinations without a more specific route. It does not validate the tested dependency.
If a regional manufacturing group leaves the following FortiGate issue unresolved—a FortiGate uses two default routes but a backup ISP is currently preferred over the primary—what is the most direct operational or security consequence?
Unexpected route preference can shift traffic to a costly or low-quality backup. Static route distance helps choose between competing route sources with the same destination prefix. The described exposure follows from leaving the administrative distance backup dependency unresolved.
That risk is associated with policy route precedence rather than the failing administrative distance backup dependency. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. The present scenario establishes a different causal exposure.
It would be a concern if longest prefix match were misconfigured. Here Static route distance helps choose between competing route sources with the same destination prefix. The selected alternative does not follow from the observed fault.
That risk is associated with equal-cost multipath routes rather than the failing administrative distance backup dependency. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. The present scenario establishes a different causal exposure.
During a segmentation review, engineers discover that failover planning requires one next hop to remain standby until the preferred route is removed. What specific failure risk follows if the underlying fault remains?
Unexpected route preference can shift traffic to a costly or low-quality backup. Static route distance helps choose between competing route sources with the same destination prefix. The described exposure follows from leaving the administrative distance backup dependency unresolved.
It would be a concern if equal-cost multipath routes were misconfigured. Here Static route distance helps choose between competing route sources with the same destination prefix. The selected alternative does not follow from the observed fault.
This describes a separate default route gateway failure. A default route supplies forwarding for destinations without a more specific route. It does not identify the most direct consequence of leaving administrative distance backup unresolved.
That risk is associated with static route wrong next hop rather than the failing administrative distance backup dependency. Static routes need viable forwarding next hops on appropriate interfaces. The present scenario establishes a different causal exposure.
A post-incident review at a customer support center identifies that a FortiGate uses two default routes but a backup ISP is currently preferred over the primary. The same control is still uncorrected. Which exposure should the risk register record?
Unexpected route preference can shift traffic to a costly or low-quality backup. Static route distance helps choose between competing route sources with the same destination prefix. The described exposure follows from leaving the administrative distance backup dependency unresolved.
That risk is associated with static route wrong next hop rather than the failing administrative distance backup 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 missing return route were misconfigured. Here Static route distance helps choose between competing route sources with the same destination prefix. The selected alternative does not follow from the observed fault.
This describes a separate policy route precedence failure. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. It does not identify the most direct consequence of leaving administrative distance backup unresolved.
At a municipal network running FortiOS 7.6, two equal-cost WAN next hops exist but FortiGate currently installs only one of them. Which configuration or investigative change most directly resolves this issue?
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.
This correction targets administrative distance backup. Static route distance helps choose between competing route sources with the same destination prefix. 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.
The proposed setting concerns static route wrong next hop, 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.
During a quarterly security audit, administrators want eligible equal-cost paths to be used by supported routing and session selection. What should the FortiGate administrator change to meet the stated requirement?
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.
Changing this could help when the fault is static route wrong next hop, because static routes need viable forwarding next hops on appropriate interfaces. Here the evidence instead identifies equal-cost multipath routes; the recommended correction addresses that dependency.
The proposed setting concerns default route gateway, 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.
Changing this could help when the fault is longest prefix match, because iP route selection prefers the most-specific matching prefix before other selection criteria. Here the evidence instead identifies equal-cost multipath routes; the recommended correction addresses that dependency.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
