Question 270
In a deployment where an administrator wants to see whether a service rule is using shortcut SLA and stickiness, the team plans to: Inspect SD-WAN service diagnostics for shortcut and stickiness flags. 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 the common BGP loopback transport and overlay zone prerequisites exist
- Ensure IKE peers and the underlying WAN transport can reach one another
- Confirm the probe measures the overlay/hub rather than an unrelated public endpoint
Explanation
Correct Answer
A:Ensure the relevant SD-WAN service rule is configured with shortcut awareness. This is the enabling condition for inspect SD-WAN service diagnostics for shortcut and stickiness flags. Without that prerequisite, the expected operational evidence may not appear: verify service output shows the chosen shortcut-specific flags. the documented recovery path is to correct service-rule configuration before relying on generic IPsec phase-1 up state.
Incorrect Answers
B:Ensure the common BGP loopback transport and overlay zone prerequisites exist is relevant when the organization must integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6. Here the prerequisite instead concerns inspect SD-WAN service diagnostics for shortcut and stickiness flags, so that different condition would not establish the necessary setup for the stated deployment.
C:Ensure IKE peers and the underlying WAN transport can reach one another is relevant when the organization must establish the supporting IPsec overlay and reachable hub/spoke route exchange first. Here the prerequisite instead concerns inspect SD-WAN service diagnostics for shortcut and stickiness flags, 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 inspect SD-WAN service diagnostics for shortcut and stickiness flags, so that different condition would not establish the necessary setup for the stated deployment.
Question 271
A team implemented this choice for a customer: Inspect SD-WAN service diagnostics for shortcut and stickiness flags. The requirement was: an administrator wants to see whether a service rule is using shortcut SLA and stickiness. 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
- Inspect the health-check status assigned to both hub zones
- Verify IPsec shortcut establishment without requiring a BGP peer on every shortcut
- Verify service output shows the chosen shortcut-specific flags
Explanation
Correct Answer
D:Verify service output shows the chosen shortcut-specific flags. It is the specific operational evidence for the requirement that an administrator wants to see whether a service rule is using shortcut SLA and stickiness. 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 verify service output shows the chosen shortcut-specific flags, which is the stated acceptance result for this Fortinet deployment.
B:Inspect the health-check status assigned to both hub zones would be meaningful evidence when attempting to assign a health check to each ADVPN-select-enabled hub zone. It does not directly demonstrate whether verify service output shows the chosen shortcut-specific flags, which is the stated acceptance result for this Fortinet deployment.
C: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 verify service output shows the chosen shortcut-specific flags, which is the stated acceptance result for this Fortinet deployment.
Question 272
A Fortinet team is working on this situation: an administrator wants to see whether a service rule is using shortcut SLA and stickiness. It attempted: Inspect SD-WAN service diagnostics for shortcut and stickiness flags. Expected evidence (Verify service output shows the chosen shortcut-specific flags) 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
- Correct service-rule configuration before relying on generic IPsec phase-1 up state
- Correct the selected health check or missing member mapping before debugging endpoint posture
- Fix group compatibility before modifying unrelated firewall inspection policies
Explanation
Correct Answer
B:Correct service-rule configuration before relying on generic IPsec phase-1 up state. The missing evidence (verify service output shows the chosen shortcut-specific flags) points to a problem with the implementation of inspect SD-WAN service diagnostics for shortcut and stickiness flags. 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 service-rule configuration before relying on generic IPsec phase-1 up state because the missing result relates to verify service output shows the chosen shortcut-specific flags.
C:Correct the selected health check or missing member mapping before debugging endpoint posture addresses a different operational issue: an SD-WAN overlay requires ADVPN 2.0 path health for hubs in separate regions. This situation calls for correct service-rule configuration before relying on generic IPsec phase-1 up state because the missing result relates to verify service output shows the chosen shortcut-specific flags.
D:Fix group compatibility before modifying unrelated firewall inspection policies addresses a different operational issue: a site fails to form a shortcut after receiving a peer address but no matching transport. This situation calls for correct service-rule configuration before relying on generic IPsec phase-1 up state because the missing result relates to verify service output shows the chosen shortcut-specific flags.
Question 273
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. A spoke needs to distinguish health of a shortcut from the parent hub overlay. Which design or implementation decision best meets the stated requirement?
- Align the available underlay transport groups between source and destination spokes
- Examine the health check assigned specifically to the ADVPN overlay zone
- Use dynamic link monitoring for established ADVPN shortcuts
- Configure the SD-WAN health check on the spoke overlay members
Explanation
Correct Answer
C:Use dynamic link monitoring for established ADVPN shortcuts. This addresses the stated requirement: a spoke needs to distinguish health of a shortcut from the parent hub overlay. The deployment must satisfy the accompanying requirement (Ensure the shortcut can be probed using its gateway address); the engineer can then validate the result by performing this check: inspect the additional shortcut link-monitor entry after tunnel establishment.
Incorrect Answers
A: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 use dynamic link monitoring for established ADVPN shortcuts.
B: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 dynamic link monitoring for established ADVPN shortcuts.
D: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 use dynamic link monitoring for established ADVPN shortcuts.
Question 274
In a deployment where a spoke needs to distinguish health of a shortcut from the parent hub overlay, the team plans to: Use dynamic link monitoring for established ADVPN shortcuts. 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
- Ensure the common BGP loopback transport and overlay zone prerequisites exist
- Ensure each tunnel member and hub probe target are reachable
Explanation
Correct Answer
B:Ensure the shortcut can be probed using its gateway address. This is the enabling condition for use dynamic link monitoring for established ADVPN shortcuts. Without that prerequisite, the expected operational evidence may not appear: inspect the additional shortcut link-monitor entry after tunnel establishment. the documented recovery path is to repair dynamic monitor creation rather than treating parent overlay metrics as shortcut metrics.
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 use dynamic link monitoring for established ADVPN shortcuts, so that different condition would not establish the necessary setup for the stated deployment.
C:Ensure the common BGP loopback transport and overlay zone prerequisites exist is relevant when the organization must integrate ADVPN into the dynamic-BGP-on-loopback overlay as supported in FortiOS 7.6. Here the prerequisite instead concerns use dynamic link monitoring for established ADVPN shortcuts, so that different condition would not establish the necessary setup for the stated deployment.
D: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 dynamic link monitoring for established ADVPN shortcuts, so that different condition would not establish the necessary setup for the stated deployment.
Question 275
A team implemented this choice for a customer: Use dynamic link monitoring for established ADVPN shortcuts. The requirement was: a spoke needs to distinguish health of a shortcut from the parent hub overlay. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Inspect the additional shortcut link-monitor entry after tunnel establishment
- Inspect dynamic shortcut operation to a resource behind the branch spoke
- Verify IPsec shortcut establishment without requiring a BGP peer on every shortcut
- Review per-member alive state, jitter and packet loss before selecting shortcuts
Explanation
Correct Answer
A:Inspect the additional shortcut link-monitor entry after tunnel establishment. It is the specific operational evidence for the requirement that a spoke needs to distinguish health of a shortcut from the parent hub overlay. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
B: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 inspect the additional shortcut link-monitor entry after tunnel establishment, which is the stated acceptance result for this Fortinet deployment.
C: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 the additional shortcut link-monitor entry after tunnel establishment, which is the stated acceptance result for this Fortinet deployment.
D:Review per-member alive state, jitter and packet loss before selecting shortcuts would be meaningful evidence when attempting to configure the SD-WAN health check on the spoke overlay members. It does not directly demonstrate whether inspect the additional shortcut link-monitor entry after tunnel establishment, which is the stated acceptance result for this Fortinet deployment.
Question 276
A Fortinet team is working on this situation: a spoke needs to distinguish health of a shortcut from the parent hub overlay. It attempted: Use dynamic link monitoring for established ADVPN shortcuts. Expected evidence (Inspect the additional shortcut link-monitor entry after tunnel establishment) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Fix the missing second-zone ADVPN settings before concluding only one hub is supported
- Repair shortcut discovery or overlay compatibility instead of permanently routing every flow through a hub
- Correct mismatched transport groups or unavailable link-health information before forcing one shortcut
- Repair dynamic monitor creation rather than treating parent overlay metrics as shortcut metrics
Explanation
Correct Answer
D:Repair dynamic monitor creation rather than treating parent overlay metrics as shortcut metrics. The missing evidence (inspect the additional shortcut link-monitor entry after tunnel establishment) points to a problem with the implementation of use dynamic link monitoring for established ADVPN shortcuts. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Fix the missing second-zone ADVPN settings before concluding only one hub is supported addresses a different operational issue: a dual-hub network enables ADVPN on only one hub SD-WAN zone. This situation calls for repair dynamic monitor creation rather than treating parent overlay metrics as shortcut metrics because the missing result relates to inspect the additional shortcut link-monitor entry after tunnel establishment.
B: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 dynamic monitor creation rather than treating parent overlay metrics as shortcut metrics because the missing result relates to inspect the additional shortcut link-monitor entry after tunnel establishment.
C:Correct mismatched transport groups or unavailable link-health information before forcing one shortcut addresses a different operational issue: an SD-WAN deployment wants spokes to consider their respective WAN link quality during shortcut selection. This situation calls for repair dynamic monitor creation rather than treating parent overlay metrics as shortcut metrics because the missing result relates to inspect the additional shortcut link-monitor entry after tunnel establishment.
Question 277
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. A SOC analyst sees shortcut ICMP probes and assumes they keep an idle tunnel alive. Which design or implementation decision best meets the stated requirement?
- Use ADVPN shortcuts to create demand-driven direct spoke-to-spoke IPsec connectivity
- Align the available underlay transport groups between source and destination spokes
- Use SPA-as-spoke topology with FortiSASE PoPs and ADVPN-aware FortiGate hub/spoke overlays
- Treat shortcut health probes as monitoring, not user traffic that prevents idle teardown
Explanation
Correct Answer
D:Treat shortcut health probes as monitoring, not user traffic that prevents idle teardown. This addresses the stated requirement: a SOC analyst sees shortcut ICMP probes and assumes they keep an idle tunnel alive. The deployment must satisfy the accompanying requirement (Confirm the tunnel's activity and timeout behavior separately from health probes); the engineer can then validate the result by performing this check: compare user-session state with dynamic shortcut monitor results.
Incorrect Answers
A: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 treat shortcut health probes as monitoring, not user traffic that prevents idle teardown.
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 treat shortcut health probes as monitoring, not user traffic that prevents idle teardown.
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 treat shortcut health probes as monitoring, not user traffic that prevents idle teardown.
Question 278
In a deployment where a SOC analyst sees shortcut ICMP probes and assumes they keep an idle tunnel alive, the team plans to: Treat shortcut health probes as monitoring, not user traffic that prevents idle teardown. Which condition must be established for the chosen implementation to work as described?
- Confirm peer link attributes can be exchanged through edge discovery
- Ensure each tunnel member and hub probe target are reachable
- Confirm the tunnel's activity and timeout behavior separately from health probes
- Ensure the FortiSASE POP-to-hub IPsec/BGP connectivity is established
Explanation
Correct Answer
C:Confirm the tunnel's activity and timeout behavior separately from health probes. This is the enabling condition for treat shortcut health probes as monitoring, not user traffic that prevents idle teardown. Without that prerequisite, the expected operational evidence may not appear: compare user-session state with dynamic shortcut monitor results. the documented recovery path is to correct idle-time expectations instead of generating artificial keepalive user traffic.
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 treat shortcut health probes as monitoring, not user traffic that prevents idle teardown, so that different condition would not establish the necessary setup for the stated deployment.
B: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 treat shortcut health probes as monitoring, not user traffic that prevents idle teardown, so that different condition would not establish the necessary setup for the stated deployment.
D: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 treat shortcut health probes as monitoring, not user traffic that prevents idle teardown, so that different condition would not establish the necessary setup for the stated deployment.
Question 279
A team implemented this choice for a customer: Treat shortcut health probes as monitoring, not user traffic that prevents idle teardown. The requirement was: a SOC analyst sees shortcut ICMP probes and assumes they keep an idle tunnel alive. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Compare user-session state with dynamic shortcut monitor results
- Verify the shortcut selection uses a transport group present at both endpoints
- Inspect dynamic shortcut operation to a resource behind the branch spoke
- Verify IPsec shortcut establishment without requiring a BGP peer on every shortcut
Explanation
Correct Answer
A:Compare user-session state with dynamic shortcut monitor results. It is the specific operational evidence for the requirement that a SOC analyst sees shortcut ICMP probes and assumes they keep an idle tunnel alive. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
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 compare user-session state with dynamic shortcut monitor results, which is the stated acceptance result for this Fortinet deployment.
C: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 compare user-session state with dynamic shortcut monitor results, which is the stated acceptance result for this Fortinet deployment.
D: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 compare user-session state with dynamic shortcut monitor results, which is the stated acceptance result for this Fortinet deployment.
Question 280
A Fortinet team is working on this situation: a SOC analyst sees shortcut ICMP probes and assumes they keep an idle tunnel alive. It attempted: Treat shortcut health probes as monitoring, not user traffic that prevents idle teardown. Expected evidence (Compare user-session state with dynamic shortcut monitor results) 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
- Correct idle-time expectations instead of generating artificial keepalive user traffic
- Correct the selected health check or missing member mapping before debugging endpoint posture
- Correct the mis-targeted overlay probe rather than increasing generic internet SLA tolerance
Explanation
Correct Answer
B:Correct idle-time expectations instead of generating artificial keepalive user traffic. The missing evidence (compare user-session state with dynamic shortcut monitor results) points to a problem with the implementation of treat shortcut health probes as monitoring, not user traffic that prevents idle teardown. 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 idle-time expectations instead of generating artificial keepalive user traffic because the missing result relates to compare user-session state with dynamic shortcut monitor results.
C:Correct the selected health check or missing member mapping before debugging endpoint posture addresses a different operational issue: an SD-WAN overlay requires ADVPN 2.0 path health for hubs in separate regions. This situation calls for correct idle-time expectations instead of generating artificial keepalive user traffic because the missing result relates to compare user-session state with dynamic shortcut monitor results.
D: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 idle-time expectations instead of generating artificial keepalive user traffic because the missing result relates to compare user-session state with dynamic shortcut monitor results.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests