NSE5_SSE_AD-7.6 Premium File
- 54 Questions & Answers
- Last Update: Nov 5, 2026
The recommended change has been applied. A FortiGate receives a branch prefix via BGP over an overlay, but the selected BGP next hop cannot be resolved to an active tunnel. Which observation best verifies the intended outcome?
The route resolves to the intended tunnel and representative private sessions complete. This is the directly relevant check for BGP route with unreachable recursive next hop. It confirms the required step: Restore next-hop reachability or supported route recursion for the overlay before accepting the prefix as usable. The operating principle is: BGP prefix receipt and route-to-next-hop resolution are separate requirements for forwarding.
New internet sessions can reach valid egress members and survive a controlled primary carrier failure. This would validate a different scenario, Default static route to SD-WAN zone, where A branch has two active SD-WAN members but the only default route still points directly at an old standalone WAN interface. The current case needs evidence for BGP route with unreachable recursive next hop.
The actual source/destination session shows which service and outbound interface the firewall selected. This would validate a different scenario, Traffic session table identifies selected route, where An operator claims SD-WAN selected the wrong link based only on aggregate interface bandwidth, but a particular application's active session is not inspected. The current case needs evidence for BGP route with unreachable recursive next hop.
Overlay health checks traverse their tunnel path and their status reflects actual private reachability. This would validate a different scenario, Overlay probe route conflicts with app data, where An SD-WAN health probe for a private tunnel target follows the public default route rather than the tunnel and falsely marks the overlay unavailable. The current case needs evidence for BGP route with unreachable recursive next hop.
An architect reviews the platform behavior behind this incident. A FortiGate receives a branch prefix via BGP over an overlay, but the selected BGP next hop cannot be resolved to an active tunnel. Which explanation applies?
BGP prefix receipt and route-to-next-hop resolution are separate requirements for forwarding. This explains BGP route with unreachable recursive next hop in the given environment. The implementation decision is: Restore next-hop reachability or supported route recursion for the overlay before accepting the prefix as usable. Confirm it with: The route resolves to the intended tunnel and representative private sessions complete.
Specific private prefixes should direct private application traffic to the correct overlay next hop. That concept concerns Private route leak to internet default, not the mechanism needed for BGP route with unreachable recursive next hop. The relevant principle is: BGP prefix receipt and route-to-next-hop resolution are separate requirements for forwarding.
Health probes need a valid forwarding route that represents the member being monitored. That concept concerns Overlay probe route conflicts with app data, not the mechanism needed for BGP route with unreachable recursive next hop. The relevant principle is: BGP prefix receipt and route-to-next-hop resolution are separate requirements for forwarding.
Session records contain forwarding state more specific than aggregate link utilization widgets. That concept concerns Traffic session table identifies selected route, not the mechanism needed for BGP route with unreachable recursive next hop. The relevant principle is: BGP prefix receipt and route-to-next-hop resolution are separate requirements for forwarding.
A support analyst is collecting data for this scenario. A FortiGate receives a branch prefix via BGP over an overlay, but the selected BGP next hop cannot be resolved to an active tunnel. Which diagnostic check is most targeted?
Inspect BGP RIB, resolved next-hop path, tunnel route and forwarding table. This inspection targets BGP route with unreachable recursive next hop rather than a different configuration issue. The corrective action is: Restore next-hop reachability or supported route recursion for the overlay before accepting the prefix as usable. Expected evidence: The route resolves to the intended tunnel and representative private sessions complete.
Inspect probe source, target route, tunnel state and captured packets. This is useful when diagnosing Overlay probe route conflicts with app data. Instead, inspect bgp rib, resolved next-hop path, tunnel route and forwarding table.
Inspect route table, SD-WAN zone route, member gateways and flow egress. This is useful when diagnosing Default static route to SD-WAN zone. Instead, inspect bgp rib, resolved next-hop path, tunnel route and forwarding table.
Inspect `diagnose sys session list`, SD-WAN service status and relevant traffic logs for the flow. This is useful when diagnosing Traffic session table identifies selected route. Instead, inspect bgp rib, resolved next-hop path, tunnel route and forwarding table.
A Fortinet administrator must address this operational problem. An administrator fixes a default route and expects an established video call to move immediately, but the session continues on its original member. Which response best resolves it?
Create controlled new flows and inspect session reevaluation behavior before labeling the route change ineffective. Session handling can retain prior forwarding decisions until reevaluation or termination conditions occur. Expected evidence: New sessions honor the corrected route while ongoing connections follow documented stateful behavior. Key limit: The session table is not necessarily rebuilt for every existing flow at each route update.
Use FortiOS session and SD-WAN diagnostics to correlate the specific flow's route, rule and member. This could apply to the separate issue Traffic session table identifies selected route: An operator claims SD-WAN selected the wrong link based only on aggregate interface bandwidth, but a particular application's active session is not inspected. For Traffic not following new static route, the directly relevant action is: Create controlled new flows and inspect session reevaluation behavior before labeling the route change ineffective.
Restore or validate an appropriate private route via the authorized overlay zone before relying on internet fallback. This could apply to the separate issue Private route leak to internet default: A remote office sends traffic for a private datacenter prefix toward internet default because the overlay route was accidentally withdrawn. For Traffic not following new static route, the directly relevant action is: Create controlled new flows and inspect session reevaluation behavior before labeling the route change ineffective.
Update and validate the member gateway and underlying route to the current ISP next hop. This could apply to the separate issue Per-member gateway resolution: An ISP changes the upstream router address on a static-address WAN, but the SD-WAN member retains the old gateway and reports intermittent traffic loss. For Traffic not following new static route, the directly relevant action is: Create controlled new flows and inspect session reevaluation behavior before labeling the route change ineffective.
For this situation, a reviewer needs acceptance evidence. An administrator fixes a default route and expects an established video call to move immediately, but the session continues on its original member. Which result most directly demonstrates success?
New sessions honor the corrected route while ongoing connections follow documented stateful behavior. This is the directly relevant check for Traffic not following new static route. It confirms the required step: Create controlled new flows and inspect session reevaluation behavior before labeling the route change ineffective. The operating principle is: Session handling can retain prior forwarding decisions until reevaluation or termination conditions occur.
ARP or neighbor discovery resolves the correct gateway and new traffic uses the member successfully. This would validate a different scenario, Per-member gateway resolution, where An ISP changes the upstream router address on a static-address WAN, but the SD-WAN member retains the old gateway and reports intermittent traffic loss. The current case needs evidence for Traffic not following new static route.
Destination lookup selects the intended private tunnel and no private data is emitted on public underlays. This would validate a different scenario, Private route leak to internet default, where A remote office sends traffic for a private datacenter prefix toward internet default because the overlay route was accidentally withdrawn. The current case needs evidence for Traffic not following new static route.
The actual source/destination session shows which service and outbound interface the firewall selected. This would validate a different scenario, Traffic session table identifies selected route, where An operator claims SD-WAN selected the wrong link based only on aggregate interface bandwidth, but a particular application's active session is not inspected. The current case needs evidence for Traffic not following new static route.
A network administrator must explain the underlying control. An administrator fixes a default route and expects an established video call to move immediately, but the session continues on its original member. Which statement is correct?
Session handling can retain prior forwarding decisions until reevaluation or termination conditions occur. This explains Traffic not following new static route in the given environment. The implementation decision is: Create controlled new flows and inspect session reevaluation behavior before labeling the route change ineffective. Confirm it with: New sessions honor the corrected route while ongoing connections follow documented stateful behavior.
Routing determines reachable destinations before SD-WAN rules choose among qualified member paths. That concept concerns Default static route to SD-WAN zone, not the mechanism needed for Traffic not following new static route. The relevant principle is: Session handling can retain prior forwarding decisions until reevaluation or termination conditions occur.
Specific private prefixes should direct private application traffic to the correct overlay next hop. That concept concerns Private route leak to internet default, not the mechanism needed for Traffic not following new static route. The relevant principle is: Session handling can retain prior forwarding decisions until reevaluation or termination conditions occur.
Session records contain forwarding state more specific than aggregate link utilization widgets. That concept concerns Traffic session table identifies selected route, not the mechanism needed for Traffic not following new static route. The relevant principle is: Session handling can retain prior forwarding decisions until reevaluation or termination conditions occur.
An incident team needs to isolate the root cause. An administrator fixes a default route and expects an established video call to move immediately, but the session continues on its original member. Which investigation should be prioritized?
Inspect session flags, route change, service counters and new-session selection. This inspection targets Traffic not following new static route rather than a different configuration issue. The corrective action is: Create controlled new flows and inspect session reevaluation behavior before labeling the route change ineffective. Expected evidence: New sessions honor the corrected route while ongoing connections follow documented stateful behavior.
Inspect interface addressing, ARP, member gateway and route lookup. This is useful when diagnosing Per-member gateway resolution. Instead, inspect session flags, route change, service counters and new-session selection.
Inspect route table, SD-WAN zone route, member gateways and flow egress. This is useful when diagnosing Default static route to SD-WAN zone. Instead, inspect session flags, route change, service counters and new-session selection.
Inspect `diagnose sys session list`, SD-WAN service status and relevant traffic logs for the flow. This is useful when diagnosing Traffic session table identifies selected route. Instead, inspect session flags, route change, service counters and new-session selection.
A network engineer faces the following FortiSASE or SD-WAN condition. A technical lead assumes the routing table's first equal-cost default nexthop always determines which ISP an App-ID based SD-WAN service uses. What should the engineer do?
Inspect both eligible routes and the matching SD-WAN service and SLA to determine actual selection. The routing table supplies destination reachability while SD-WAN service policy selects among relevant members. Expected evidence: A controlled application flow exits via the member selected by its SD-WAN strategy despite multiple eligible routes. Key limit: A service still needs routes that make the candidate members available.
Correct the route model and associated member gateways so both intended underlay paths are available for SD-WAN evaluation. This could apply to the separate issue ECMP route availability for two carriers: An SD-WAN branch has two healthy ISPs but only one eligible default route, so routing never considers the backup in selection. For Routing table versus SD-WAN best link, the directly relevant action is: Inspect both eligible routes and the matching SD-WAN service and SLA to determine actual selection.
Use FortiOS session and SD-WAN diagnostics to correlate the specific flow's route, rule and member. This could apply to the separate issue Traffic session table identifies selected route: An operator claims SD-WAN selected the wrong link based only on aggregate interface bandwidth, but a particular application's active session is not inspected. For Routing table versus SD-WAN best link, the directly relevant action is: Inspect both eligible routes and the matching SD-WAN service and SLA to determine actual selection.
Review route status and health-check withdrawal behavior so a failed route no longer wins forwarding. This could apply to the separate issue Route priority during primary circuit loss: A primary ISP fails and a secondary has a usable next hop, but the routing table retains a stale preferred route to the dead member. For Routing table versus SD-WAN best link, the directly relevant action is: Inspect both eligible routes and the matching SD-WAN service and SLA to determine actual selection.
A pilot is validating the implementation. A technical lead assumes the routing table's first equal-cost default nexthop always determines which ISP an App-ID based SD-WAN service uses. Which finding proves that the intended fix works?
A controlled application flow exits via the member selected by its SD-WAN strategy despite multiple eligible routes. This is the directly relevant check for Routing table versus SD-WAN best link. It confirms the required step: Inspect both eligible routes and the matching SD-WAN service and SLA to determine actual selection. The operating principle is: The routing table supplies destination reachability while SD-WAN service policy selects among relevant members.
Route diagnostics show usable candidate paths and tested failover reaches the backup carrier. This would validate a different scenario, ECMP route availability for two carriers, where An SD-WAN branch has two healthy ISPs but only one eligible default route, so routing never considers the backup in selection. The current case needs evidence for Routing table versus SD-WAN best link.
The actual source/destination session shows which service and outbound interface the firewall selected. This would validate a different scenario, Traffic session table identifies selected route, where An operator claims SD-WAN selected the wrong link based only on aggregate interface bandwidth, but a particular application's active session is not inspected. The current case needs evidence for Routing table versus SD-WAN best link.
In a controlled jitter test, new video flows move to the better quality member when allowed by policy. This would validate a different scenario, Static preference versus measured quality, where An engineer sets an SD-WAN video service to manual primary ISP preference but expects automatic selection of the lower-jitter link. The current case needs evidence for Routing table versus SD-WAN best link.
A technical lead asks why the recommended approach works. A technical lead assumes the routing table's first equal-cost default nexthop always determines which ISP an App-ID based SD-WAN service uses. Which mechanism is most relevant?
The routing table supplies destination reachability while SD-WAN service policy selects among relevant members. This explains Routing table versus SD-WAN best link in the given environment. The implementation decision is: Inspect both eligible routes and the matching SD-WAN service and SLA to determine actual selection. Confirm it with: A controlled application flow exits via the member selected by its SD-WAN strategy despite multiple eligible routes.
Session records contain forwarding state more specific than aggregate link utilization widgets. That concept concerns Traffic session table identifies selected route, not the mechanism needed for Routing table versus SD-WAN best link. The relevant principle is: The routing table supplies destination reachability while SD-WAN service policy selects among relevant members.
Dynamic route eligibility and SD-WAN member health cooperate to prevent forwarding into failed links. That concept concerns Route priority during primary circuit loss, not the mechanism needed for Routing table versus SD-WAN best link. The relevant principle is: The routing table supplies destination reachability while SD-WAN service policy selects among relevant members.
Routing and equal-cost eligibility provide candidate next hops on which SD-WAN service selection operates. That concept concerns ECMP route availability for two carriers, not the mechanism needed for Routing table versus SD-WAN best link. The relevant principle is: The routing table supplies destination reachability while SD-WAN service policy selects among relevant members.
Before changing production settings, an engineer reviews the symptoms. A technical lead assumes the routing table's first equal-cost default nexthop always determines which ISP an App-ID based SD-WAN service uses. Which evidence is most useful?
Review route lookup, SLA target, service match and active session egress. This inspection targets Routing table versus SD-WAN best link rather than a different configuration issue. The corrective action is: Inspect both eligible routes and the matching SD-WAN service and SLA to determine actual selection. Expected evidence: A controlled application flow exits via the member selected by its SD-WAN strategy despite multiple eligible routes.
Inspect route distance, inactive flags, health-check state and failover path. This is useful when diagnosing Route priority during primary circuit loss, but not the best first investigation here. Instead, review route lookup, sla target, service match and active session egress.
Inspect `diagnose sys session list`, SD-WAN service status and relevant traffic logs for the flow. This is useful when diagnosing Traffic session table identifies selected route, but not the best first investigation here. Instead, review route lookup, sla target, service match and active session egress.
Inspect IPv6 route table, neighbor discovery, zone policy and session path. This is useful when diagnosing SD-WAN IPv6 route eligibility, but not the best first investigation here. Instead, review route lookup, sla target, service match and active session egress.
Please check your mailbox for a message from support@examlabs.com and follow the directions.