100% Latest & Updated Fortinet NSE5_SSE_AD-7.6 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 360
Select TWO options. Which mutually consistent response elements resolve the failure and demonstrate controlled recovery? Traffic to a private hub disappears after a tunnel becomes an SD-WAN member because the route to the IPsec peer recursively follows that tunnel.
- Parameterize the branch-specific next-hop and zone settings and validate a pilot before wider installation.
- Check peer reachability and tunnel SA separately from route lookup for private application prefixes.
- Preserve a valid underlay route to the peer gateway and keep protected destinations on the overlay route.
- Site-specific routes resolve correctly without reusing another branch's ISP gateway.
- Compare generated routes with each branch's actual gateway and test off-net reachability.
Explanation
Correct Answers
B:Check peer reachability and tunnel SA separately from route lookup for private application prefixes. This verifies the required result: the overlay stays established without routing its own underlay control traffic recursively.
C:The specific correction for the fault is: Preserve a valid underlay route to the peer gateway and keep protected destinations on the overlay route. The operational distinction is: Routing and next-hop reachability still govern viable forwarding even after an SD-WAN preference is configured. A defensible decision joins Preserve a valid underlay route to the peer gateway and keep protected destinations on the overlay route. with evidence Check peer reachability and tunnel SA separately from route lookup for private application prefixes. and the operating result The overlay stays established without routing its own underlay control traffic recursively.
Incorrect Answers
A:That action addresses a different fault: A FortiManager template applies identical default-route gateways to branches with different ISPs, producing inconsistent member reachability. Here, preserve a valid underlay route to the peer gateway and keep protected destinations on the overlay route.
D:This end state is associated with a different failure (A FortiManager template applies identical default-route gateways to branches with different ISPs, producing inconsistent member reachability.). It does not show the required case result The overlay stays established without routing its own underlay control traffic recursively. A defensible decision joins Preserve a valid underlay route to the peer gateway and keep protected destinations on the overlay route. with evidence Check peer reachability and tunnel SA separately from route lookup for private application prefixes. and the operating result The overlay stays established without routing its own underlay control traffic recursively.
E:This test measures another incident (A FortiManager template applies identical default-route gateways to branches with different ISPs, producing inconsistent member reachability.) and would not establish correction here. The missing evidence for the actual fault is Check peer reachability and tunnel SA separately from route lookup for private application prefixes. A defensible decision joins Preserve a valid underlay route to the peer gateway and keep protected destinations on the overlay route. with evidence Check peer reachability and tunnel SA separately from route lookup for private application prefixes. and the operating result The overlay stays established without routing its own underlay control traffic recursively.
Question 361
An administrator receives this incident: An administrator sees a preferred SD-WAN member healthy but new sessions reach an alternate path because the route lookup chooses a more-specific route. Which scoped correction is warranted?
- Check session state and supported reevaluation rules before forcing disruptive session changes.
- Verify health-check route-update settings and the intended administrative and member route behavior.
- Inspect longest-prefix route selection and align intended specific routes before changing rule preferences.
- Repair the necessary route or change candidate selection based on actual destination reachability.
Explanation
Correct Answer
C:Inspect longest-prefix route selection and align intended specific routes before changing rule preferences. The technical reason is that routing and next-hop reachability still govern viable forwarding even after an SD-WAN preference is configured. Scope the change to the reported fault without broadening access.
Incorrect Answers
A:That action addresses a different fault: During WAN failback, newly established sessions use a repaired primary while old sessions remain on backup, and the team calls this a routing failure. Here, inspect longest-prefix route selection and align intended specific routes before changing rule preferences.
B:That action addresses a different fault: A site uses static routes for two ISP members, but a health-check failure does not withdraw the broken member's route as the design expects. Here, inspect longest-prefix route selection and align intended specific routes before changing rule preferences.
D:That action addresses a different fault: An SD-WAN service rule names a link that is healthy, but no installed route reaches the destination through that member. Here, inspect longest-prefix route selection and align intended specific routes before changing rule preferences.
Question 362
Which targeted observation best distinguishes recovery from an unrelated success signal? An administrator sees a preferred SD-WAN member healthy but new sessions reach an alternate path because the route lookup chooses a more-specific route.
- Compare destination prefix lookup and egress for the SaaS test flow and internal app flows.
- Compare rule election with route-table and next-hop evidence for the specific destination.
- Inspect policy-route hits and route/member state for representative affected sessions.
- Compare destination route prefix lengths and resulting session egress for the target host.
Explanation
Correct Answer
D:This check measures the current failure rather than an unrelated one: Compare destination route prefix lengths and resulting session egress for the target host. It supports the required recovered state: Routing decisions honor the actual most-specific reachable route and service intent. An effective test must observe the condition Compare destination route prefix lengths and resulting session egress for the target host. rather than merely show that a configuration object exists.
Incorrect Answers
A:That test addresses another incident: A branch needs to reach a SaaS service directly but a broad internal route covers its destination through the private hub. The relevant verification here is compare destination route prefix lengths and resulting session egress for the target host.
B:That test addresses another incident: An SD-WAN service rule names a link that is healthy, but no installed route reaches the destination through that member. The relevant verification here is compare destination route prefix lengths and resulting session egress for the target host.
C:That test addresses another incident: A policy route forces one class of traffic through a provider that has become unhealthy; a generic SD-WAN rule appears unable to help. The relevant verification here is compare destination route prefix lengths and resulting session egress for the target host.
Question 363
For this issue, which end state should the service owner require? An administrator sees a preferred SD-WAN member healthy but new sessions reach an alternate path because the route lookup chooses a more-specific route.
- Default forwarding enters the intended SD-WAN selection process instead of bypassing it.
- Routing decisions honor the actual most-specific reachable route and service intent.
- Unhealthy paths are excluded from eligible forwarding when configured link-monitor policies require it.
- Private headquarters traffic uses available approved tunnels rather than an old member reference.
Explanation
Correct Answer
B:Routing decisions honor the actual most-specific reachable route and service intent. Verify it after inspect longest-prefix route selection and align intended specific routes before changing rule preferences.
Incorrect Answers
A:That outcome concerns a separate failure: A branch routes internet traffic into an SD-WAN zone but the only installed default route still points directly to old wan1. The required result here is: Routing decisions honor the actual most-specific reachable route and service intent.
C:That outcome concerns a separate failure: A site uses static routes for two ISP members, but a health-check failure does not withdraw the broken member's route as the design expects. The required result here is: Routing decisions honor the actual most-specific reachable route and service intent.
D:That outcome concerns a separate failure: Operations sees both overlay tunnels up but the selected route to headquarters still points at an obsolete tunnel name. The required result here is: Routing decisions honor the actual most-specific reachable route and service intent.
Question 364
Which mutually consistent response elements resolve the failure and demonstrate controlled recovery? An administrator sees a preferred SD-WAN member healthy but new sessions reach an alternate path because the route lookup chooses a more-specific route.
- Resolve overlapping addressing or route design explicitly rather than forcing a broad policy-route workaround.
- Review route preference and remove or adjust the obsolete static route under change control.
- Use supported learned-gateway routing for that link and review the member's gateway handling.
- Inspect longest-prefix route selection and align intended specific routes before changing rule preferences.
Explanation
Correct Answer
D:The specific correction for the fault is: Inspect longest-prefix route selection and align intended specific routes before changing rule preferences. The operational distinction is: Routing and next-hop reachability still govern viable forwarding even after an SD-WAN preference is configured. A defensible decision joins Inspect longest-prefix route selection and align intended specific routes before changing rule preferences. with evidence Compare destination route prefix lengths and resulting session egress for the target host. and the operating result Routing decisions honor the actual most-specific reachable route and service intent.
Incorrect Answers
A:That action addresses a different fault: A static route to a remote site uses the same address space as a local VLAN, causing route ambiguity during an SD-WAN migration. Here, inspect longest-prefix route selection and align intended specific routes before changing rule preferences.
B:That action addresses a different fault: A FortiGate receives a dynamic BGP private route but an old high-priority static entry masks it, causing a blackhole after migration. Here, inspect longest-prefix route selection and align intended specific routes before changing rule preferences.
C:That action addresses a different fault: A provider uses PPPoE and updates its gateway dynamically, but the SD-WAN route assumes a permanently fixed next hop. Here, inspect longest-prefix route selection and align intended specific routes before changing rule preferences.
Question 365
Select THREE options. An administrator receives this incident: A site uses static routes for two ISP members, but a health-check failure does not withdraw the broken member's route as the design expects. Which scoped correction is warranted?
- Unhealthy paths are excluded from eligible forwarding when configured link-monitor policies require it.
- Inspect route installation before, during, and after a simulated member failure.
- Verify health-check route-update settings and the intended administrative and member route behavior.
- Inspect prefix matching, zone and egress for a partner subnet test connection.
- Partner traffic follows the approved route rather than the unintended guest internet path.
- Correct the erroneous partner-prefix route and preserve any necessary authorized overlay route.
Explanation
Correct Answers
A:The intended recovery condition is: Unhealthy paths are excluded from eligible forwarding when configured link-monitor policies require it. It follows only after the control Verify health-check route-update settings and the intended administrative and member route behavior. is applied and validated. The change must repair the fault in A site uses static routes for two ISP members, but a health-check failure does not withdraw the broken member's route as the design expects. and must not introduce a broader access exception.
B:This check measures the current failure rather than an unrelated one: Inspect route installation before, during, and after a simulated member failure. It supports the required recovered state: Unhealthy paths are excluded from eligible forwarding when configured link-monitor policies require it. The change must repair the fault in A site uses static routes for two ISP members, but a health-check failure does not withdraw the broken member's route as the design expects. and must not introduce a broader access exception.
C:Verify health-check route-update settings and the intended administrative and member route behavior. The technical reason is that routing and next-hop reachability still govern viable forwarding even after an SD-WAN preference is configured. Scope the change to the reported fault without broadening access.
Incorrect Answers
D:This test measures another incident (A route for a partner subnet is accidentally more specific than the general datacenter route and points at a guest internet zone.) and would not establish correction here. The missing evidence for the actual fault is Inspect route installation before, during, and after a simulated member failure. The change must repair the fault in A site uses static routes for two ISP members, but a health-check failure does not withdraw the broken member's route as the design expects. and must not introduce a broader access exception.
E:This end state is associated with a different failure (A route for a partner subnet is accidentally more specific than the general datacenter route and points at a guest internet zone.). It does not show the required case result Unhealthy paths are excluded from eligible forwarding when configured link-monitor policies require it. The change must repair the fault in A site uses static routes for two ISP members, but a health-check failure does not withdraw the broken member's route as the design expects. and must not introduce a broader access exception.
F:That action addresses a different fault: A route for a partner subnet is accidentally more specific than the general datacenter route and points at a guest internet zone. Here, verify health-check route-update settings and the intended administrative and member route behavior.
Question 366
Which targeted observation best distinguishes recovery from an unrelated success signal? A site uses static routes for two ISP members, but a health-check failure does not withdraw the broken member's route as the design expects.
- Trace monitor probes separately from user data flow and inspect per-member health results.
- Compare route-table entries, firewall matches, and selected member for authorized internet sessions.
- Capture route lookup, policy-route match and SD-WAN decision for the test packet.
- Inspect route installation before, during, and after a simulated member failure.
Explanation
Correct Answer
D:This check measures the current failure rather than an unrelated one: Inspect route installation before, during, and after a simulated member failure. It supports the required recovered state: Unhealthy paths are excluded from eligible forwarding when configured link-monitor policies require it. An effective test must observe the condition Inspect route installation before, during, and after a simulated member failure. rather than merely show that a configuration object exists.
Incorrect Answers
A:That test addresses another incident: An operator changes the local-out monitoring server and unintentionally routes the FortiGate's own probe traffic through an unrelated SD-WAN zone. The relevant verification here is inspect route installation before, during, and after a simulated member failure.
B:That test addresses another incident: An engineer assumes that an SD-WAN zone referenced in a firewall rule automatically installs an internet default route. The relevant verification here is inspect route installation before, during, and after a simulated member failure.
C:That test addresses another incident: A cloud application sometimes follows an unintended exit because route policy and SD-WAN steering were modified without reviewing their order of operations. The relevant verification here is inspect route installation before, during, and after a simulated member failure.
Question 367
For this issue, which end state should the service owner require? A site uses static routes for two ISP members, but a health-check failure does not withdraw the broken member's route as the design expects.
- Default forwarding enters the intended SD-WAN selection process instead of bypassing it.
- Unhealthy paths are excluded from eligible forwarding when configured link-monitor policies require it.
- Site-specific routes resolve correctly without reusing another branch's ISP gateway.
- Private headquarters traffic uses available approved tunnels rather than an old member reference.
Explanation
Correct Answer
B:Unhealthy paths are excluded from eligible forwarding when configured link-monitor policies require it. Verify it after verify health-check route-update settings and the intended administrative and member route behavior.
Incorrect Answers
A:That outcome concerns a separate failure: A branch routes internet traffic into an SD-WAN zone but the only installed default route still points directly to old wan1. The required result here is: Unhealthy paths are excluded from eligible forwarding when configured link-monitor policies require it.
C:That outcome concerns a separate failure: A FortiManager template applies identical default-route gateways to branches with different ISPs, producing inconsistent member reachability. The required result here is: Unhealthy paths are excluded from eligible forwarding when configured link-monitor policies require it.
D:That outcome concerns a separate failure: Operations sees both overlay tunnels up but the selected route to headquarters still points at an obsolete tunnel name. The required result here is: Unhealthy paths are excluded from eligible forwarding when configured link-monitor policies require it.
Question 368
Which mutually consistent response elements resolve the failure and demonstrate controlled recovery? A site uses static routes for two ISP members, but a health-check failure does not withdraw the broken member's route as the design expects.
- Analyze the actual route and policy-route lookup sequence for the affected flow before changing rules.
- Resolve overlapping addressing or route design explicitly rather than forcing a broad policy-route workaround.
- Verify health-check route-update settings and the intended administrative and member route behavior.
- Parameterize the branch-specific next-hop and zone settings and validate a pilot before wider installation.
Explanation
Correct Answer
C:The specific correction for the fault is: Verify health-check route-update settings and the intended administrative and member route behavior. The operational distinction is: Routing and next-hop reachability still govern viable forwarding even after an SD-WAN preference is configured. A defensible decision joins Verify health-check route-update settings and the intended administrative and member route behavior. with evidence Inspect route installation before, during, and after a simulated member failure. and the operating result Unhealthy paths are excluded from eligible forwarding when configured link-monitor policies require it.
Incorrect Answers
A:That action addresses a different fault: A cloud application sometimes follows an unintended exit because route policy and SD-WAN steering were modified without reviewing their order of operations. Here, verify health-check route-update settings and the intended administrative and member route behavior.
B:That action addresses a different fault: A static route to a remote site uses the same address space as a local VLAN, causing route ambiguity during an SD-WAN migration. Here, verify health-check route-update settings and the intended administrative and member route behavior.
D:That action addresses a different fault: A FortiManager template applies identical default-route gateways to branches with different ISPs, producing inconsistent member reachability. Here, verify health-check route-update settings and the intended administrative and member route behavior.
Question 369
An administrator receives this incident: A datacenter application route points to an SD-WAN zone containing public WAN interfaces rather than the private overlay tunnels. Which scoped correction is warranted?
- Align route availability with supported tunnel or health state and verify alternate-member behavior.
- Add the required route and confirm it is usable independently of the firewall's permission decision.
- Analyze the actual route and policy-route lookup sequence for the affected flow before changing rules.
- Target the appropriate overlay zone and validate next-hop reachability for the private prefix.
Explanation
Correct Answer
D:Target the appropriate overlay zone and validate next-hop reachability for the private prefix. The technical reason is that routing and next-hop reachability still govern viable forwarding even after an SD-WAN preference is configured. Scope the change to the reported fault without broadening access.
Incorrect Answers
A:This action is suited to a different fault: A tunnel overlay must reach a private prefix only when the remote peer is alive, but a persistent static route remains even when the tunnel is unusable. In this case the necessary change is Target the appropriate overlay zone and validate next-hop reachability for the private prefix. The alternative leaves the reported control defect unresolved. The change must repair the fault in A datacenter application route points to an SD-WAN zone containing public WAN interfaces rather than the private overlay tunnels. and must not introduce a broader access exception.
B:That action addresses a different fault: An engineer assumes that an SD-WAN zone referenced in a firewall rule automatically installs an internet default route. Here, target the appropriate overlay zone and validate next-hop reachability for the private prefix.
C:This action is suited to a different fault: A cloud application sometimes follows an unintended exit because route policy and SD-WAN steering were modified without reviewing their order of operations. In this case the necessary change is Target the appropriate overlay zone and validate next-hop reachability for the private prefix. The alternative leaves the reported control defect unresolved. The change must repair the fault in A datacenter application route points to an SD-WAN zone containing public WAN interfaces rather than the private overlay tunnels. and must not introduce a broader access exception.
Question 370
Select TWO options. Which targeted observation best distinguishes recovery from an unrelated success signal? A datacenter application route points to an SD-WAN zone containing public WAN interfaces rather than the private overlay tunnels.
- Update the affected route gateway or dynamic-gateway behavior and verify its adjacency.
- Target the appropriate overlay zone and validate next-hop reachability for the private prefix.
- Inspect route resolution, ARP/neighbor state and forwarding on the changed member.
- The new provider gateway supports actual off-net traffic without altering unaffected members.
- Trace private-prefix routing and packet forwarding under permitted test conditions.
Explanation
Correct Answers
B:The specific correction for the fault is: Target the appropriate overlay zone and validate next-hop reachability for the private prefix. The operational distinction is: Routing and next-hop reachability still govern viable forwarding even after an SD-WAN preference is configured. An effective test must observe the condition Trace private-prefix routing and packet forwarding under permitted test conditions. rather than merely show that a configuration object exists.
E:This check measures the current failure rather than an unrelated one: Trace private-prefix routing and packet forwarding under permitted test conditions. It supports the required recovered state: The datacenter destination uses an intended private path, not unrestricted internet breakout. An effective test must observe the condition Trace private-prefix routing and packet forwarding under permitted test conditions. rather than merely show that a configuration object exists.
Incorrect Answers
A:This action is suited to a different fault: The WAN team changes one provider gateway after a maintenance window but a member static route continues pointing to the old next hop. In this case the necessary change is Target the appropriate overlay zone and validate next-hop reachability for the private prefix. The alternative leaves the reported control defect unresolved. An effective test must observe the condition Trace private-prefix routing and packet forwarding under permitted test conditions. rather than merely show that a configuration object exists.
C:That test addresses another incident: The WAN team changes one provider gateway after a maintenance window but a member static route continues pointing to the old next hop. The relevant verification here is trace private-prefix routing and packet forwarding under permitted test conditions.
D:This end state is associated with a different failure (The WAN team changes one provider gateway after a maintenance window but a member static route continues pointing to the old next hop.). It does not show the required case result The datacenter destination uses an intended private path, not unrestricted internet breakout. An effective test must observe the condition Trace private-prefix routing and packet forwarding under permitted test conditions. rather than merely show that a configuration object exists.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests