NSE5_SSE_AD-7.6 Premium File
- 54 Questions & Answers
- Last Update: Nov 5, 2026
For this situation, a reviewer needs acceptance evidence. 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. Which result most directly demonstrates success?
A controlled primary fault withdraws unusable routes and new sessions reach the backup ISP. This is the directly relevant check for Route priority during primary circuit loss. It confirms the required step: Review route status and health-check withdrawal behavior so a failed route no longer wins forwarding. The operating principle is: Dynamic route eligibility and SD-WAN member health cooperate to prevent forwarding into failed links.
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 Route priority during primary circuit loss.
Management service packets resolve the intended next hop and reach their cloud management endpoint. This would validate a different scenario, Zero-route after management network change, where A remote FortiGate loses external connectivity after management-network renumbering, and the team creates a permissive firewall rule without checking routing. The current case needs evidence for Route priority during primary circuit loss.
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 Route priority during primary circuit loss.
A network administrator must explain the underlying control. 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. Which statement is correct?
Dynamic route eligibility and SD-WAN member health cooperate to prevent forwarding into failed links. This explains Route priority during primary circuit loss in the given environment. The implementation decision is: Review route status and health-check withdrawal behavior so a failed route no longer wins forwarding. Confirm it with: A controlled primary fault withdraws unusable routes and new sessions reach the backup ISP.
The routing table supplies destination reachability while SD-WAN service policy selects among relevant members. That concept concerns Routing table versus SD-WAN best link, not the mechanism needed for Route priority during primary circuit loss. The relevant principle is: Dynamic route eligibility and SD-WAN member health cooperate to prevent forwarding into failed links.
Session handling can retain prior forwarding decisions until reevaluation or termination conditions occur. That concept concerns Traffic not following new static route, not the mechanism needed for Route priority during primary circuit loss. The relevant principle is: Dynamic route eligibility and SD-WAN member health cooperate to prevent forwarding into failed links.
Each SD-WAN underlay member requires a reachable path through its associated next hop. That concept concerns Per-member gateway resolution, not the mechanism needed for Route priority during primary circuit loss. The relevant principle is: Dynamic route eligibility and SD-WAN member health cooperate to prevent forwarding into failed links.
An incident team needs to isolate the root cause. 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. Which investigation should be prioritized?
Inspect route distance, inactive flags, health-check state and failover path. This inspection targets Route priority during primary circuit loss rather than a different configuration issue. The corrective action is: Review route status and health-check withdrawal behavior so a failed route no longer wins forwarding. Expected evidence: A controlled primary fault withdraws unusable routes and new sessions reach the backup ISP.
Inspect interface addressing, ARP, member gateway and route lookup. This is useful when diagnosing Per-member gateway resolution. Instead, inspect route distance, inactive flags, health-check state and failover path.
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 route distance, inactive flags, health-check state and failover path.
Inspect BGP RIB, resolved next-hop path, tunnel route and forwarding table. This is useful when diagnosing BGP route with unreachable recursive next hop. Instead, inspect route distance, inactive flags, health-check state and failover path.
A network engineer faces the following FortiSASE or SD-WAN condition. After WAN failover, a long-lived outbound TCP session is still bound to a public IP from the failed carrier, causing the peer to reject traffic on the backup. What should the engineer do?
Analyze session persistence and SNAT handling for the changed egress, and use controlled reconnection where necessary. Source NAT and stateful session records can depend on the original egress interface and public address. Expected evidence: Fresh sessions on the backup have correct translated identity and complete return-path handshakes. Key limit: A physical carrier switch cannot guarantee preservation of old TCP sessions across public IP changes.
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 Asymmetric SNAT sessions on WAN failover, the directly relevant action is: Analyze session persistence and SNAT handling for the changed egress, and use controlled reconnection where necessary.
Reconcile the FortiOS policy-route and SD-WAN route processing order so the authorized path selection is unambiguous. This could apply to the separate issue SD-WAN policy route precedence: A specific policy route sends payroll traffic through an obsolete WAN even after administrators build a new SD-WAN rule for it. For Asymmetric SNAT sessions on WAN failover, the directly relevant action is: Analyze session persistence and SNAT handling for the changed egress, and use controlled reconnection where necessary.
Create controlled new flows and inspect session reevaluation behavior before labeling the route change ineffective. This could apply to the separate issue Traffic not following new static route: An administrator fixes a default route and expects an established video call to move immediately, but the session continues on its original member. For Asymmetric SNAT sessions on WAN failover, the directly relevant action is: Analyze session persistence and SNAT handling for the changed egress, and use controlled reconnection where necessary.
A pilot is validating the implementation. After WAN failover, a long-lived outbound TCP session is still bound to a public IP from the failed carrier, causing the peer to reject traffic on the backup. Which finding proves that the intended fix works?
Fresh sessions on the backup have correct translated identity and complete return-path handshakes. This is the directly relevant check for Asymmetric SNAT sessions on WAN failover. It confirms the required step: Analyze session persistence and SNAT handling for the changed egress, and use controlled reconnection where necessary. The operating principle is: Source NAT and stateful session records can depend on the original egress interface and public address.
New sessions honor the corrected route while ongoing connections follow documented stateful behavior. This would validate a different scenario, Traffic not following new static route, where An administrator fixes a default route and expects an established video call to move immediately, but the session continues on its original member. The current case needs evidence for Asymmetric SNAT sessions on WAN failover.
An authorized multi-request login remains associated with an acceptable member and public identity. This would validate a different scenario, Load balance same-source session persistence, where A branch load-balances web sessions across two equal links, but an SaaS provider rejects login changes when successive sessions use different public source addresses. The current case needs evidence for Asymmetric SNAT sessions on WAN failover.
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 Asymmetric SNAT sessions on WAN failover.
A technical lead asks why the recommended approach works. After WAN failover, a long-lived outbound TCP session is still bound to a public IP from the failed carrier, causing the peer to reject traffic on the backup. Which mechanism is most relevant?
Source NAT and stateful session records can depend on the original egress interface and public address. This explains Asymmetric SNAT sessions on WAN failover in the given environment. The implementation decision is: Analyze session persistence and SNAT handling for the changed egress, and use controlled reconnection where necessary. Confirm it with: Fresh sessions on the backup have correct translated identity and complete return-path handshakes.
FortiOS can apply a built-in implicit SD-WAN selection rule when no user-defined service matches. That concept concerns Implicit rule unexpectedly distributing traffic, not the mechanism needed for Asymmetric SNAT sessions on WAN failover. The relevant principle is: Source NAT and stateful session records can depend on the original egress interface and public address.
Session handling can retain prior forwarding decisions until reevaluation or termination conditions occur. That concept concerns Traffic not following new static route, not the mechanism needed for Asymmetric SNAT sessions on WAN failover. The relevant principle is: Source NAT and stateful session records can depend on the original egress interface and public address.
Policy-based routing can alter forwarding decisions before or alongside SD-WAN selection depending on configured route types. That concept concerns SD-WAN policy route precedence, not the mechanism needed for Asymmetric SNAT sessions on WAN failover. The relevant principle is: Source NAT and stateful session records can depend on the original egress interface and public address.
Before changing production settings, an engineer reviews the symptoms. After WAN failover, a long-lived outbound TCP session is still bound to a public IP from the failed carrier, causing the peer to reject traffic on the backup. Which evidence is most useful?
Inspect session tuple, original SNAT address, route change event and return packets. This inspection targets Asymmetric SNAT sessions on WAN failover rather than a different configuration issue. The corrective action is: Analyze session persistence and SNAT handling for the changed egress, and use controlled reconnection where necessary. Expected evidence: Fresh sessions on the backup have correct translated identity and complete return-path handshakes.
Inspect load-balance method, session table, NAT and client source patterns. This is useful when diagnosing Load balance same-source session persistence. Instead, inspect session tuple, original snat address, route change event and return packets.
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 tuple, original snat address, route change event and return packets.
Inspect policy route list, destination, source criteria, FIB and selected session path. This is useful when diagnosing SD-WAN policy route precedence. Instead, inspect session tuple, original snat address, route change event and return packets.
A deployment review finds this gap. 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. What is the most targeted next configuration step?
Use FortiOS session and SD-WAN diagnostics to correlate the specific flow's route, rule and member. Session records contain forwarding state more specific than aggregate link utilization widgets. Expected evidence: The actual source/destination session shows which service and outbound interface the firewall selected. Key limit: A snapshot of one existing session may not represent new-session path decisions after SLA changes.
Inspect both eligible routes and the matching SD-WAN service and SLA to determine actual selection. This could apply to the separate issue Routing table versus SD-WAN best link: 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. For Traffic session table identifies selected route, the directly relevant action is: Use FortiOS session and SD-WAN diagnostics to correlate the specific flow's route, rule and member.
Install a supported default static route through the intended SD-WAN zone or valid associated route model. This could apply to the separate issue Default static route to SD-WAN zone: A branch has two active SD-WAN members but the only default route still points directly at an old standalone WAN interface. For Traffic session table identifies selected route, the directly relevant action is: Use FortiOS session and SD-WAN diagnostics to correlate the specific flow's route, rule and member.
Create controlled new flows and inspect session reevaluation behavior before labeling the route change ineffective. This could apply to the separate issue Traffic not following new static route: An administrator fixes a default route and expects an established video call to move immediately, but the session continues on its original member. For Traffic session table identifies selected route, the directly relevant action is: Use FortiOS session and SD-WAN diagnostics to correlate the specific flow's route, rule and member.
The recommended change has been applied. 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. Which observation best verifies the intended outcome?
The actual source/destination session shows which service and outbound interface the firewall selected. This is the directly relevant check for Traffic session table identifies selected route. It confirms the required step: Use FortiOS session and SD-WAN diagnostics to correlate the specific flow's route, rule and member. The operating principle is: Session records contain forwarding state more specific than aggregate link utilization widgets.
New sessions honor the corrected route while ongoing connections follow documented stateful behavior. This would validate a different scenario, Traffic not following new static route, where An administrator fixes a default route and expects an established video call to move immediately, but the session continues on its original member. The current case needs evidence for Traffic session table identifies selected route.
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 Traffic session table identifies selected route.
A controlled application flow exits via the member selected by its SD-WAN strategy despite multiple eligible routes. This would validate a different scenario, Routing table versus SD-WAN best link, where 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. The current case needs evidence for Traffic session table identifies selected route.
An architect reviews the platform behavior behind this incident. 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. Which explanation applies?
Session records contain forwarding state more specific than aggregate link utilization widgets. This explains Traffic session table identifies selected route in the given environment. The implementation decision is: Use FortiOS session and SD-WAN diagnostics to correlate the specific flow's route, rule and member. Confirm it with: The actual source/destination session shows which service and outbound interface the firewall selected.
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 session table identifies selected route. The relevant principle is: Session records contain forwarding state more specific than aggregate link utilization widgets.
Session handling can retain prior forwarding decisions until reevaluation or termination conditions occur. That concept concerns Traffic not following new static route, not the mechanism needed for Traffic session table identifies selected route. The relevant principle is: Session records contain forwarding state more specific than aggregate link utilization widgets.
The routing table supplies destination reachability while SD-WAN service policy selects among relevant members. That concept concerns Routing table versus SD-WAN best link, not the mechanism needed for Traffic session table identifies selected route. The relevant principle is: Session records contain forwarding state more specific than aggregate link utilization widgets.
A support analyst is collecting data for this scenario. 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. Which diagnostic check is most targeted?
Inspect `diagnose sys session list`, SD-WAN service status and relevant traffic logs for the flow. This inspection targets Traffic session table identifies selected route rather than a different configuration issue. The corrective action is: Use FortiOS session and SD-WAN diagnostics to correlate the specific flow's route, rule and member. Expected evidence: The actual source/destination session shows which service and outbound interface the firewall selected.
Inspect session flags, route change, service counters and new-session selection. This is useful when diagnosing Traffic not following new static route. Instead, inspect `diagnose sys session list`, sd-wan service status and relevant traffic logs for the flow.
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 `diagnose sys session list`, sd-wan service status and relevant traffic logs for the flow.
Inspect BGP RIB, resolved next-hop path, tunnel route and forwarding table. This is useful when diagnosing BGP route with unreachable recursive next hop. Instead, inspect `diagnose sys session list`, sd-wan service status and relevant traffic logs for the flow.
Please check your mailbox for a message from support@examlabs.com and follow the directions.