Practice Exams:

Fortinet FCP_FGT_AD-7.6 Dumps

EXAM: FCP - FortiGate 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

FCP_FGT_AD-7.6 Premium ETE File


  • Premium File 128 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet FCP_FGT_AD-7.6 Practice Test 58

Question 570

A freight depot's backup tunnel remains stuck after the primary modem briefly loses carrier. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the freight depot's backup tunnel deployment: Implement: Tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity. Verify: Disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.
  2. For the freight depot's backup tunnel deployment: Implement: Tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity. Verify: Disconnect the remote peer briefly and observe DPD events, SA state change and successful renegotiation after connectivity returns.
  3. For the freight depot's backup tunnel deployment: Implement: Configure an interface-based IPsec tunnel with a route and bidirectional firewall policy matching the intended protected networks. Verify: Verify tunnel interface and route status, send a packet to the remote protected prefix and check matching policy and tunnel byte counters.
  4. For the freight depot's backup tunnel deployment: Implement: Check UDP 500/4500 path and supported NAT traversal settings when an IPsec peer sits behind address translation. Verify: Disconnect the remote peer briefly and observe DPD events, SA state change and successful renegotiation after connectivity returns.

Answer & Explanations

Correct answer: B

A.

This action and check address the alternate operation “For the freight depot's backup tunnel deployment: Implement: Tune supported dead peer detection and recovery behavior appropriate to a…” instead of the stated acceptance requirement. The matching action is to tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity. Its confirming test is to disconnect the remote peer briefly and observe DPD events, SA state change and successful renegotiation after connectivity returns.

B.

The situation is that a freight depot's backup tunnel remains stuck after the primary modem briefly loses carrier. Implement: Tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity. Verify: Disconnect the remote peer briefly and observe DPD events, SA state change and successful renegotiation after connectivity returns. This pairing is justified because DPD identifies an unresponsive IKE peer so stale SAs can be cleared and re-established; it does not replace routing or persistent tunnel monitoring.

C.

The situation is that a freight depot's backup tunnel remains stuck after the primary modem briefly loses carrier. This action and check address the distinct objective “Add route and policy for an interface-based IPsec tunnel” instead of the stated acceptance requirement. The matching action is to tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity. Its confirming test is to disconnect the remote peer briefly and observe DPD events, SA state change and successful renegotiation after connectivity returns.

D.

This action and check address the alternate operation “For the freight depot's backup tunnel deployment: Implement: Check UDP 500/4500 path and supported NAT traversal settings when an…” instead of the stated acceptance requirement. The matching action is to tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity. Its confirming test is to disconnect the remote peer briefly and observe DPD events, SA state change and successful renegotiation after connectivity returns.

Question 571

A national charity maintains two WAN providers for its branch-to-data-center protected network. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the national charity deployment: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures.
  2. For the national charity deployment: Check UDP 500/4500 path and supported NAT traversal settings when an IPsec peer sits behind address translation.
  3. For the national charity deployment: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage.
  4. For the national charity deployment: Tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity.

Answer & Explanations

Correct answer: C

A.

This option addresses the distinct objective “Use constrained IKE diagnostics to distinguish negotiation faults”, not the immediate requirement. IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate. For the stated case, multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

B.

This option addresses the distinct objective “Account for NAT traversal of IKE and IPsec”, not the immediate requirement. NAT traversal encapsulates ESP in UDP 4500 where negotiated and needed; an intermediary that drops required IKE or UDP-encapsulated traffic can break tunnel establishment or data. For the stated case, multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

C.

Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. This resolves the issue because multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions. To verify, disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

D.

This option addresses the distinct objective “Use dead peer detection to clear broken sessions”, not the immediate requirement. DPD identifies an unresponsive IKE peer so stale SAs can be cleared and re-established; it does not replace routing or persistent tunnel monitoring. For the stated case, multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

Question 572

A national charity maintains two WAN providers for its branch-to-data-center protected network. The engineer proposes this change: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the national charity deployment: NAT traversal encapsulates ESP in UDP 4500 where negotiated and needed; an intermediary that drops required IKE or UDP-encapsulated traffic can break tunnel establishment or data.
  2. For the national charity deployment: DPD identifies an unresponsive IKE peer so stale SAs can be cleared and re-established; it does not replace routing or persistent tunnel monitoring.
  3. For the national charity deployment: IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.
  4. For the national charity deployment: Multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

Answer & Explanations

Correct answer: D

A.

That statement explains the distinct objective “Account for NAT traversal of IKE and IPsec” rather than the cause in this case. The deciding mechanism here is that multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

B.

That statement explains the distinct objective “Use dead peer detection to clear broken sessions” rather than the cause in this case. The deciding mechanism here is that multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

C.

That statement explains the distinct objective “Use constrained IKE diagnostics to distinguish negotiation faults” rather than the cause in this case. The deciding mechanism here is that multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

D.

Multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions. It supports this action: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. To confirm, disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

Question 573

