Fortinet NSE7_SSE_AR-26 Practice Test 29 - Prepaway
Practice Exams:

Pass Fortinet NSE7_SSE_AR-26 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$89.99 $98.99

NSE7_SSE_AR-26 Premium ETE File


  • Premium File 50 Questions & Answers. Last Update: Nov 13, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet NSE7_SSE_AR-26 Practice Test 29

Question 280

At fictional Granite Regional Services, the network resilience and VPN operations group observes: A new site establishes phase-one IKE but cannot reach one protected production network across the SD-WAN overlay. Diagnostic evidence: Tunnel diagnostics show compatible phase-one proposals yet the intended subnet is absent from negotiated phase-two selectors. Which scoped action together with a separately measurable acceptance check is best?

  1. For fictional Granite Regional Services, network resilience and VPN operations group: Action: Align approved traffic selectors and security policy across the IPsec peers for the required application networks. Independent proof: A test flow from the authorized subnet encrypts through the overlay while unauthorized prefixes remain excluded.
  2. For fictional Granite Regional Services, network resilience and VPN operations group: Action: Define the intended multipath and additional-paths behavior end-to-end and test forwarding and failover under load. Independent proof: The selected paths match the approved topology and fail over without transient duplicate or blackholed service.
  3. For fictional Granite Regional Services, network resilience and VPN operations group: Action: Correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes. Independent proof: BGP establishes across the intended tunnel and advertises only the authorized branch routes.
  4. For fictional Granite Regional Services, network resilience and VPN operations group: Action: Check supported ADVPN role settings, shortcut negotiation conditions and reachability across the relevant overlays. Independent proof: A controlled spoke-to-spoke flow creates the expected authorized shortcut without bypassing security policy.

Explanation

Correct Answer

A:

Align approved traffic selectors and security policy across the IPsec peers for the required application networks. Validation requires a test flow from the authorized subnet encrypts through the overlay while unauthorized prefixes remain excluded rather than relying on a successful configuration save. IPsec authentication can succeed before data-plane encryption selectors and routes permit a particular application flow.

Incorrect Answers

B:

Action: Define the intended multipath and additional-paths behavior end-to-end and test forwarding and failover under load. Independent proof: The selected paths match the approved topology and fail over without transient duplicate or blackholed service. It misses the relevant dependency because IPsec authentication can succeed before data-plane encryption selectors and routes permit a particular application flow. Instead verify that a test flow from the authorized subnet encrypts through the overlay while unauthorized prefixes remain excluded.

C:

The proposed pair addresses Action: Correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes. Independent proof: BGP establishes across the intended tunnel and advertises only the authorized branch routes. Here tunnel diagnostics show compatible phase-one proposals yet the intended subnet is absent from negotiated phase-two selectors. The bounded response is align approved traffic selectors and security policy across the IPsec peers for the required application networks with proof that a test flow from the authorized subnet encrypts through the overlay while unauthorized prefixes remain excluded.

D:

The alternative action and test—Action: Check supported ADVPN role settings, shortcut negotiation conditions and reachability across the relevant overlays. Independent proof: A controlled spoke-to-spoke flow creates the expected authorized shortcut without bypassing security policy—would measure a different issue. This case requires align approved traffic selectors and security policy across the IPsec peers for the required application networks and confirmation that a test flow from the authorized subnet encrypts through the overlay while unauthorized prefixes remain excluded.

Question 281

At fictional Meridian Business Group, the SD-WAN traffic engineering team controls application steering, routing and IPsec overlay policy. The observed FortiSASE 26/FortiOS 7.4–7.6 issue is: A new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. Distinguishing technical evidence: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Which bounded response is most defensible?

  1. For fictional Meridian Business Group, SD-WAN traffic engineering team: Align approved traffic selectors and security policy across the IPsec peers for the required application networks.
  2. For fictional Meridian Business Group, SD-WAN traffic engineering team: Correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes.
  3. For fictional Meridian Business Group, SD-WAN traffic engineering team: Check supported ADVPN role settings, shortcut negotiation conditions and reachability across the relevant overlays.
  4. For fictional Meridian Business Group, SD-WAN traffic engineering team: Review supported overlay-stickiness and session-change behavior against loss thresholds and application resiliency requirements.

Explanation

Correct Answer

B:

The case reveals FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. That matters because overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model. The corrective step is to correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes. Preserve this constraint during the change: Different deployments may use BGP per overlay or loopback peering; do not mix their requirements unintentionally.

Incorrect Answers

A:

Another possible response is to align approved traffic selectors and security policy across the IPsec peers for the required application networks. The case evidence instead shows that FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

C:

Check supported ADVPN role settings, shortcut negotiation conditions and reachability across the relevant overlays. This does not address the reported incident: a new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. The case-specific correction is to correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes.

D:

One alternative would be to review supported overlay-stickiness and session-change behavior against loss thresholds and application resiliency requirements. The observed evidence instead shows that FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. The more relevant correction is to correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes.

Question 282

At fictional Meridian Business Group, the SD-WAN traffic engineering team examines this advanced Fortinet architecture incident: A new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. Which observed finding most specifically distinguishes its cause before changing the configuration?

  1. For fictional Meridian Business Group, SD-WAN traffic engineering team: Session traces show existing flow affinity while another overlay meets the agreed performance SLA.
  2. For fictional Meridian Business Group, SD-WAN traffic engineering team: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay.
  3. For fictional Meridian Business Group, SD-WAN traffic engineering team: BGP detail shows multiple candidate paths without the supported additional-paths policy needed by the chosen topology.
  4. For fictional Meridian Business Group, SD-WAN traffic engineering team: IKE diagnostics identify a peer identity or trust-chain mismatch between the presented new certificate and configured expected identity.

Explanation

Correct Answer

B:

FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. It identifies the problem behind a new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. Overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

Incorrect Answers

A:

Session traces show existing flow affinity while another overlay meets the agreed performance SLA. It does not account for the observation FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay in the reported situation.

C:

One proposed finding is BGP detail shows multiple candidate paths without the supported additional-paths policy needed by the chosen topology. This would indicate another failure; here FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

D:

The alternative observation, IKE diagnostics identify a peer identity or trust-chain mismatch between the presented new certificate and configured expected identity, concerns a different dependency. This incident is distinguished by FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

Question 283

At fictional Meridian Business Group, the following problem has been reported: A new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. Evidence: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Proposed correction: Correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes. Which separate postchange test most convincingly verifies proper remediation?

  1. For fictional Meridian Business Group, SD-WAN traffic engineering team: The selected paths match the approved topology and fail over without transient duplicate or blackholed service.
  2. For fictional Meridian Business Group, SD-WAN traffic engineering team: The tunnel renegotiates with verified peer identity and a revoked test certificate is rejected.
  3. For fictional Meridian Business Group, SD-WAN traffic engineering team: A controlled spoke-to-spoke flow creates the expected authorized shortcut without bypassing security policy.
  4. For fictional Meridian Business Group, SD-WAN traffic engineering team: BGP establishes across the intended tunnel and advertises only the authorized branch routes.

Explanation

Correct Answer

D:

Success requires BGP establishes across the intended tunnel and advertises only the authorized branch routes. That result tests the previously observed condition: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

Incorrect Answers

A:

Even verifying the selected paths match the approved topology and fail over without transient duplicate or blackholed service leaves the reported failure unproven. An acceptance test must show that BGP establishes across the intended tunnel and advertises only the authorized branch routes.

B:

The alternative outcome is the tunnel renegotiates with verified peer identity and a revoked test certificate is rejected. It may validate a separate setting, but not the required action: correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes. The required observation is BGP establishes across the intended tunnel and advertises only the authorized branch routes.

C:

A controlled spoke-to-spoke flow creates the expected authorized shortcut without bypassing security policy. The evidence relevant to this incident is FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Confirm the corresponding recovery result: BGP establishes across the intended tunnel and advertises only the authorized branch routes.

Question 284

