NSE5_SSE_AD-7.6 Premium File
- 54 Questions & Answers
- Last Update: Nov 5, 2026
A pilot is validating the implementation. 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. Which finding proves that the intended fix works?
ARP or neighbor discovery resolves the correct gateway and new traffic uses the member successfully. This is the directly relevant check for Per-member gateway resolution. It confirms the required step: Update and validate the member gateway and underlying route to the current ISP next hop. The operating principle is: Each SD-WAN underlay member requires a reachable path through its associated 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 Per-member gateway resolution.
A controlled primary fault withdraws unusable routes and new sessions reach the backup ISP. This would validate a different scenario, Route priority during primary circuit loss, where 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. The current case needs evidence for Per-member gateway resolution.
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 Per-member gateway resolution.
A technical lead asks why the recommended approach works. 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. Which mechanism is most relevant?
Each SD-WAN underlay member requires a reachable path through its associated next hop. This explains Per-member gateway resolution in the given environment. The implementation decision is: Update and validate the member gateway and underlying route to the current ISP next hop. Confirm it with: ARP or neighbor discovery resolves the correct gateway and new traffic uses the member successfully.
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 Per-member gateway resolution. The relevant principle is: Each SD-WAN underlay member requires a reachable path through its associated next hop.
Source NAT and stateful session records can depend on the original egress interface and public address. That concept concerns Asymmetric SNAT sessions on WAN failover, not the mechanism needed for Per-member gateway resolution. The relevant principle is: Each SD-WAN underlay member requires a reachable path through its associated next hop.
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 Per-member gateway resolution. The relevant principle is: Each SD-WAN underlay member requires a reachable path through its associated next hop.
Before changing production settings, an engineer reviews the symptoms. 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. Which evidence is most useful?
Inspect interface addressing, ARP, member gateway and route lookup. This inspection targets Per-member gateway resolution rather than a different configuration issue. The corrective action is: Update and validate the member gateway and underlying route to the current ISP next hop. Expected evidence: ARP or neighbor discovery resolves the correct gateway and new traffic uses the member successfully.
Inspect session flags, route change, service counters and new-session selection. This is useful when diagnosing Traffic not following new static route. Instead, inspect interface addressing, arp, member gateway and route lookup.
Inspect route distance, inactive flags, health-check state and failover path. This is useful when diagnosing Route priority during primary circuit loss. Instead, inspect interface addressing, arp, member gateway and route lookup.
Inspect longest-prefix route, tunnel status, BGP/static prefix and packet trace. This is useful when diagnosing Private route leak to internet default. Instead, inspect interface addressing, arp, member gateway and route lookup.
A deployment review finds this gap. A growing chain has dozens of private subnets across SD-WAN VPN overlays and static routes are missing new sites. What is the most targeted next configuration step?
Use approved dynamic routing over healthy overlay tunnels and verify exchanged prefixes and route selection. Routing protocols can advertise private prefixes over overlay members while SD-WAN chooses available transports. Expected evidence: New approved branch prefixes appear in the routing table and private applications reach the intended remote site. Key limit: A BGP neighbor state alone does not prove the intended prefixes were accepted into forwarding.
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 Overlay route advertisement via BGP, the directly relevant action is: Use approved dynamic routing over healthy overlay tunnels and verify exchanged prefixes and route selection.
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 Overlay route advertisement via BGP, the directly relevant action is: Use approved dynamic routing over healthy overlay tunnels and verify exchanged prefixes and route selection.
Correct the supported probe or target route so reachability is measured through the intended overlay member. This could apply to the separate issue Overlay probe route conflicts with app data: 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. For Overlay route advertisement via BGP, the directly relevant action is: Use approved dynamic routing over healthy overlay tunnels and verify exchanged prefixes and route selection.
The recommended change has been applied. A growing chain has dozens of private subnets across SD-WAN VPN overlays and static routes are missing new sites. Which observation best verifies the intended outcome?
New approved branch prefixes appear in the routing table and private applications reach the intended remote site. This is the directly relevant check for Overlay route advertisement via BGP. It confirms the required step: Use approved dynamic routing over healthy overlay tunnels and verify exchanged prefixes and route selection. The operating principle is: Routing protocols can advertise private prefixes over overlay members while SD-WAN chooses available transports.
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 Overlay route advertisement via BGP.
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 Overlay route advertisement via BGP.
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 Overlay route advertisement via BGP.
An architect reviews the platform behavior behind this incident. A growing chain has dozens of private subnets across SD-WAN VPN overlays and static routes are missing new sites. Which explanation applies?
Routing protocols can advertise private prefixes over overlay members while SD-WAN chooses available transports. This explains Overlay route advertisement via BGP in the given environment. The implementation decision is: Use approved dynamic routing over healthy overlay tunnels and verify exchanged prefixes and route selection. Confirm it with: New approved branch prefixes appear in the routing table and private applications reach the intended remote site.
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 Overlay route advertisement via BGP. The relevant principle is: Routing protocols can advertise private prefixes over overlay members while SD-WAN chooses available transports.
BGP prefix receipt and route-to-next-hop resolution are separate requirements for forwarding. That concept concerns BGP route with unreachable recursive next hop, not the mechanism needed for Overlay route advertisement via BGP. The relevant principle is: Routing protocols can advertise private prefixes over overlay members while SD-WAN chooses available transports.
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 Overlay route advertisement via BGP. The relevant principle is: Routing protocols can advertise private prefixes over overlay members while SD-WAN chooses available transports.
A support analyst is collecting data for this scenario. A growing chain has dozens of private subnets across SD-WAN VPN overlays and static routes are missing new sites. Which diagnostic check is most targeted?
Inspect BGP adjacency, advertised routes, recursive next hops and overlay tunnel reachability. This inspection targets Overlay route advertisement via BGP rather than a different configuration issue. The corrective action is: Use approved dynamic routing over healthy overlay tunnels and verify exchanged prefixes and route selection. Expected evidence: New approved branch prefixes appear in the routing table and private applications reach the intended remote site.
Inspect session flags, route change, service counters and new-session selection. This is useful when diagnosing Traffic not following new static route. Instead, inspect bgp adjacency, advertised routes, recursive next hops and overlay tunnel reachability.
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 adjacency, advertised routes, recursive next hops and overlay tunnel reachability.
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 adjacency, advertised routes, recursive next hops and overlay tunnel reachability.
A Fortinet administrator must address this operational problem. An SD-WAN branch has two healthy ISPs but only one eligible default route, so routing never considers the backup in selection. Which response best resolves it?
Correct the route model and associated member gateways so both intended underlay paths are available for SD-WAN evaluation. Routing and equal-cost eligibility provide candidate next hops on which SD-WAN service selection operates. Expected evidence: Route diagnostics show usable candidate paths and tested failover reaches the backup carrier. Key limit: Equal-cost routing by itself does not ensure an application selects the best jitter path.
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 ECMP route availability for two carriers, the directly relevant action is: Correct the route model and associated member gateways so both intended underlay paths are available for SD-WAN evaluation.
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 ECMP route availability for two carriers, the directly relevant action is: Correct the route model and associated member gateways so both intended underlay paths are available for SD-WAN evaluation.
Configure the supported IPv6 member gateways, routes and policies for the authorized dual-stack traffic. This could apply to the separate issue SD-WAN IPv6 route eligibility: A dual-stack branch has working IPv4 SD-WAN routing but IPv6 web sessions time out because only IPv4 default paths were configured. For ECMP route availability for two carriers, the directly relevant action is: Correct the route model and associated member gateways so both intended underlay paths are available for SD-WAN evaluation.
For this situation, a reviewer needs acceptance evidence. An SD-WAN branch has two healthy ISPs but only one eligible default route, so routing never considers the backup in selection. Which result most directly demonstrates success?
Route diagnostics show usable candidate paths and tested failover reaches the backup carrier. This is the directly relevant check for ECMP route availability for two carriers. It confirms the required step: Correct the route model and associated member gateways so both intended underlay paths are available for SD-WAN evaluation. The operating principle is: Routing and equal-cost eligibility provide candidate next hops on which SD-WAN service selection operates.
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 ECMP route availability for two carriers.
Controlled IPv6 sessions route through the intended healthy member with valid next-hop resolution. This would validate a different scenario, SD-WAN IPv6 route eligibility, where A dual-stack branch has working IPv4 SD-WAN routing but IPv6 web sessions time out because only IPv4 default paths were configured. The current case needs evidence for ECMP route availability for two carriers.
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 ECMP route availability for two carriers.
A network administrator must explain the underlying control. An SD-WAN branch has two healthy ISPs but only one eligible default route, so routing never considers the backup in selection. Which statement is correct?
Routing and equal-cost eligibility provide candidate next hops on which SD-WAN service selection operates. This explains ECMP route availability for two carriers in the given environment. The implementation decision is: Correct the route model and associated member gateways so both intended underlay paths are available for SD-WAN evaluation. Confirm it with: Route diagnostics show usable candidate paths and tested failover reaches the backup carrier.
Locally originated management traffic requires valid routes independent of ordinary LAN-to-WAN policy rules. That concept concerns Zero-route after management network change, not the mechanism needed for ECMP route availability for two carriers. The relevant principle is: Routing and equal-cost eligibility provide candidate next hops on which SD-WAN service selection operates.
IPv4 and IPv6 use distinct routing and address-family configuration even on the same physical SD-WAN members. That concept concerns SD-WAN IPv6 route eligibility, not the mechanism needed for ECMP route availability for two carriers. The relevant principle is: Routing and equal-cost eligibility provide candidate next hops on which SD-WAN service selection operates.
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 ECMP route availability for two carriers. The relevant principle is: Routing and equal-cost eligibility provide candidate next hops on which SD-WAN service selection operates.
An incident team needs to isolate the root cause. An SD-WAN branch has two healthy ISPs but only one eligible default route, so routing never considers the backup in selection. Which investigation should be prioritized?
Inspect route distance, SD-WAN member gateway, ECMP eligibility and route table. This inspection targets ECMP route availability for two carriers rather than a different configuration issue. The corrective action is: Correct the route model and associated member gateways so both intended underlay paths are available for SD-WAN evaluation. Expected evidence: Route diagnostics show usable candidate paths and tested failover reaches the backup carrier.
Inspect longest-prefix route, tunnel status, BGP/static prefix and packet trace. This is useful when diagnosing Private route leak to internet default. Instead, inspect route distance, sd-wan member gateway, ecmp eligibility and route table.
Inspect IPv6 route table, neighbor discovery, zone policy and session path. This is useful when diagnosing SD-WAN IPv6 route eligibility. Instead, inspect route distance, sd-wan member gateway, ecmp eligibility and route table.
Inspect local-out source, routing table, DNS resolution and carrier gateway. This is useful when diagnosing Zero-route after management network change. Instead, inspect route distance, sd-wan member gateway, ecmp eligibility and route table.
Please check your mailbox for a message from support@examlabs.com and follow the directions.