A national charity maintains two WAN providers for its branch-to-data-center protected network. After implementing this change—Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage—which test best establishes that the intended outcome is actually working?

  1. For the national charity deployment: Disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.
  2. For the national charity deployment: Trace the peer handshake and UDP port negotiation on both sides of the NAT device, then confirm encrypted byte counters advance.
  3. For the national charity deployment: Disconnect the remote peer briefly and observe DPD events, SA state change and successful renegotiation after connectivity returns.
  4. For the national charity deployment: Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

Answer & Explanations

Correct answer: A

A.

Disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely. This is the relevant test because multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

B.

This check would help evaluate the distinct objective “Account for NAT traversal of IKE and IPsec”, but not the required result. For this case, disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

C.

This check would help evaluate the distinct objective “Use dead peer detection to clear broken sessions”, but not the required result. For this case, disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

D.

This check would help evaluate the distinct objective “Use constrained IKE diagnostics to distinguish negotiation faults”, but not the required result. For this case, disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

Question 574

A national charity maintains two WAN providers for its branch-to-data-center protected network. Which proposed shortcut would most directly cause an available standby tunnel never receiving traffic during the main peer failure, and therefore must be avoided for this requirement?

  1. For the national charity deployment: Permit only unencapsulated ESP through an upstream NAT while blocking required UDP negotiation.
  2. For the national charity deployment: Declare redundancy complete because a second tunnel object exists without any valid backup route.
  3. For the national charity deployment: Set the tunnel to trust stale SAs indefinitely whenever the peer goes offline.
  4. For the national charity deployment: Run unrestricted debug sessions for hours and conclude the cause solely from a generic failed ping.

Answer & Explanations

Correct answer: B

A.

That shortcut would relate to the distinct objective “Account for NAT traversal of IKE and IPsec”, rather than the specific configuration or use described. The unsafe step in this case is to declare redundancy complete because a second tunnel object exists without any valid backup route.

B.

Declare redundancy complete because a second tunnel object exists without any valid backup route. The proposed shortcut bypasses the needed control: Multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions. The appropriate response is to create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage.

C.

That shortcut would relate to the distinct objective “Use dead peer detection to clear broken sessions”, rather than the specific configuration or use described. The unsafe step in this case is to declare redundancy complete because a second tunnel object exists without any valid backup route.

D.

That shortcut would relate to the distinct objective “Use constrained IKE diagnostics to distinguish negotiation faults”, rather than the specific configuration or use described. The unsafe step in this case is to declare redundancy complete because a second tunnel object exists without any valid backup route.

Question 575

A national charity maintains two WAN providers for its branch-to-data-center protected network. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the national charity deployment: Implement: Check UDP 500/4500 path and supported NAT traversal settings when an IPsec peer sits behind address translation. Verify: Trace the peer handshake and UDP port negotiation on both sides of the NAT device, then confirm encrypted byte counters advance.
  2. For the national charity deployment: Implement: Tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity. Verify: Disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.
  3. For the national charity deployment: Implement: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. Verify: Disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.
  4. For the national charity deployment: Implement: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. Verify: Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

Answer & Explanations

Correct answer: C

A.

This action and check address the distinct objective “Account for NAT traversal of IKE and IPsec” instead of the stated acceptance requirement. The matching action is to create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. Its confirming test is to disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

B.

This action and check address the alternate operation “For the national charity deployment: Implement: Tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected…” instead of the stated acceptance requirement. The matching action is to create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. Its confirming test is to disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

C.

Implement: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. Verify: Disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely. This pairing is justified because multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

D.

This action and check address the alternate operation “For the national charity deployment: Implement: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health…” instead of the stated acceptance requirement. The matching action is to create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. Its confirming test is to disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

Question 576

A public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the public utilities cooperative deployment: Tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity.
  2. For the public utilities cooperative deployment: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures.
  3. For the public utilities cooperative deployment: Check UDP 500/4500 path and supported NAT traversal settings when an IPsec peer sits behind address translation.
  4. For the public utilities cooperative deployment: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage.

Answer & Explanations

Correct answer: D

A.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. This option addresses the distinct objective “Use dead peer detection to clear broken sessions”, not the immediate requirement. DPD identifies an unresponsive IKE peer so stale SAs can be cleared and re-established; it does not replace routing or persistent tunnel monitoring. For the stated case, multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

B.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. This option addresses the distinct objective “Use constrained IKE diagnostics to distinguish negotiation faults”, not the immediate requirement. IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate. For the stated case, multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

C.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. This option addresses the distinct objective “Account for NAT traversal of IKE and IPsec”, not the immediate requirement. NAT traversal encapsulates ESP in UDP 4500 where negotiated and needed; an intermediary that drops required IKE or UDP-encapsulated traffic can break tunnel establishment or data. For the stated case, multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

D.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. This resolves the issue because multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions. To verify, disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

Question 577