At fictional Meridian Business Group, operators encounter: A new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. The key diagnostic observation is: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Which Fortinet SD-WAN/FortiSASE architectural principle best informs the response?

  1. For fictional Meridian Business Group, SD-WAN traffic engineering team: Encrypted overlay availability depends on identity validation as well as transport reachability and cryptographic proposals.
  2. For fictional Meridian Business Group, SD-WAN traffic engineering team: ADVPN creates optimized spoke paths on top of a functioning hub-and-spoke overlay when discovery and negotiation are configured correctly.
  3. For fictional Meridian Business Group, SD-WAN traffic engineering team: IPsec authentication can succeed before data-plane encryption selectors and routes permit a particular application flow.
  4. For fictional Meridian Business Group, SD-WAN traffic engineering team: Overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

Explanation

Correct Answer

D:

The governing distinction is that overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model. Here, FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes.

Incorrect Answers

A:

Encrypted overlay availability depends on identity validation as well as transport reachability and cryptographic proposals. The decisive observation, FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay, requires a different explanation: Overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

B:

A different principle is: ADVPN creates optimized spoke paths on top of a functioning hub-and-spoke overlay when discovery and negotiation are configured correctly. The causal link actually supported by FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay is overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

C:

IPsec authentication can succeed before data-plane encryption selectors and routes permit a particular application flow. However, it does not explain FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. The applicable principle is that overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

Question 285

At fictional Meridian Business Group, the SD-WAN traffic engineering team observes: A new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. Diagnostic evidence: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Which scoped action together with a separately measurable acceptance check is best?

  1. For fictional Meridian Business Group, SD-WAN traffic engineering team: Action: Check supported ADVPN role settings, shortcut negotiation conditions and reachability across the relevant overlays. Independent proof: A controlled spoke-to-spoke flow creates the expected authorized shortcut without bypassing security policy.
  2. For fictional Meridian Business Group, SD-WAN traffic engineering team: Action: Correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes. Independent proof: BGP establishes across the intended tunnel and advertises only the authorized branch routes.
  3. For fictional Meridian Business Group, SD-WAN traffic engineering team: Action: Review supported overlay-stickiness and session-change behavior against loss thresholds and application resiliency requirements. Independent proof: New and recoverable sessions select an acceptable overlay while the system respects explicitly configured affinity boundaries.
  4. For fictional Meridian Business Group, SD-WAN traffic engineering team: Action: Update the approved peer identity and certificate trust configuration on the affected tunnel endpoints. Independent proof: The tunnel renegotiates with verified peer identity and a revoked test certificate is rejected.

Explanation

Correct Answer

B:

The documented evidence is FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. The proportionate response is to correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes; its success must be shown by BGP establishes across the intended tunnel and advertises only the authorized branch routes.

Incorrect Answers

A:

Action: Check supported ADVPN role settings, shortcut negotiation conditions and reachability across the relevant overlays. Independent proof: A controlled spoke-to-spoke flow creates the expected authorized shortcut without bypassing security policy. The pair does not resolve the observed FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Use correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes and verify BGP establishes across the intended tunnel and advertises only the authorized branch routes.

C:

The alternate plan combines Action: Review supported overlay-stickiness and session-change behavior against loss thresholds and application resiliency requirements. Independent proof: New and recoverable sessions select an acceptable overlay while the system respects explicitly configured affinity boundaries. The identified fault is FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Closing it requires BGP establishes across the intended tunnel and advertises only the authorized branch routes.

D:

The alternative proposal is Action: Update the approved peer identity and certificate trust configuration on the affected tunnel endpoints. Independent proof: The tunnel renegotiates with verified peer identity and a revoked test certificate is rejected. It does not address the current evidence: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. The appropriate action is correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes.

Question 286

At fictional Cedar Valley University, the network resilience and VPN operations group maintains branch routing, BGP and secured overlays. The observed FortiSASE 26/FortiOS 7.4–7.6 issue is: A new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. Distinguishing technical evidence: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Which bounded response is most defensible?

  1. For fictional Cedar Valley University, network resilience and VPN operations group: Define the intended multipath and additional-paths behavior end-to-end and test forwarding and failover under load.
  2. For fictional Cedar Valley University, network resilience and VPN operations group: Align approved traffic selectors and security policy across the IPsec peers for the required application networks.
  3. For fictional Cedar Valley University, network resilience and VPN operations group: Update the approved peer identity and certificate trust configuration on the affected tunnel endpoints.
  4. For fictional Cedar Valley University, network resilience and VPN operations group: Correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes.

