Question 240
A Fortinet team is working on this situation: a mobile workforce needs direct access to a remote branch through an existing SD-WAN hub. It attempted: Use SPA-as-spoke topology with FortiSASE PoPs and ADVPN-aware FortiGate hub/spoke overlays. Expected evidence (Inspect dynamic shortcut operation to a resource behind the branch spoke) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Correct stickiness and shortcut eligibility rather than changing BGP router ID
- Correct service-rule configuration before relying on generic IPsec phase-1 up state
- Correct the mis-targeted overlay probe rather than increasing generic internet SLA tolerance
- Correct SPA hub IPsec or route advertisement before blaming local browser DNS
Explanation
Correct Answer
D:Correct SPA hub IPsec or route advertisement before blaming local browser DNS. The missing evidence (inspect dynamic shortcut operation to a resource behind the branch spoke) points to a problem with the implementation of use SPA-as-spoke topology with FortiSASE PoPs and ADVPN-aware FortiGate hub/spoke overlays. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Correct stickiness and shortcut eligibility rather than changing BGP router ID addresses a different operational issue: existing voice sessions should stay on their direct ADVPN tunnel while it continues to meet SLA. This situation calls for correct SPA hub IPsec or route advertisement before blaming local browser DNS because the missing result relates to inspect dynamic shortcut operation to a resource behind the branch spoke.
B:Correct service-rule configuration before relying on generic IPsec phase-1 up state addresses a different operational issue: an administrator wants to see whether a service rule is using shortcut SLA and stickiness. This situation calls for correct SPA hub IPsec or route advertisement before blaming local browser DNS because the missing result relates to inspect dynamic shortcut operation to a resource behind the branch spoke.
C:Correct the mis-targeted overlay probe rather than increasing generic internet SLA tolerance addresses a different operational issue: a shortcut remains unavailable despite green general internet probes. This situation calls for correct SPA hub IPsec or route advertisement before blaming local browser DNS because the missing result relates to inspect dynamic shortcut operation to a resource behind the branch spoke.
Question 241
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. An SD-WAN overlay requires ADVPN 2.0 path health for hubs in separate regions. Which design or implementation decision best meets the stated requirement?
- Assign a health check to each ADVPN-select-enabled hub zone
- Use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity
- Use SPA-as-spoke topology with FortiSASE PoPs and ADVPN-aware FortiGate hub/spoke overlays
- Enable ADVPN 2.0 edge discovery and path-management behavior
Explanation
Correct Answer
A:Assign a health check to each ADVPN-select-enabled hub zone. This addresses the stated requirement: an SD-WAN overlay requires ADVPN 2.0 path health for hubs in separate regions. The deployment must satisfy the accompanying requirement (Ensure each tunnel member and hub probe target are reachable); the engineer can then validate the result by performing this check: inspect the health-check status assigned to both hub zones.
Incorrect Answers
B:Use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity is a legitimate choice for another type of situation: remote spoke traffic hairpins through a hub while both spokes have a viable direct path. The alternative design first requires the team to ensure ADVPN-compatible spokes and overlay underlays are configured, but it does not directly implement the specified requirement to assign a health check to each ADVPN-select-enabled hub zone.
C:Use SPA-as-spoke topology with FortiSASE PoPs and ADVPN-aware FortiGate hub/spoke overlays is a legitimate choice for another type of situation: a mobile workforce needs direct access to a remote branch through an existing SD-WAN hub. The alternative design first requires the team to ensure the FortiSASE POP-to-hub IPsec/BGP connectivity is established, but it does not directly implement the specified requirement to assign a health check to each ADVPN-select-enabled hub zone.
D:Enable ADVPN 2.0 edge discovery and path-management behavior is a legitimate choice for another type of situation: an SD-WAN deployment wants spokes to consider their respective WAN link quality during shortcut selection. The alternative design first requires the team to ensure spokes exchange underlay link information including quality, cost and transport group, but it does not directly implement the specified requirement to assign a health check to each ADVPN-select-enabled hub zone.
Question 242
In a deployment where an SD-WAN overlay requires ADVPN 2.0 path health for hubs in separate regions, the team plans to: Assign a health check to each ADVPN-select-enabled hub zone. Which condition must be established for the chosen implementation to work as described?
- Ensure the relevant SD-WAN service rule is configured with shortcut awareness
- Ensure ADVPN-compatible spokes and overlay underlays are configured
- Ensure spokes exchange underlay link information including quality, cost and transport group
- Ensure each tunnel member and hub probe target are reachable
Explanation
Correct Answer
D:Ensure each tunnel member and hub probe target are reachable. This is the enabling condition for assign a health check to each ADVPN-select-enabled hub zone. Without that prerequisite, the expected operational evidence may not appear: inspect the health-check status assigned to both hub zones. the documented recovery path is to correct the selected health check or missing member mapping before debugging endpoint posture.
Incorrect Answers
A: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 assign a health check to each ADVPN-select-enabled hub zone, so that different condition would not establish the necessary setup for the stated deployment.
B:Ensure ADVPN-compatible spokes and overlay underlays are configured is relevant when the organization must use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity. Here the prerequisite instead concerns assign a health check to each ADVPN-select-enabled hub zone, so that different condition would not establish the necessary setup for the stated deployment.
C:Ensure spokes exchange underlay link information including quality, cost and transport group is relevant when the organization must enable ADVPN 2.0 edge discovery and path-management behavior. Here the prerequisite instead concerns assign a health check to each ADVPN-select-enabled hub zone, so that different condition would not establish the necessary setup for the stated deployment.
Question 243
A team implemented this choice for a customer: Assign a health check to each ADVPN-select-enabled hub zone. The requirement was: an SD-WAN overlay requires ADVPN 2.0 path health for hubs in separate regions. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Verify direct shortcut tunnel establishment after eligible traffic
- Inspect the health-check status assigned to both hub zones
- Inspect shortcut health and selected member after an SLA failure
- Verify the shortcut selection uses a transport group present at both endpoints
Explanation
Correct Answer
B:Inspect the health-check status assigned to both hub zones. It is the specific operational evidence for the requirement that an SD-WAN overlay requires ADVPN 2.0 path health for hubs in separate regions. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A:Verify direct shortcut tunnel establishment after eligible traffic would be meaningful evidence when attempting to use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity. It does not directly demonstrate whether inspect the health-check status assigned to both hub zones, 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 the health-check status assigned to both hub zones, which is the stated acceptance result for this Fortinet deployment.
D:Verify the shortcut selection uses a transport group present at both endpoints would be meaningful evidence when attempting to align the available underlay transport groups between source and destination spokes. It does not directly demonstrate whether inspect the health-check status assigned to both hub zones, which is the stated acceptance result for this Fortinet deployment.
Question 244
A Fortinet team is working on this situation: an SD-WAN overlay requires ADVPN 2.0 path health for hubs in separate regions. It attempted: Assign a health check to each ADVPN-select-enabled hub zone. Expected evidence (Inspect the health-check status assigned to both hub zones) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Repair shortcut discovery or overlay compatibility instead of permanently routing every flow through a hub
- Restore the carrier health or select another passing shortcut instead of forcing the bad session path
- Correct the selected health check or missing member mapping before debugging endpoint posture
- Correct service-rule configuration before relying on generic IPsec phase-1 up state
Explanation
Correct Answer
C:Correct the selected health check or missing member mapping before debugging endpoint posture. The missing evidence (inspect the health-check status assigned to both hub zones) points to a problem with the implementation of assign a health check to each ADVPN-select-enabled hub zone. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Repair shortcut discovery or overlay compatibility instead of permanently routing every flow through a hub addresses a different operational issue: remote spoke traffic hairpins through a hub while both spokes have a viable direct path. This situation calls for correct the selected health check or missing member mapping before debugging endpoint posture because the missing result relates to inspect the health-check status assigned to both hub zones.
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 correct the selected health check or missing member mapping before debugging endpoint posture because the missing result relates to inspect the health-check status assigned to both hub zones.
D:Correct service-rule configuration before relying on generic IPsec phase-1 up state addresses a different operational issue: an administrator wants to see whether a service rule is using shortcut SLA and stickiness. This situation calls for correct the selected health check or missing member mapping before debugging endpoint posture because the missing result relates to inspect the health-check status assigned to both hub zones.
Question 245
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. An operator enables spoke shortcuts but no path health information is available. Which design or implementation decision best meets the stated requirement?
- Configure the SD-WAN health check on the spoke overlay members
- Align the available underlay transport groups between source and destination spokes
- Use SLA-aware shortcut selection so failing paths are not retained by stickiness
- Treat shortcut health probes as monitoring, not user traffic that prevents idle teardown
Explanation
Correct Answer
A:Configure the SD-WAN health check on the spoke overlay members. This addresses the stated requirement: an operator enables spoke shortcuts but no path health information is available. The deployment must satisfy the accompanying requirement (Verify the probe server IP and selected tunnel members are correct); the engineer can then validate the result by performing this check: review per-member alive state, jitter and packet loss before selecting shortcuts.
Incorrect Answers
B:Align the available underlay transport groups between source and destination spokes is a legitimate choice for another type of situation: a site fails to form a shortcut after receiving a peer address but no matching transport. The alternative design first requires the team to confirm peer link attributes can be exchanged through edge discovery, but it does not directly implement the specified requirement to configure the SD-WAN health check on the spoke overlay members.
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 configure the SD-WAN health check on the spoke overlay members.
D:Treat shortcut health probes as monitoring, not user traffic that prevents idle teardown is a legitimate choice for another type of situation: a SOC analyst sees shortcut ICMP probes and assumes they keep an idle tunnel alive. The alternative design first requires the team to confirm the tunnel's activity and timeout behavior separately from health probes, but it does not directly implement the specified requirement to configure the SD-WAN health check on the spoke overlay members.
Question 246
In a deployment where an operator enables spoke shortcuts but no path health information is available, the team plans to: Configure the SD-WAN health check on the spoke overlay members. Which condition must be established for the chosen implementation to work as described?
- Confirm peer link attributes can be exchanged through edge discovery
- Verify the probe server IP and selected tunnel members are correct
- Ensure the shortcut was established and is included in the SLA-aware rule
- Confirm alternate healthy members exist for the affected service
Explanation
Correct Answer
B:Verify the probe server IP and selected tunnel members are correct. This is the enabling condition for configure the SD-WAN health check on the spoke overlay members. Without that prerequisite, the expected operational evidence may not appear: review per-member alive state, jitter and packet loss before selecting shortcuts. the documented recovery path is to repair absent or invalid probe targets before changing BGP advertised routes.
Incorrect Answers
A:Confirm peer link attributes can be exchanged through edge discovery is relevant when the organization must align the available underlay transport groups between source and destination spokes. Here the prerequisite instead concerns configure the SD-WAN health check on the spoke overlay members, so that different condition would not establish the necessary setup for the stated deployment.
C: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 configure the SD-WAN health check on the spoke overlay members, 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 configure the SD-WAN health check on the spoke overlay members, so that different condition would not establish the necessary setup for the stated deployment.
Question 247
A team implemented this choice for a customer: Configure the SD-WAN health check on the spoke overlay members. The requirement was: an operator enables spoke shortcuts but no path health information is available. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Inspect dynamic shortcut operation to a resource behind the branch spoke
- Verify the shortcut selection uses a transport group present at both endpoints
- Review per-member alive state, jitter and packet loss before selecting shortcuts
- Verify the session stays on a passing shortcut despite small quality shifts
Explanation
Correct Answer
C:Review per-member alive state, jitter and packet loss before selecting shortcuts. It is the specific operational evidence for the requirement that an operator enables spoke shortcuts but no path health information is available. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A:Inspect dynamic shortcut operation to a resource behind the branch spoke would be meaningful evidence when attempting to use SPA-as-spoke topology with FortiSASE PoPs and ADVPN-aware FortiGate hub/spoke overlays. It does not directly demonstrate whether review per-member alive state, jitter and packet loss before selecting shortcuts, which is the stated acceptance result for this Fortinet deployment.
B:Verify the shortcut selection uses a transport group present at both endpoints would be meaningful evidence when attempting to align the available underlay transport groups between source and destination spokes. It does not directly demonstrate whether review per-member alive state, jitter and packet loss before selecting shortcuts, which is the stated acceptance result for this Fortinet deployment.
D:Verify the session stays on a passing shortcut despite small quality shifts would be meaningful evidence when attempting to enable SD-WAN SLA stickiness for established shortcuts when appropriate. It does not directly demonstrate whether review per-member alive state, jitter and packet loss before selecting shortcuts, which is the stated acceptance result for this Fortinet deployment.
Question 248
A Fortinet team is working on this situation: an operator enables spoke shortcuts but no path health information is available. It attempted: Configure the SD-WAN health check on the spoke overlay members. Expected evidence (Review per-member alive state, jitter and packet loss before selecting shortcuts) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Correct SPA hub IPsec or route advertisement before blaming local browser DNS
- Correct stickiness and shortcut eligibility rather than changing BGP router ID
- 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
D:Repair absent or invalid probe targets before changing BGP advertised routes. The missing evidence (review per-member alive state, jitter and packet loss before selecting shortcuts) points to a problem with the implementation of configure the SD-WAN health check on the spoke overlay members. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Correct SPA hub IPsec or route advertisement before blaming local browser DNS addresses a different operational issue: a mobile workforce needs direct access to a remote branch through an existing SD-WAN hub. This situation calls for repair absent or invalid probe targets before changing BGP advertised routes because the missing result relates to review per-member alive state, jitter and packet loss before selecting shortcuts.
B:Correct stickiness and shortcut eligibility rather than changing BGP router ID addresses a different operational issue: existing voice sessions should stay on their direct ADVPN tunnel while it continues to meet SLA. This situation calls for repair absent or invalid probe targets before changing BGP advertised routes because the missing result relates to review per-member alive state, jitter and packet loss before selecting shortcuts.
C:Repair shortcut discovery or overlay compatibility instead of permanently routing every flow through a hub addresses a different operational issue: remote spoke traffic hairpins through a hub while both spokes have a viable direct path. This situation calls for repair absent or invalid probe targets before changing BGP advertised routes because the missing result relates to review per-member alive state, jitter and packet loss before selecting shortcuts.
Question 249
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. A deployment uses BGP on loopback and wants ADVPN shortcut selection. Which design or implementation decision best meets the stated requirement?
- Integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6
- Align the available underlay transport groups between source and destination spokes
- Use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity
- Enable ADVPN 2.0 edge discovery and path-management behavior
Explanation
Correct Answer
A:Integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6. This addresses the stated requirement: a deployment uses BGP on loopback and wants ADVPN shortcut selection. The deployment must satisfy the accompanying requirement (Ensure the common BGP loopback transport and overlay zone prerequisites exist); the engineer can then validate the result by performing this check: verify IPsec shortcut establishment without requiring a BGP peer on every shortcut.
Incorrect Answers
B:Align the available underlay transport groups between source and destination spokes is a legitimate choice for another type of situation: a site fails to form a shortcut after receiving a peer address but no matching transport. The alternative design first requires the team to confirm peer link attributes can be exchanged through edge discovery, but it does not directly implement the specified requirement to integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6.
C:Use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity is a legitimate choice for another type of situation: remote spoke traffic hairpins through a hub while both spokes have a viable direct path. The alternative design first requires the team to ensure ADVPN-compatible spokes and overlay underlays are configured, but it does not directly implement the specified requirement to integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6.
D:Enable ADVPN 2.0 edge discovery and path-management behavior is a legitimate choice for another type of situation: an SD-WAN deployment wants spokes to consider their respective WAN link quality during shortcut selection. The alternative design first requires the team to ensure spokes exchange underlay link information including quality, cost and transport group, but it does not directly implement the specified requirement to integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6.
Question 250
In a deployment where a deployment uses BGP on loopback and wants ADVPN shortcut selection, the team plans to: Integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6. 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 was established and is included in the SLA-aware rule
- Ensure the FortiSASE POP-to-hub IPsec/BGP connectivity is established
- Ensure the common BGP loopback transport and overlay zone prerequisites exist
Explanation
Correct Answer
D:Ensure the common BGP loopback transport and overlay zone prerequisites exist. This is the enabling condition for integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6. Without that prerequisite, the expected operational evidence may not appear: verify IPsec shortcut establishment without requiring a BGP peer on every shortcut. the documented recovery path is to fix IPsec zone selection rather than adding redundant per-shortcut BGP neighbors.
Incorrect Answers
A:Ensure spokes exchange underlay link information including quality, cost and transport group is relevant when the organization must enable ADVPN 2.0 edge discovery and path-management behavior. Here the prerequisite instead concerns integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6, 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 integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6, so that different condition would not establish the necessary setup for the stated deployment.
C:Ensure the FortiSASE POP-to-hub IPsec/BGP connectivity is established is relevant when the organization must use SPA-as-spoke topology with FortiSASE PoPs and ADVPN-aware FortiGate hub/spoke overlays. Here the prerequisite instead concerns integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6, 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