A public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. The engineer proposes this change: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the public utilities cooperative deployment: Multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.
  2. For the public utilities cooperative deployment: DPD identifies an unresponsive IKE peer so stale SAs can be cleared and re-established; it does not replace routing or persistent tunnel monitoring.
  3. For the public utilities cooperative deployment: IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.
  4. For the public utilities cooperative deployment: NAT traversal encapsulates ESP in UDP 4500 where negotiated and needed; an intermediary that drops required IKE or UDP-encapsulated traffic can break tunnel establishment or data.

Answer & Explanations

Correct answer: A

A.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. Multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions. It supports this action: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. To confirm, disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

B.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. That statement explains the distinct objective “Use dead peer detection to clear broken sessions” rather than the cause in this case. The deciding mechanism here is that multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

C.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. That statement explains the distinct objective “Use constrained IKE diagnostics to distinguish negotiation faults” rather than the cause in this case. The deciding mechanism here is that multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

D.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. That statement explains the distinct objective “Account for NAT traversal of IKE and IPsec” rather than the cause in this case. The deciding mechanism here is that multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

Question 578

A public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. After implementing this change—Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage—which test best establishes that the intended outcome is actually working?

  1. For the public utilities cooperative deployment: Disconnect the remote peer briefly and observe DPD events, SA state change and successful renegotiation after connectivity returns.
  2. For the public utilities cooperative deployment: Disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.
  3. For the public utilities cooperative deployment: Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.
  4. For the public utilities cooperative deployment: Trace the peer handshake and UDP port negotiation on both sides of the NAT device, then confirm encrypted byte counters advance.

Answer & Explanations

Correct answer: B

A.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. This check would help evaluate the distinct objective “Use dead peer detection to clear broken sessions”, but not the required result. For this case, disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

B.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. Disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely. This is the relevant test because multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

C.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. This check would help evaluate the distinct objective “Use constrained IKE diagnostics to distinguish negotiation faults”, but not the required result. For this case, disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

D.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. This check would help evaluate the distinct objective “Account for NAT traversal of IKE and IPsec”, but not the required result. For this case, disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

Question 579

A public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. Which proposed shortcut would most directly cause an available standby tunnel never receiving traffic during the main peer failure, and therefore must be avoided for this requirement?

  1. For the public utilities cooperative deployment: Set the tunnel to trust stale SAs indefinitely whenever the peer goes offline.
  2. For the public utilities cooperative deployment: Run unrestricted debug sessions for hours and conclude the cause solely from a generic failed ping.
  3. For the public utilities cooperative deployment: Declare redundancy complete because a second tunnel object exists without any valid backup route.
  4. For the public utilities cooperative deployment: Permit only unencapsulated ESP through an upstream NAT while blocking required UDP negotiation.

Answer & Explanations

Correct answer: C

A.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. That shortcut would relate to the distinct objective “Use dead peer detection to clear broken sessions”, rather than the specific configuration or use described. The unsafe step in this case is to declare redundancy complete because a second tunnel object exists without any valid backup route.

B.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. That shortcut would relate to the distinct objective “Use constrained IKE diagnostics to distinguish negotiation faults”, rather than the specific configuration or use described. The unsafe step in this case is to declare redundancy complete because a second tunnel object exists without any valid backup route.

C.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. Declare redundancy complete because a second tunnel object exists without any valid backup route. The proposed shortcut bypasses the needed control: Multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions. The appropriate response is to create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage.

D.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. That shortcut would relate to the distinct objective “Account for NAT traversal of IKE and IPsec”, rather than the specific configuration or use described. The unsafe step in this case is to declare redundancy complete because a second tunnel object exists without any valid backup route.

Question 580

A public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the public utilities cooperative deployment: Implement: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. Verify: Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.
  2. For the public utilities cooperative deployment: Implement: Check UDP 500/4500 path and supported NAT traversal settings when an IPsec peer sits behind address translation. Verify: Trace the peer handshake and UDP port negotiation on both sides of the NAT device, then confirm encrypted byte counters advance.
  3. For the public utilities cooperative deployment: Implement: Tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity. Verify: Disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.
  4. For the public utilities cooperative deployment: Implement: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. Verify: Disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

Answer & Explanations

Correct answer: D

A.

This action and check address the alternate operation “For the public utilities cooperative deployment: Implement: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel…” instead of the stated acceptance requirement. The matching action is to create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. Its confirming test is to disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

B.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. This action and check address the distinct objective “Account for NAT traversal of IKE and IPsec” instead of the stated acceptance requirement. The matching action is to create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. Its confirming test is to disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

C.

This action and check address the alternate operation “For the public utilities cooperative deployment: Implement: Tune supported dead peer detection and recovery behavior appropriate to a tunnel's…” instead of the stated acceptance requirement. The matching action is to create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. Its confirming test is to disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely.

D.

The situation is that a public utilities cooperative wants protected telemetry to traverse an alternate IPsec peer when its primary ISP fails. Implement: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage. Verify: Disable the preferred peer in a maintenance test, verify the backup route and tunnel counters, then restore preferred-path behavior safely. This pairing is justified because multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.

FCP - FortiGate 7.6 Administrator (FCP_FGT_AD-7.6) Practice Tests