Explanation

Correct Answer

D:

FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Instead of unrelated changes, correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes. The expected result is BGP establishes across the intended tunnel and advertises only the authorized branch routes. Preserve this constraint during the change: Different deployments may use BGP per overlay or loopback peering; do not mix their requirements unintentionally.

Incorrect Answers

A:

Define the intended multipath and additional-paths behavior end-to-end and test forwarding and failover under load. It could be useful for another problem, but it does not change FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. The response needs to correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes.

B:

An alternative action is align approved traffic selectors and security policy across the IPsec peers for the required application networks. This incident instead involves FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Confirm the scoped change through BGP establishes across the intended tunnel and advertises only the authorized branch routes.

C:

Update the approved peer identity and certificate trust configuration on the affected tunnel endpoints. That would not correct the reported FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. The supported response is to correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes.

Question 287

At fictional Cedar Valley University, the network resilience and VPN operations group examines this advanced Fortinet architecture incident: A new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. Which observed finding most specifically distinguishes its cause before changing the configuration?

  1. For fictional Cedar Valley University, network resilience and VPN operations group: BGP detail shows multiple candidate paths without the supported additional-paths policy needed by the chosen topology.
  2. For fictional Cedar Valley University, network resilience and VPN operations group: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay.
  3. For fictional Cedar Valley University, network resilience and VPN operations group: IKE diagnostics identify a peer identity or trust-chain mismatch between the presented new certificate and configured expected identity.
  4. For fictional Cedar Valley University, network resilience and VPN operations group: Tunnel diagnostics show compatible phase-one proposals yet the intended subnet is absent from negotiated phase-two selectors.

Explanation

Correct Answer

B:

Look for the recorded condition: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. That is decisive because overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model. Correction should target correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes.

Incorrect Answers

A:

BGP detail shows multiple candidate paths without the supported additional-paths policy needed by the chosen topology. That finding does not isolate the reported issue: a new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. The determining evidence is FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay.

C:

That alternative instead describes IKE diagnostics identify a peer identity or trust-chain mismatch between the presented new certificate and configured expected identity. The actual diagnostic record shows FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay instead. The difference matters because overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

D:

Even if tunnel diagnostics show compatible phase-one proposals yet the intended subnet is absent from negotiated phase-two selectors, it would not establish the cause here. FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. The case-specific correction is to correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes.

Question 288

At fictional Cedar Valley University, the following problem has been reported: A new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. Evidence: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Proposed correction: Correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes. Which separate postchange test most convincingly verifies proper remediation?

  1. For fictional Cedar Valley University, network resilience and VPN operations group: A controlled spoke-to-spoke flow creates the expected authorized shortcut without bypassing security policy.
  2. For fictional Cedar Valley University, network resilience and VPN operations group: New and recoverable sessions select an acceptable overlay while the system respects explicitly configured affinity boundaries.
  3. For fictional Cedar Valley University, network resilience and VPN operations group: BGP establishes across the intended tunnel and advertises only the authorized branch routes.
  4. For fictional Cedar Valley University, network resilience and VPN operations group: A test flow from the authorized subnet encrypts through the overlay while unauthorized prefixes remain excluded.

Explanation

Correct Answer

C:

To close the incident, demonstrate that BGP establishes across the intended tunnel and advertises only the authorized branch routes. That addresses FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay and reflects the rule that overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

Incorrect Answers

A:

A test that a controlled spoke-to-spoke flow creates the expected authorized shortcut without bypassing security policy would not demonstrate closure of this condition. The needed proof is BGP establishes across the intended tunnel and advertises only the authorized branch routes.

B:

New and recoverable sessions select an acceptable overlay while the system respects explicitly configured affinity boundaries. That does not demonstrate the case-specific success condition: BGP establishes across the intended tunnel and advertises only the authorized branch routes. Overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

D:

A test flow from the authorized subnet encrypts through the overlay while unauthorized prefixes remain excluded. That result does not test the original problem, identified by FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Recovery must show that BGP establishes across the intended tunnel and advertises only the authorized branch routes.

