At a supply-chain company running FortiOS 7.6, a branch host uses a broad route to the Internet even though an overlapping more-specific route should send traffic to a private MPLS peer. Which configuration or investigative change most directly resolves this issue?
Check longest-prefix routing and install the appropriately specific destination route. IP route selection prefers the most-specific matching prefix before other selection criteria. This corrects the FortiGate behavior described by the specific longest prefix match fault.
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 longest prefix match condition: a branch host uses a broad route to the Internet even though an overlapping more-specific route should send traffic to a private MPLS peer.
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 longest prefix match; the recommended correction addresses that dependency.
The proposed setting concerns default route gateway, not the actual source of failure. IP route selection prefers the most-specific matching prefix before other selection criteria. It would leave the cited symptom unresolved.
During an approved policy change, two valid static routes match one destination and the administrator must predict the selected path. What should the FortiGate administrator change to meet the stated requirement?
Check longest-prefix routing and install the appropriately specific destination route. IP route selection prefers the most-specific matching prefix before other selection criteria. This corrects the FortiGate behavior described by the specific longest prefix match fault.
The proposed setting concerns default route gateway, not the actual source of failure. IP route selection prefers the most-specific matching prefix before other selection criteria. 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 longest prefix match condition: two valid static routes match one destination and the administrator must predict the selected path.
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 longest prefix match; the recommended correction addresses that dependency.
A municipal network discovers a FortiGate control gap during a planned cutover: a branch host uses a broad route to the Internet even though an overlapping more-specific route should send traffic to a private MPLS peer; additionally, two valid static routes match one destination and the administrator must predict the selected path. Which targeted correction should the team implement?
Check longest-prefix routing and install the appropriately specific destination route. IP route selection prefers the most-specific matching prefix before other selection criteria. This corrects the FortiGate behavior described by the specific longest prefix match fault.
The proposed setting concerns missing return route, not the actual source of failure. IP route selection prefers the most-specific matching prefix before other selection criteria. It would leave the cited symptom unresolved.
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 longest prefix match; the recommended correction addresses that dependency.
The proposed setting concerns equal-cost multipath routes, not the actual source of failure. IP route selection prefers the most-specific matching prefix before other selection criteria. It would leave the cited symptom unresolved.
The managed services provider team is verifying its fix for an incident where a branch host uses a broad route to the Internet even though an overlapping more-specific route should send traffic to a private MPLS peer. Which specific observation most convincingly demonstrates the required FortiGate behavior?
A route lookup for the specific subnet chooses its longer-prefix next hop instead of the generic route. IP route selection prefers the most-specific matching prefix before other selection criteria. This is directly observable evidence for the longest prefix match requirement, rather than a generic appliance-health indicator.
That observation is a useful test for administrative distance backup, but not decisive proof of longest prefix match. 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: static route wrong next hop. IP route selection prefers the most-specific matching prefix before other selection criteria. The stated incident requires evidence of its own packet, identity or policy behavior.
That observation is a useful test for policy route precedence, but not decisive proof of longest prefix match. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. The recorded acceptance check must demonstrate the actual requirement.
After a new branch activation, administrators correct a problem where two valid static routes match one destination and the administrator must predict the selected path. Which test result should their acceptance record contain?
A route lookup for the specific subnet chooses its longer-prefix next hop instead of the generic route. IP route selection prefers the most-specific matching prefix before other selection criteria. This is directly observable evidence for the longest prefix match requirement, rather than a generic appliance-health indicator.
This verifies a different control: equal-cost multipath routes. IP route selection prefers the most-specific matching prefix before other selection criteria. The stated incident requires evidence of its own packet, identity or policy behavior.
A result about policy route precedence can be true while the longest prefix match 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 longest prefix match. Successful routed connectivity depends on both outbound forwarding and a usable return path. The recorded acceptance check must demonstrate the actual requirement.
An auditor reviewing a research institute deployment finds that a branch host uses a broad route to the Internet even though an overlapping more-specific route should send traffic to a private MPLS peer. The team claims this is resolved; which concrete evidence would substantiate that claim?
A route lookup for the specific subnet chooses its longer-prefix next hop instead of the generic route. IP route selection prefers the most-specific matching prefix before other selection criteria. This is directly observable evidence for the longest prefix match requirement, rather than a generic appliance-health indicator.
That observation is a useful test for policy route precedence, but not decisive proof of longest prefix match. FortiOS policy routes may influence forwarding for matched traffic separately from conventional static routes. The recorded acceptance check must demonstrate the actual requirement.
This verifies a different control: administrative distance backup. IP route selection prefers the most-specific matching prefix before other selection criteria. The stated incident requires evidence of its own packet, identity or policy behavior.
A result about default route gateway can be true while the longest prefix match defect persists. A default route supplies forwarding for destinations without a more specific route. It does not validate the tested dependency.
If a public library system leaves the following FortiGate issue unresolved—a branch host uses a broad route to the Internet even though an overlapping more-specific route should send traffic to a private MPLS peer—what is the most direct operational or security consequence?
Traffic may follow an unintended uplink when a needed specific prefix is missing. IP route selection prefers the most-specific matching prefix before other selection criteria. The described exposure follows from leaving the longest prefix match dependency unresolved.
That risk is associated with equal-cost multipath routes rather than the failing longest prefix match dependency. ECMP uses eligible routes of equal preference for multipath forwarding according to configured behavior. The present scenario establishes a different causal exposure.
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 longest prefix match unresolved.
That risk is associated with missing return route rather than the failing longest prefix match dependency. Successful routed connectivity depends on both outbound forwarding and a usable return path. The present scenario establishes a different causal exposure.
During a configuration recovery exercise, engineers discover that two valid static routes match one destination and the administrator must predict the selected path. What specific failure risk follows if the underlying fault remains?
Traffic may follow an unintended uplink when a needed specific prefix is missing. IP route selection prefers the most-specific matching prefix before other selection criteria. The described exposure follows from leaving the longest prefix match dependency unresolved.
It would be a concern if default route gateway were misconfigured. Here IP route selection prefers the most-specific matching prefix before other selection criteria. 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 longest prefix match unresolved.
It would be a concern if administrative distance backup were misconfigured. Here IP route selection prefers the most-specific matching prefix before other selection criteria. The selected alternative does not follow from the observed fault.
A post-incident review at a factory network identifies that a branch host uses a broad route to the Internet even though an overlapping more-specific route should send traffic to a private MPLS peer. The same control is still uncorrected. Which exposure should the risk register record?
Traffic may follow an unintended uplink when a needed specific prefix is missing. IP route selection prefers the most-specific matching prefix before other selection criteria. The described exposure follows from leaving the longest prefix match dependency unresolved.
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 longest prefix match unresolved.
That risk is associated with administrative distance backup rather than the failing longest prefix match 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 policy route precedence were misconfigured. Here IP route selection prefers the most-specific matching prefix before other selection criteria. The selected alternative does not follow from the observed fault.
At a retail logistics company running FortiOS 7.6, a FortiGate uses two default routes but a backup ISP is currently preferred over the primary. Which configuration or investigative change most directly resolves this issue?
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 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 administrative distance backup; the recommended correction addresses that dependency.
The proposed setting concerns missing return route, 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.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
