After a weekend failover rehearsal, administrators correct a problem where clients cannot reach a partner subnet after the WAN next-hop address changed. Which test result should their acceptance record contain?
The next hop resolves on the intended interface and controlled probes reach the partner network. Static routes need viable forwarding next hops on appropriate interfaces. This is directly observable evidence for the static route wrong next hop requirement, rather than a generic appliance-health indicator.
This verifies a different control: administrative distance backup. Static routes need viable forwarding next hops on appropriate interfaces. The stated incident requires evidence of its own packet, identity or policy behavior.
A result about equal-cost multipath routes can be true while the static route wrong next hop 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 blackhole route for fail-closed traffic, but not decisive proof of static route wrong next hop. A blackhole route can provide safe fallback forwarding when an intended more-specific path disappears. The recorded acceptance check must demonstrate the actual requirement.
An auditor reviewing a retail logistics company deployment finds that an installed route points to an unreachable gateway IP although the destination prefix is correct. The team claims this is resolved; which concrete evidence would substantiate that claim?
The next hop resolves on the intended interface and controlled probes reach the partner network. Static routes need viable forwarding next hops on appropriate interfaces. This is directly observable evidence for the static route wrong next hop requirement, rather than a generic appliance-health indicator.
That observation is a useful test for equal-cost multipath routes, but not decisive proof of static route wrong next hop. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. The recorded acceptance check must demonstrate the actual requirement.
This verifies a different control: longest prefix match. Static routes need viable forwarding next hops on appropriate interfaces. The stated incident requires evidence of its own packet, identity or policy behavior.
A result about default route gateway can be true while the static route wrong next hop defect persists. A default route supplies forwarding for destinations without a more specific route. It does not validate the tested dependency.
If an e-commerce platform leaves the following FortiGate issue unresolved—an installed route points to an unreachable gateway IP although the destination prefix is correct—what is the most direct operational or security consequence?
A syntactically present route can still fail if its next hop is not reachable. Static routes need viable forwarding next hops on appropriate interfaces. The described exposure follows from leaving the static route wrong next hop dependency unresolved.
That risk is associated with administrative distance backup rather than the failing static route wrong next hop dependency. Static route distance helps choose between competing route sources with the same destination prefix. The present scenario establishes a different causal exposure.
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 static route wrong next hop unresolved.
That risk is associated with missing return route rather than the failing static route wrong next hop dependency. Successful routed connectivity depends on both outbound forwarding and a usable return path. The present scenario establishes a different causal exposure.
During an incident-response triage, engineers discover that clients cannot reach a partner subnet after the WAN next-hop address changed. What specific failure risk follows if the underlying fault remains?
A syntactically present route can still fail if its next hop is not reachable. Static routes need viable forwarding next hops on appropriate interfaces. The described exposure follows from leaving the static route wrong next hop dependency unresolved.
It would be a concern if longest prefix match were misconfigured. Here Static routes need viable forwarding next hops on appropriate interfaces. 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 static route wrong next hop unresolved.
It would be a concern if policy route precedence were misconfigured. Here Static routes need viable forwarding next hops on appropriate interfaces. The selected alternative does not follow from the observed fault.
A post-incident review at a distributed engineering campus identifies that an installed route points to an unreachable gateway IP although the destination prefix is correct. The same control is still uncorrected. Which exposure should the risk register record?
A syntactically present route can still fail if its next hop is not reachable. Static routes need viable forwarding next hops on appropriate interfaces. The described exposure follows from leaving the static route wrong next hop 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 static route wrong next hop unresolved.
That risk is associated with administrative distance backup rather than the failing static route wrong next hop dependency. Static route distance helps choose between competing route sources with the same destination prefix. The present scenario establishes a different causal exposure.
It would be a concern if blackhole route for fail-closed traffic were misconfigured. Here Static routes need viable forwarding next hops on appropriate interfaces. The selected alternative does not follow from the observed fault.
At a financial services branch running FortiOS 7.6, ordinary routing selects wan1, but a configured policy route sends one application through wan2. Which configuration or investigative change most directly resolves this issue?
Review relevant policy routes and their matching source, destination, service and outgoing interface. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. This corrects the FortiGate behavior described by the specific policy route precedence fault.
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 policy route precedence; the recommended correction addresses that dependency.
The proposed setting concerns longest prefix match, not the actual source of failure. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. 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 policy route precedence condition: ordinary routing selects wan1, but a configured policy route sends one application through wan2.
During a segmentation review, a route lookup looks correct yet packets from a particular source follow an unexpected WAN interface. What should the FortiGate administrator change to meet the stated requirement?
Review relevant policy routes and their matching source, destination, service and outgoing interface. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. This corrects the FortiGate behavior described by the specific policy route precedence fault.
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 policy route precedence; the recommended correction addresses that dependency.
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 policy route precedence condition: a route lookup looks correct yet packets from a particular source follow an unexpected WAN interface.
Changing this could help when the fault is blackhole route for fail-closed traffic, because a blackhole route can provide safe fallback forwarding when an intended more-specific path disappears. Here the evidence instead identifies policy route precedence; the recommended correction addresses that dependency.
A regional manufacturing group discovers a FortiGate control gap during a incident-response triage: ordinary routing selects wan1, but a configured policy route sends one application through wan2; additionally, a route lookup looks correct yet packets from a particular source follow an unexpected WAN interface. Which targeted correction should the team implement?
Review relevant policy routes and their matching source, destination, service and outgoing interface. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. This corrects the FortiGate behavior described by the specific policy route precedence fault.
The proposed setting concerns default route gateway, not the actual source of failure. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. It would leave the cited symptom unresolved.
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 policy route precedence condition: ordinary routing selects wan1, but a configured policy route sends one application through wan2.
The proposed setting concerns static route wrong next hop, not the actual source of failure. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. It would leave the cited symptom unresolved.
The supply-chain company team is verifying its fix for an incident where ordinary routing selects wan1, but a configured policy route sends one application through wan2. Which specific observation most convincingly demonstrates the required FortiGate behavior?
Packet debug for the exact test flow identifies the intended policy-route selection or its absence. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. This is directly observable evidence for the policy route precedence requirement, rather than a generic appliance-health indicator.
That observation is a useful test for missing return route, but not decisive proof of policy route precedence. 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: longest prefix match. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. The stated incident requires evidence of its own packet, identity or policy behavior.
A result about administrative distance backup can be true while the policy route precedence defect persists. Static route distance helps choose between competing route sources with the same destination prefix. It does not validate the tested dependency.
After a quarterly security audit, administrators correct a problem where a route lookup looks correct yet packets from a particular source follow an unexpected WAN interface. Which test result should their acceptance record contain?
Packet debug for the exact test flow identifies the intended policy-route selection or its absence. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. This is directly observable evidence for the policy route precedence requirement, rather than a generic appliance-health indicator.
A result about blackhole route for fail-closed traffic can be true while the policy route precedence defect persists. A blackhole route can provide safe fallback forwarding when an intended more-specific path disappears. It does not validate the tested dependency.
That observation is a useful test for administrative distance backup, but not decisive proof of policy route precedence. Static route distance helps choose between competing route sources with the same destination prefix. The recorded acceptance check must demonstrate the actual requirement.
This verifies a different control: equal-cost multipath routes. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. The stated incident requires evidence of its own packet, identity or policy behavior.
An auditor reviewing a municipal network deployment finds that ordinary routing selects wan1, but a configured policy route sends one application through wan2. The team claims this is resolved; which concrete evidence would substantiate that claim?
Packet debug for the exact test flow identifies the intended policy-route selection or its absence. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. This is directly observable evidence for the policy route precedence requirement, rather than a generic appliance-health indicator.
A result about longest prefix match can be true while the policy route precedence 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: equal-cost multipath routes. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. The stated incident requires evidence of its own packet, identity or policy behavior.
A result about default route gateway can be true while the policy route precedence defect persists. A default route supplies forwarding for destinations without a more specific route. It does not validate the tested dependency.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