Question 289

At fictional Cedar Valley University, operators encounter: A new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. The key diagnostic observation is: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Which Fortinet SD-WAN/FortiSASE architectural principle best informs the response?

  1. For fictional Cedar Valley University, network resilience and VPN operations group: Encrypted overlay availability depends on identity validation as well as transport reachability and cryptographic proposals.
  2. For fictional Cedar Valley University, network resilience and VPN operations group: Session stability and dynamic path optimization are competing goals in tunneled SD-WAN networks.
  3. For fictional Cedar Valley University, network resilience and VPN operations group: ADVPN creates optimized spoke paths on top of a functioning hub-and-spoke overlay when discovery and negotiation are configured correctly.
  4. For fictional Cedar Valley University, network resilience and VPN operations group: Overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

Explanation

Correct Answer

D:

Overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model. That explains the observed condition: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. The scoped response is to correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes.

Incorrect Answers

A:

A proposed explanation is encrypted overlay availability depends on identity validation as well as transport reachability and cryptographic proposals. The present evidence is FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay, which instead follows from overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

B:

Session stability and dynamic path optimization are competing goals in tunneled SD-WAN networks. This describes another relationship, not the cause of a new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. Overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

C:

The rule ADVPN creates optimized spoke paths on top of a functioning hub-and-spoke overlay when discovery and negotiation are configured correctly does not account for FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. This case is governed by overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

Question 290

At fictional Cedar Valley University, the network resilience and VPN operations group observes: A new hub-and-spoke overlay carries encrypted packets, but the BGP peer is configured on an unreachable interface outside that tunnel. Diagnostic evidence: FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. Which scoped action together with a separately measurable acceptance check is best?

  1. For fictional Cedar Valley University, network resilience and VPN operations group: Action: Define the intended multipath and additional-paths behavior end-to-end and test forwarding and failover under load. Independent proof: The selected paths match the approved topology and fail over without transient duplicate or blackholed service.
  2. For fictional Cedar Valley University, network resilience and VPN operations group: Action: Align approved traffic selectors and security policy across the IPsec peers for the required application networks. Independent proof: A test flow from the authorized subnet encrypts through the overlay while unauthorized prefixes remain excluded.
  3. For fictional Cedar Valley University, network resilience and VPN operations group: Action: Update the approved peer identity and certificate trust configuration on the affected tunnel endpoints. Independent proof: The tunnel renegotiates with verified peer identity and a revoked test certificate is rejected.
  4. For fictional Cedar Valley University, network resilience and VPN operations group: Action: Correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes. Independent proof: BGP establishes across the intended tunnel and advertises only the authorized branch routes.

Explanation

Correct Answer

D:

The proposed change is to correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes. The separate proof is BGP establishes across the intended tunnel and advertises only the authorized branch routes. Overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model.

Incorrect Answers

A:

Action: Define the intended multipath and additional-paths behavior end-to-end and test forwarding and failover under load. Independent proof: The selected paths match the approved topology and fail over without transient duplicate or blackholed service. It misses the relevant dependency because overlay routing adjacency must use reachable endpoints that match the chosen IPsec and BGP design model. Instead verify that BGP establishes across the intended tunnel and advertises only the authorized branch routes.

B:

The proposed pair addresses Action: Align approved traffic selectors and security policy across the IPsec peers for the required application networks. Independent proof: A test flow from the authorized subnet encrypts through the overlay while unauthorized prefixes remain excluded. Here FortiGate BGP debug reports failed TCP peering to an address not reachable through the assigned overlay. The bounded response is correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes with proof that BGP establishes across the intended tunnel and advertises only the authorized branch routes.

C:

The alternative action and test—Action: Update the approved peer identity and certificate trust configuration on the affected tunnel endpoints. Independent proof: The tunnel renegotiates with verified peer identity and a revoked test certificate is rejected—would measure a different issue. This case requires correct the documented BGP overlay neighbor addressing and source interface before redistributing branch prefixes and confirmation that BGP establishes across the intended tunnel and advertises only the authorized branch routes.

Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests