Question 220
A Fortinet team is working on this situation: a branch loses a physical WAN but still sees BGP peering down despite a healthy overlay. It attempted: Diagnose transport to the BGP loopback address via surviving overlays. Expected evidence (Inspect route-to-loopback and tunnel state before resetting BGP) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Correct the route origin or tagging method before troubleshooting unrelated IPsec ciphers
- Repair missing BGP community signaling rather than adding one-off firewall address entries
- Split the zone assignment if one broad policy accidentally handles both trust classes
- Correct missing loopback transport reachability rather than repeatedly bouncing the neighbor
Explanation
Correct Answer
D:Correct missing loopback transport reachability rather than repeatedly bouncing the neighbor. The missing evidence (inspect route-to-loopback and tunnel state before resetting BGP) points to a problem with the implementation of diagnose transport to the BGP loopback address via surviving overlays. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Correct the route origin or tagging method before troubleshooting unrelated IPsec ciphers addresses a different operational issue: a team attempts to use BGP tags for static routes that have no community processing. This situation calls for correct missing loopback transport reachability rather than repeatedly bouncing the neighbor because the missing result relates to inspect route-to-loopback and tunnel state before resetting BGP.
B:Repair missing BGP community signaling rather than adding one-off firewall address entries addresses a different operational issue: a business adds a new private network prefix without changing SD-WAN policies. This situation calls for correct missing loopback transport reachability rather than repeatedly bouncing the neighbor because the missing result relates to inspect route-to-loopback and tunnel state before resetting BGP.
C:Split the zone assignment if one broad policy accidentally handles both trust classes addresses a different operational issue: an MPLS provider wants separate inspection for private WAN traffic and public broadband sessions. This situation calls for correct missing loopback transport reachability rather than repeatedly bouncing the neighbor because the missing result relates to inspect route-to-loopback and tunnel state before resetting BGP.
Question 221
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. Remote spoke traffic hairpins through a hub while both spokes have a viable direct path. Which design or implementation decision best meets the stated requirement?
- Examine the health check assigned specifically to the ADVPN overlay zone
- Enable and map ADVPN selection consistently to the intended hub zones
- Use SLA-aware shortcut selection so failing paths are not retained by stickiness
- Use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity
Explanation
Correct Answer
D:Use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity. This addresses the stated requirement: remote spoke traffic hairpins through a hub while both spokes have a viable direct path. The deployment must satisfy the accompanying requirement (Ensure ADVPN-compatible spokes and overlay underlays are configured); the engineer can then validate the result by performing this check: verify direct shortcut tunnel establishment after eligible traffic.
Incorrect Answers
A:Examine the health check assigned specifically to the ADVPN overlay zone is a legitimate choice for another type of situation: a shortcut remains unavailable despite green general internet probes. The alternative design first requires the team to confirm the probe measures the overlay/hub rather than an unrelated public endpoint, but it does not directly implement the specified requirement to use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity.
B:Enable and map ADVPN selection consistently to the intended hub zones is a legitimate choice for another type of situation: a dual-hub network enables ADVPN on only one hub SD-WAN zone. The alternative design first requires the team to confirm each participating hub zone has appropriate health checking, but it does not directly implement the specified requirement to use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity.
C:Use SLA-aware shortcut selection so failing paths are not retained by stickiness is a legitimate choice for another type of situation: a shortcut's SLA degrades below acceptance and traffic must avoid it. The alternative design first requires the team to confirm alternate healthy members exist for the affected service, but it does not directly implement the specified requirement to use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity.
Question 222
In a deployment where remote spoke traffic hairpins through a hub while both spokes have a viable direct path, the team plans to: Use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity. Which condition must be established for the chosen implementation to work as described?
- Ensure each tunnel member and hub probe target are reachable
- Ensure ADVPN-compatible spokes and overlay underlays are configured
- Confirm each participating hub zone has appropriate health checking
- Confirm the probe measures the overlay/hub rather than an unrelated public endpoint
Explanation
Correct Answer
B:Ensure ADVPN-compatible spokes and overlay underlays are configured. This is the enabling condition for use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity. Without that prerequisite, the expected operational evidence may not appear: verify direct shortcut tunnel establishment after eligible traffic. the documented recovery path is to repair shortcut discovery or overlay compatibility instead of permanently routing every flow through a hub.
Incorrect Answers
A:Ensure each tunnel member and hub probe target are reachable is relevant when the organization must assign a health check to each ADVPN-select-enabled hub zone. Here the prerequisite instead concerns use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity, so that different condition would not establish the necessary setup for the stated deployment.
C:Confirm each participating hub zone has appropriate health checking is relevant when the organization must enable and map ADVPN selection consistently to the intended hub zones. Here the prerequisite instead concerns use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity, so that different condition would not establish the necessary setup for the stated deployment.
D:Confirm the probe measures the overlay/hub rather than an unrelated public endpoint is relevant when the organization must examine the health check assigned specifically to the ADVPN overlay zone. Here the prerequisite instead concerns use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity, so that different condition would not establish the necessary setup for the stated deployment.
Question 223
A team implemented this choice for a customer: Use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity. The requirement was: remote spoke traffic hairpins through a hub while both spokes have a viable direct path. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Verify direct shortcut tunnel establishment after eligible traffic
- Inspect shortcut health and selected member after an SLA failure
- Verify shortcut choice can use eligible overlay paths through either hub
- Inspect the additional shortcut link-monitor entry after tunnel establishment
Explanation
Correct Answer
A:Verify direct shortcut tunnel establishment after eligible traffic. It is the specific operational evidence for the requirement that remote spoke traffic hairpins through a hub while both spokes have a viable direct path. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
B:Inspect shortcut health and selected member after an SLA failure would be meaningful evidence when attempting to use SLA-aware shortcut selection so failing paths are not retained by stickiness. It does not directly demonstrate whether verify direct shortcut tunnel establishment after eligible traffic, which is the stated acceptance result for this Fortinet deployment.
C:Verify shortcut choice can use eligible overlay paths through either hub would be meaningful evidence when attempting to enable and map ADVPN selection consistently to the intended hub zones. It does not directly demonstrate whether verify direct shortcut tunnel establishment after eligible traffic, which is the stated acceptance result for this Fortinet deployment.
D:Inspect the additional shortcut link-monitor entry after tunnel establishment would be meaningful evidence when attempting to use dynamic link monitoring for established ADVPN shortcuts. It does not directly demonstrate whether verify direct shortcut tunnel establishment after eligible traffic, which is the stated acceptance result for this Fortinet deployment.
Question 224
A Fortinet team is working on this situation: remote spoke traffic hairpins through a hub while both spokes have a viable direct path. It attempted: Use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity. Expected evidence (Verify direct shortcut tunnel establishment after eligible traffic) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Correct idle-time expectations instead of generating artificial keepalive user traffic
- Restore the carrier health or select another passing shortcut instead of forcing the bad session path
- Repair shortcut discovery or overlay compatibility instead of permanently routing every flow through a hub
- Repair absent or invalid probe targets before changing BGP advertised routes
Explanation
Correct Answer
C:Repair shortcut discovery or overlay compatibility instead of permanently routing every flow through a hub. The missing evidence (verify direct shortcut tunnel establishment after eligible traffic) points to a problem with the implementation of use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Correct idle-time expectations instead of generating artificial keepalive user traffic addresses a different operational issue: a SOC analyst sees shortcut ICMP probes and assumes they keep an idle tunnel alive. This situation calls for repair shortcut discovery or overlay compatibility instead of permanently routing every flow through a hub because the missing result relates to verify direct shortcut tunnel establishment after eligible traffic.
B:Restore the carrier health or select another passing shortcut instead of forcing the bad session path addresses a different operational issue: a shortcut's SLA degrades below acceptance and traffic must avoid it. This situation calls for repair shortcut discovery or overlay compatibility instead of permanently routing every flow through a hub because the missing result relates to verify direct shortcut tunnel establishment after eligible traffic.
D:Repair absent or invalid probe targets before changing BGP advertised routes addresses a different operational issue: an operator enables spoke shortcuts but no path health information is available. This situation calls for repair shortcut discovery or overlay compatibility instead of permanently routing every flow through a hub because the missing result relates to verify direct shortcut tunnel establishment after eligible traffic.
Question 225
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. An SD-WAN deployment wants spokes to consider their respective WAN link quality during shortcut selection. Which design or implementation decision best meets the stated requirement?
- Configure the SD-WAN health check on the spoke overlay members
- Enable ADVPN 2.0 edge discovery and path-management behavior
- Assign a health check to each ADVPN-select-enabled hub zone
- Examine the health check assigned specifically to the ADVPN overlay zone
Explanation
Correct Answer
B:Enable ADVPN 2.0 edge discovery and path-management behavior. This addresses the stated requirement: an SD-WAN deployment wants spokes to consider their respective WAN link quality during shortcut selection. The deployment must satisfy the accompanying requirement (Ensure spokes exchange underlay link information including quality, cost and transport group); the engineer can then validate the result by performing this check: inspect selected shortcut transport and quality criteria at both spokes.
Incorrect Answers
A:Configure the SD-WAN health check on the spoke overlay members is a legitimate choice for another type of situation: an operator enables spoke shortcuts but no path health information is available. The alternative design first requires the team to verify the probe server IP and selected tunnel members are correct, but it does not directly implement the specified requirement to enable ADVPN 2.0 edge discovery and path-management behavior.
C:Assign a health check to each ADVPN-select-enabled hub zone is a legitimate choice for another type of situation: an SD-WAN overlay requires ADVPN 2.0 path health for hubs in separate regions. The alternative design first requires the team to ensure each tunnel member and hub probe target are reachable, but it does not directly implement the specified requirement to enable ADVPN 2.0 edge discovery and path-management behavior.
D:Examine the health check assigned specifically to the ADVPN overlay zone is a legitimate choice for another type of situation: a shortcut remains unavailable despite green general internet probes. The alternative design first requires the team to confirm the probe measures the overlay/hub rather than an unrelated public endpoint, but it does not directly implement the specified requirement to enable ADVPN 2.0 edge discovery and path-management behavior.
Question 226
In a deployment where an SD-WAN deployment wants spokes to consider their respective WAN link quality during shortcut selection, the team plans to: Enable ADVPN 2.0 edge discovery and path-management behavior. Which condition must be established for the chosen implementation to work as described?
- Ensure spokes exchange underlay link information including quality, cost and transport group
- Ensure the shortcut can be probed using its gateway address
- Confirm the probe measures the overlay/hub rather than an unrelated public endpoint
- Ensure the relevant SD-WAN service rule is configured with shortcut awareness
Explanation
Correct Answer
A:Ensure spokes exchange underlay link information including quality, cost and transport group. This is the enabling condition for enable ADVPN 2.0 edge discovery and path-management behavior. Without that prerequisite, the expected operational evidence may not appear: inspect selected shortcut transport and quality criteria at both spokes. the documented recovery path is to correct mismatched transport groups or unavailable link-health information before forcing one shortcut.
Incorrect Answers
B:Ensure the shortcut can be probed using its gateway address is relevant when the organization must use dynamic link monitoring for established ADVPN shortcuts. Here the prerequisite instead concerns enable ADVPN 2.0 edge discovery and path-management behavior, so that different condition would not establish the necessary setup for the stated deployment.
C:Confirm the probe measures the overlay/hub rather than an unrelated public endpoint is relevant when the organization must examine the health check assigned specifically to the ADVPN overlay zone. Here the prerequisite instead concerns enable ADVPN 2.0 edge discovery and path-management behavior, so that different condition would not establish the necessary setup for the stated deployment.
D:Ensure the relevant SD-WAN service rule is configured with shortcut awareness is relevant when the organization must inspect SD-WAN service diagnostics for shortcut and stickiness flags. Here the prerequisite instead concerns enable ADVPN 2.0 edge discovery and path-management behavior, so that different condition would not establish the necessary setup for the stated deployment.
Question 227
A team implemented this choice for a customer: Enable ADVPN 2.0 edge discovery and path-management behavior. The requirement was: an SD-WAN deployment wants spokes to consider their respective WAN link quality during shortcut selection. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Inspect overlay-specific SLA state and shortcut parameters
- Verify IPsec shortcut establishment without requiring a BGP peer on every shortcut
- Inspect shortcut health and selected member after an SLA failure
- Inspect selected shortcut transport and quality criteria at both spokes
Explanation
Correct Answer
D:Inspect selected shortcut transport and quality criteria at both spokes. It is the specific operational evidence for the requirement that an SD-WAN deployment wants spokes to consider their respective WAN link quality during shortcut selection. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A:Inspect overlay-specific SLA state and shortcut parameters would be meaningful evidence when attempting to examine the health check assigned specifically to the ADVPN overlay zone. It does not directly demonstrate whether inspect selected shortcut transport and quality criteria at both spokes, which is the stated acceptance result for this Fortinet deployment.
B:Verify IPsec shortcut establishment without requiring a BGP peer on every shortcut would be meaningful evidence when attempting to integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6. It does not directly demonstrate whether inspect selected shortcut transport and quality criteria at both spokes, which is the stated acceptance result for this Fortinet deployment.
C:Inspect shortcut health and selected member after an SLA failure would be meaningful evidence when attempting to use SLA-aware shortcut selection so failing paths are not retained by stickiness. It does not directly demonstrate whether inspect selected shortcut transport and quality criteria at both spokes, which is the stated acceptance result for this Fortinet deployment.
Question 228
A Fortinet team is working on this situation: an SD-WAN deployment wants spokes to consider their respective WAN link quality during shortcut selection. It attempted: Enable ADVPN 2.0 edge discovery and path-management behavior. Expected evidence (Inspect selected shortcut transport and quality criteria at both spokes) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Restore the carrier health or select another passing shortcut instead of forcing the bad session path
- Repair dynamic monitor creation rather than treating parent overlay metrics as shortcut metrics
- Correct mismatched transport groups or unavailable link-health information before forcing one shortcut
- Fix IPsec zone selection rather than adding redundant per-shortcut BGP neighbors
Explanation
Correct Answer
C:Correct mismatched transport groups or unavailable link-health information before forcing one shortcut. The missing evidence (inspect selected shortcut transport and quality criteria at both spokes) points to a problem with the implementation of enable ADVPN 2.0 edge discovery and path-management behavior. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Restore the carrier health or select another passing shortcut instead of forcing the bad session path addresses a different operational issue: a shortcut's SLA degrades below acceptance and traffic must avoid it. This situation calls for correct mismatched transport groups or unavailable link-health information before forcing one shortcut because the missing result relates to inspect selected shortcut transport and quality criteria at both spokes.
B:Repair dynamic monitor creation rather than treating parent overlay metrics as shortcut metrics addresses a different operational issue: a spoke needs to distinguish health of a shortcut from the parent hub overlay. This situation calls for correct mismatched transport groups or unavailable link-health information before forcing one shortcut because the missing result relates to inspect selected shortcut transport and quality criteria at both spokes.
D:Fix IPsec zone selection rather than adding redundant per-shortcut BGP neighbors addresses a different operational issue: a deployment uses BGP on loopback and wants ADVPN shortcut selection. This situation calls for correct mismatched transport groups or unavailable link-health information before forcing one shortcut because the missing result relates to inspect selected shortcut transport and quality criteria at both spokes.
Question 229
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. An engineer expects ADVPN shortcut formation without any available IPsec overlay. Which design or implementation decision best meets the stated requirement?
- Establish the supporting IPsec overlay and reachable hub/spoke route exchange first
- Enable SD-WAN SLA stickiness for established shortcuts when appropriate
- Use SLA-aware shortcut selection so failing paths are not retained by stickiness
- Enable and map ADVPN selection consistently to the intended hub zones
Explanation
Correct Answer
A:Establish the supporting IPsec overlay and reachable hub/spoke route exchange first. This addresses the stated requirement: an engineer expects ADVPN shortcut formation without any available IPsec overlay. The deployment must satisfy the accompanying requirement (Ensure IKE peers and the underlying WAN transport can reach one another); the engineer can then validate the result by performing this check: check overlay tunnel and exchange state before looking for shortcuts.
Incorrect Answers
B:Enable SD-WAN SLA stickiness for established shortcuts when appropriate is a legitimate choice for another type of situation: existing voice sessions should stay on their direct ADVPN tunnel while it continues to meet SLA. The alternative design first requires the team to ensure the shortcut was established and is included in the SLA-aware rule, but it does not directly implement the specified requirement to establish the supporting IPsec overlay and reachable hub/spoke route exchange first.
C:Use SLA-aware shortcut selection so failing paths are not retained by stickiness is a legitimate choice for another type of situation: a shortcut's SLA degrades below acceptance and traffic must avoid it. The alternative design first requires the team to confirm alternate healthy members exist for the affected service, but it does not directly implement the specified requirement to establish the supporting IPsec overlay and reachable hub/spoke route exchange first.
D:Enable and map ADVPN selection consistently to the intended hub zones is a legitimate choice for another type of situation: a dual-hub network enables ADVPN on only one hub SD-WAN zone. The alternative design first requires the team to confirm each participating hub zone has appropriate health checking, but it does not directly implement the specified requirement to establish the supporting IPsec overlay and reachable hub/spoke route exchange first.
Question 230
In a deployment where an engineer expects ADVPN shortcut formation without any available IPsec overlay, the team plans to: Establish the supporting IPsec overlay and reachable hub/spoke route exchange first. Which condition must be established for the chosen implementation to work as described?
- Ensure the shortcut can be probed using its gateway address
- Ensure the shortcut was established and is included in the SLA-aware rule
- Ensure IKE peers and the underlying WAN transport can reach one another
- Confirm alternate healthy members exist for the affected service
Explanation
Correct Answer
C:Ensure IKE peers and the underlying WAN transport can reach one another. This is the enabling condition for establish the supporting IPsec overlay and reachable hub/spoke route exchange first. Without that prerequisite, the expected operational evidence may not appear: check overlay tunnel and exchange state before looking for shortcuts. the documented recovery path is to restore the underlying IPsec overlay rather than adjusting the shortcut member priority.
Incorrect Answers
A:Ensure the shortcut can be probed using its gateway address is relevant when the organization must use dynamic link monitoring for established ADVPN shortcuts. Here the prerequisite instead concerns establish the supporting IPsec overlay and reachable hub/spoke route exchange first, so that different condition would not establish the necessary setup for the stated deployment.
B:Ensure the shortcut was established and is included in the SLA-aware rule is relevant when the organization must enable SD-WAN SLA stickiness for established shortcuts when appropriate. Here the prerequisite instead concerns establish the supporting IPsec overlay and reachable hub/spoke route exchange first, so that different condition would not establish the necessary setup for the stated deployment.
D:Confirm alternate healthy members exist for the affected service is relevant when the organization must use SLA-aware shortcut selection so failing paths are not retained by stickiness. Here the prerequisite instead concerns establish the supporting IPsec overlay and reachable hub/spoke route exchange first, so that different condition would not establish the necessary setup for the stated deployment.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests