Fortinet NSE7_SSE_AR-26 Practice Test 38
Question 370
For an original Fortinet NSE 7 FortiSASE 26 Architect educational scenario, consider: An enterprise expects one loopback BGP peer to survive tunnel changes yet the underlying transport routes for the loopbacks are tied to the failed member. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Check loopback source, recursive next-hop, overlay routes, BGP TTL or multihop support and neighbor convergence under one tunnel failure.
- Change: Build supported loopback-based BGP peer reachability across overlay paths with correct source and route distribution.
- Check: Compare existing overlays, security boundaries, app destination placement, failover paths and FortiSASE client traffic traces.
- Create loopback addresses and assume BGP finds them across IPsec automatically without any route or source configuration.
- Change: Reconcile routing and policy-route precedence with SD-WAN steering, ensuring eligible next hops and policy context for the intended flow.
Explanation
Correct Answer
A:Loopback peering decouples neighbor identity from a physical tunnel, but only if loopback routes remain resolvable over working overlays. Acceptance: Stable BGP peering or controlled reconvergence survives eligible transport changes without exposing control-plane addresses externally.
B:Loopback peering decouples neighbor identity from a physical tunnel, but only if loopback routes remain resolvable over working overlays. Evidence: Check loopback source, recursive next-hop, overlay routes, BGP TTL or multihop support and neighbor convergence under one tunnel failure.
Incorrect Answers
C:Check: Compare existing overlays, security boundaries, app destination placement, failover paths and FortiSASE client traffic traces. Loopback peering decouples neighbor identity from a physical tunnel, but only if loopback routes remain resolvable over working overlays.
D:For this select two assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it. Loopback peering decouples neighbor identity from a physical tunnel, but only if loopback routes remain resolvable over working overlays.
E:This option addresses a different Fortinet NSE 7 secure networking topic (SD-WAN route lookup versus policy route) rather than the documented BGP on loopback overlay design decision.
Question 371
A Fortinet NSE 7 architect is reviewing this FortiSASE environment scenario: A long-lived ERP session repeatedly alternates between equally healthy tunnels after minor performance variations, breaking stateful middlebox expectations. An unsafe shortcut would be: Pin every session forever to its first tunnel even when the tunnel fails security or reachability checks. What should the FortiSASE administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Configure supported overlay path persistence and health-driven switching to balance stateful continuity against real link failure.
- Distribute the appropriate approved FortiClient installer and enrollment configuration per device and user population, then validate first connection.
- Pin every session forever to its first tunnel even when the tunnel fails security or reachability checks.
- Validate member-specific gateway and static route semantics, and align zone routes with supported SD-WAN topology and security policy.
Explanation
Correct Answer
A:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
Incorrect Answers
B:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change. Configure supported overlay path persistence and health-driven switching to balance stateful continuity against real link failure.
C:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change. For this best change assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it.
D:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change. Validate member-specific gateway and static route semantics, and align zone routes with supported SD-WAN topology and security policy.
Question 372
A Fortinet SD-WAN and FortiSASE environment review finds: A long-lived ERP session repeatedly alternates between equally healthy tunnels after minor performance variations, breaking stateful middlebox expectations. The team proposes: Configure supported overlay path persistence and health-driven switching to balance stateful continuity against real link failure. Which FortiSASE technical principle most strongly supports the proposed response? Select ONE best answer.
- Log-export configuration is a service action dependent on private transport and mutual path reachability; enabling export does not guarantee delivery.
- Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
- Established-session state, NAT and protocol tracking influence path persistence independently of current control-plane route choices.
- A member must have a valid route and reachable next hop; membership in a logical SD-WAN zone is not proof of transport reachability.
Explanation
Correct Answer
B:Demonstrable success requires: Stateful traffic remains stable when paths are healthy and shifts only under intended events, with documented recovery behavior. This principle explains the proposed network response, which is: Configure supported overlay path persistence and health-driven switching to balance stateful continuity against real link failure.
Incorrect Answers
A:Log-export configuration is a service action dependent on private transport and mutual path reachability; enabling export does not guarantee delivery. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
C:Established-session state, NAT and protocol tracking influence path persistence independently of current control-plane route choices. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
D:This option addresses a different Fortinet NSE 7 secure networking topic (Per-member static-route gateway validity) rather than the documented Overlay stickiness and app session stability decision.
Question 373
The Fortinet network operations team has not approved a broad network-wide change. Available evidence indicates: A long-lived ERP session repeatedly alternates between equally healthy tunnels after minor performance variations, breaking stateful middlebox expectations. Which evidence best tests the FortiSASE diagnosis before approving a disruptive change? Select ONE best answer.
- Track member selection and session lifetime through jitter variation, true tunnel failure and controlled restore to service.
- Check policy order, user claims, category or app recognition, matched rule logs and allowed versus denied sample sessions.
- Compare explicit rule hits, implicit rule status, member eligibility, routing table and observed next hop for a test flow.
- Compare supported OS and agent versions, pilot incident rates, installed versions, connection logs and representative application tests.
Explanation
Correct Answer
A:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change. Confirm afterward that: Stateful traffic remains stable when paths are healthy and shifts only under intended events, with documented recovery behavior.
Incorrect Answers
B:Check policy order, user claims, category or app recognition, matched rule logs and allowed versus denied sample sessions. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
C:Compare explicit rule hits, implicit rule status, member eligibility, routing table and observed next hop for a test flow. A long-lived ERP session repeatedly alternates between equally healthy tunnels after minor performance variations, breaking stateful middlebox expectations.
D:Compare supported OS and agent versions, pilot incident rates, installed versions, connection logs and representative application tests. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
Question 374
A candidate network response has been piloted and stakeholders require a post-change acceptance check. Original problem: A long-lived ERP session repeatedly alternates between equally healthy tunnels after minor performance variations, breaking stateful middlebox expectations. The accountable service owner requires evidence that outcomes are met without disrupting planned work. Which acceptance result demonstrates that the network response meets the intended outcome? Select ONE best answer.
- Managed branches receive consistent members, tunnels and routing before steering policies are activated.
- Permitted research is performed under intended containment and sensitive identity or session context is not exposed to untrusted sites.
- Stateful traffic remains stable when paths are healthy and shifts only under intended events, with documented recovery behavior.
- New traffic chooses an eligible path and existing applications recover according to documented session-continuity expectations.
Explanation
Correct Answer
C:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change. The result must be validated using the documented site, route, application or user context.
Incorrect Answers
A:Managed branches receive consistent members, tunnels and routing before steering policies are activated. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
B:Permitted research is performed under intended containment and sensitive identity or session context is not exposed to untrusted sites. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
D:New traffic chooses an eligible path and existing applications recover according to documented session-continuity expectations. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
Question 375
A production SD-WAN or secure access change review identifies the following problem: A long-lived ERP session repeatedly alternates between equally healthy tunnels after minor performance variations, breaking stateful middlebox expectations. Which paired FortiSASE action and verification should close the review? Select ONE best answer.
- Change: Configure supported administrator SAML trust, assertion settings and least-privilege admin role mapping with a secured recovery path. Verify: Review issuer metadata, audience or reply URL, certificate status, identity claims and positive or denied admin login tests.
- Change: Verify supported ADVPN hub and spoke roles, discovery messages, peer reachability and shortcut policy before claiming direct tunnels. Verify: Inspect shortcut negotiation events, established IPsec SAs, path traces and fallback via hub from both spokes.
- Change: Configure supported overlay path persistence and health-driven switching to balance stateful continuity against real link failure. Verify: Track member selection and session lifetime through jitter variation, true tunnel failure and controlled restore to service.
- Change: Build the supported single-hub private SPA route and security policy with explicit return reachability and verified identity. Verify: Inspect hub route tables, session direction, FortiSASE connection policy, proxy or tunnel logs and bidirectional captures.
Explanation
Correct Answer
C:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change. This pair links the appropriate network response with evidence of the underlying FortiSASE issue.
Incorrect Answers
A:Change: Configure supported administrator SAML trust, assertion settings and least-privilege admin role mapping with a secured recovery path. A long-lived ERP session repeatedly alternates between equally healthy tunnels after minor performance variations, breaking stateful middlebox expectations.
B:This option addresses a different Fortinet NSE 7 secure networking topic (ADVPN shortcut creation) rather than the documented Overlay stickiness and app session stability decision.
D:Change: Build the supported single-hub private SPA route and security policy with explicit return reachability and verified identity. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
Question 376
A Fortinet NSE 7 architect is reviewing this FortiSASE environment scenario: A spoke keeps using a failed tunnel due to overaggressive path stickiness despite healthy backup overlays. An unsafe shortcut would be: Pin every session forever to its first tunnel even when the tunnel fails security or reachability checks. What should the FortiSASE administrator recommend as the narrowly scoped correction? Select ONE best answer.
- Validate supported BGP multipath or additional-path behavior and reachability of each selected overlay under the intended SD-WAN strategy.
- Pin every session forever to its first tunnel even when the tunnel fails security or reachability checks.
- Verify the implicit rule and appropriate default routing behavior, then add explicit rules only where business-specific steering is required.
- Configure supported overlay path persistence and health-driven switching to balance stateful continuity against real link failure.
Explanation
Correct Answer
D:The required acceptance condition is: Stateful traffic remains stable when paths are healthy and shifts only under intended events, with documented recovery behavior.
Incorrect Answers
A:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
B:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change. Use this instead: Configure supported overlay path persistence and health-driven switching to balance stateful continuity against real link failure.
C:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change. Verify the implicit rule and appropriate default routing behavior, then add explicit rules only where business-specific steering is required.
Question 377
A Fortinet SD-WAN and FortiSASE environment review finds: A spoke keeps using a failed tunnel due to overaggressive path stickiness despite healthy backup overlays. The team proposes: Configure supported overlay path persistence and health-driven switching to balance stateful continuity against real link failure. Which FortiSASE technical principle most strongly supports the proposed response? Select ONE best answer.
- Operational troubleshooting can expose user and network data; observability must preserve the tenant and data-privacy boundaries of the managed service.
- Synthetic active probes and observed session metrics answer different questions; either alone can miss path or application-specific degradation.
- Steering bypass affects which traffic receives FortiSASE controls; broad exceptions can undermine the service even when introduced to fix one app.
- Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
Explanation
Correct Answer
D:Demonstrable success requires: Stateful traffic remains stable when paths are healthy and shifts only under intended events, with documented recovery behavior.
Incorrect Answers
A:Operational troubleshooting can expose user and network data; observability must preserve the tenant and data-privacy boundaries of the managed service. A spoke keeps using a failed tunnel due to overaggressive path stickiness despite healthy backup overlays.
B:Synthetic active probes and observed session metrics answer different questions; either alone can miss path or application-specific degradation. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
C:Steering bypass affects which traffic receives FortiSASE controls; broad exceptions can undermine the service even when introduced to fix one app. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
Question 378
The Fortinet network operations team has not approved a broad network-wide change. Available evidence indicates: A spoke keeps using a failed tunnel due to overaggressive path stickiness despite healthy backup overlays. Which evidence best tests the FortiSASE diagnosis before approving a disruptive change? Select ONE best answer.
- Compare FQDN or destination match, affected process or app, observed direct paths, policy impact and expiry or review owner.
- Inspect server certificate SAN, chain, validity, client trust store, connection handshake and authorized-user policy match.
- Correlate session flags, NAT source, new versus existing flow creation and SLA event timestamps through controlled failover.
- Track member selection and session lifetime through jitter variation, true tunnel failure and controlled restore to service.
Explanation
Correct Answer
D:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
Incorrect Answers
A:Compare FQDN or destination match, affected process or app, observed direct paths, policy impact and expiry or review owner. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
B:Inspect server certificate SAN, chain, validity, client trust store, connection handshake and authorized-user policy match. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
C:Correlate session flags, NAT source, new versus existing flow creation and SLA event timestamps through controlled failover. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
Question 379
A candidate network response has been piloted and stakeholders require a post-change acceptance check. Original problem: A spoke keeps using a failed tunnel due to overaggressive path stickiness despite healthy backup overlays. The accountable service owner requires evidence that outcomes are met without disrupting planned work. Which acceptance result demonstrates that the network response meets the intended outcome? Select ONE best answer.
- The incident scope and actions are supported by traceable evidence while unrelated endpoints remain unaffected.
- Stateful traffic remains stable when paths are healthy and shifts only under intended events, with documented recovery behavior.
- Regional destinations use appropriate overlays and alternate-region fallback remains loop-free and auditable.
- Private apps are reachable through a maintainable supported path with intended policy and recovery under link faults.
Explanation
Correct Answer
B:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change. The approved implementation step was: Configure supported overlay path persistence and health-driven switching to balance stateful continuity against real link failure.
Incorrect Answers
A:The incident scope and actions are supported by traceable evidence while unrelated endpoints remain unaffected. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
C:Regional destinations use appropriate overlays and alternate-region fallback remains loop-free and auditable. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
D:Private apps are reachable through a maintainable supported path with intended policy and recovery under link faults. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
Question 380
For an original Fortinet NSE 7 FortiSASE 26 Architect educational scenario, consider: A spoke keeps using a failed tunnel due to overaggressive path stickiness despite healthy backup overlays. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Inspect hub peer relationships, BGP or overlay routes, advertised prefixes, policy enforcement and client-to-service traces.
- Change: Configure supported overlay path persistence and health-driven switching to balance stateful continuity against real link failure.
- Change: Match a supported agentless ZTNA access method with app protocol, certificate-based or SSO authentication and narrowly scoped private service policy.
- Check: Track member selection and session lifetime through jitter variation, true tunnel failure and controlled restore to service.
- Pin every session forever to its first tunnel even when the tunnel fails security or reachability checks.
Explanation
Correct Answer
B:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change. Acceptance: Stateful traffic remains stable when paths are healthy and shifts only under intended events, with documented recovery behavior.
D:Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change. Required intervention: Configure supported overlay path persistence and health-driven switching to balance stateful continuity against real link failure.
Incorrect Answers
A:Check: Inspect hub peer relationships, BGP or overlay routes, advertised prefixes, policy enforcement and client-to-service traces. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.
C:Change: Match a supported agentless ZTNA access method with app protocol, certificate-based or SSO authentication and narrowly scoped private service policy. A spoke keeps using a failed tunnel due to overaggressive path stickiness despite healthy backup overlays.
E:For this select two assessment, the shortcut changes or bypasses the necessary transport, routing, identity or security-policy boundary rather than correcting it. Stickiness retains an elected overlay under allowed conditions, but must yield when health or reachability constraints demand a change.