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 59

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.

Question 581

A maritime terminal has intermittent IPsec bring-up failures after a peer update and needs a bounded negotiation trace. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the maritime terminal deployment: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures.
  2. For the maritime terminal deployment: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication.
  3. For the maritime terminal deployment: Tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity.
  4. For the maritime terminal 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: A

A.

Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. This resolves the issue because IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate. To verify, perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

B.

This option addresses the distinct objective “Use certificate-based peer identity when policy requires it”, not the immediate requirement. Certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key. For the stated case, IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

C.

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, IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

D.

This option addresses the distinct objective “Design redundant IPsec paths with measurable failover”, not the immediate requirement. Multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions. For the stated case, IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

Question 582

A maritime terminal has intermittent IPsec bring-up failures after a peer update and needs a bounded negotiation trace. The engineer proposes this change: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the maritime terminal deployment: Certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.
  2. For the maritime terminal deployment: IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.
  3. For the maritime terminal 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.
  4. For the maritime terminal 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: B

A.

That statement explains the distinct objective “Use certificate-based peer identity when policy requires it” rather than the cause in this case. The deciding mechanism here is that IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

B.

IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate. It supports this action: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. To confirm, perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

C.

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 IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

D.

That statement explains the distinct objective “Design redundant IPsec paths with measurable failover” rather than the cause in this case. The deciding mechanism here is that IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

Question 583

A maritime terminal has intermittent IPsec bring-up failures after a peer update and needs a bounded negotiation trace. After implementing this change—Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures—which test best establishes that the intended outcome is actually working?

  1. For the maritime terminal deployment: Inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.
  2. For the maritime terminal deployment: Disconnect the remote peer briefly and observe DPD events, SA state change and successful renegotiation after connectivity returns.
  3. For the maritime terminal deployment: Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.
  4. For the maritime terminal deployment: 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: C

A.

This check would help evaluate the distinct objective “Use certificate-based peer identity when policy requires it”, but not the required result. For this case, perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

B.

This check would help evaluate the distinct objective “Use dead peer detection to clear broken sessions”, but not the required result. For this case, perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

C.

Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction. This is the relevant test because IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

D.

This check would help evaluate the distinct objective “Design redundant IPsec paths with measurable failover”, but not the required result. For this case, perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

Question 584

A maritime terminal has intermittent IPsec bring-up failures after a peer update and needs a bounded negotiation trace. Which proposed shortcut would most directly cause flooded diagnostic logs without isolating the actual negotiation failure, and therefore must be avoided for this requirement?

  1. For the maritime terminal deployment: Set the tunnel to trust stale SAs indefinitely whenever the peer goes offline.
  2. For the maritime terminal deployment: Declare redundancy complete because a second tunnel object exists without any valid backup route.
  3. For the maritime terminal deployment: Accept any self-presented peer certificate without checking its issuing trust chain or identity.
  4. For the maritime terminal deployment: Run unrestricted debug sessions for hours and conclude the cause solely from a generic failed ping.

Answer & Explanations

Correct answer: D

A.

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 run unrestricted debug sessions for hours and conclude the cause solely from a generic failed ping.

B.

That shortcut would relate to the distinct objective “Design redundant IPsec paths with measurable failover”, rather than the specific configuration or use described. The unsafe step in this case is to run unrestricted debug sessions for hours and conclude the cause solely from a generic failed ping.

C.

That shortcut would relate to the distinct objective “Use certificate-based peer identity when policy requires it”, rather than the specific configuration or use described. The unsafe step in this case is to run unrestricted debug sessions for hours and conclude the cause solely from a generic failed ping.

D.

Run unrestricted debug sessions for hours and conclude the cause solely from a generic failed ping. The proposed shortcut bypasses the needed control: IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate. The appropriate response is to capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures.

Question 585

A maritime terminal has intermittent IPsec bring-up failures after a peer update and needs a bounded negotiation trace. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the maritime terminal deployment: Implement: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. Verify: Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.
  2. For the maritime terminal 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 maritime terminal 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.
  4. For the maritime terminal deployment: Implement: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. Verify: Inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

Answer & Explanations

Correct answer: A

A.

Implement: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. Verify: Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction. This pairing is justified because IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

B.

This action and check address the distinct objective “Use dead peer detection to clear broken sessions” instead of the stated acceptance requirement. The matching action is to capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. Its confirming test is to perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

C.

This action and check address the alternate operation “For the maritime terminal 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 capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. Its confirming test is to perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

D.

This action and check address the alternate operation “For the maritime terminal deployment: Implement: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one,…” instead of the stated acceptance requirement. The matching action is to capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. Its confirming test is to perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

Question 586

A regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the regional office deployment: Tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity.
  2. For the regional office deployment: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures.
  3. For the regional office 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 regional office deployment: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication.

Answer & Explanations

Correct answer: B

A.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. 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, IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

B.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. This resolves the issue because IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate. To verify, perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

C.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. This option addresses the distinct objective “Design redundant IPsec paths with measurable failover”, not the immediate requirement. Multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions. For the stated case, IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

D.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. This option addresses the distinct objective “Use certificate-based peer identity when policy requires it”, not the immediate requirement. Certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key. For the stated case, IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

Question 587

A regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. The engineer proposes this change: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the regional office 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.
  2. For the regional office deployment: Multiple configured tunnels are not themselves a failover plan; eligible routes and health signals determine which path receives new protected sessions.
  3. For the regional office 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 regional office deployment: Certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

Answer & Explanations

Correct answer: C

A.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. 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 IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

B.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. That statement explains the distinct objective “Design redundant IPsec paths with measurable failover” rather than the cause in this case. The deciding mechanism here is that IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

C.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate. It supports this action: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. To confirm, perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

D.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. That statement explains the distinct objective “Use certificate-based peer identity when policy requires it” rather than the cause in this case. The deciding mechanism here is that IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

Question 588

A regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. After implementing this change—Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures—which test best establishes that the intended outcome is actually working?

  1. For the regional office 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 regional office deployment: Inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.
  3. For the regional office deployment: Disconnect the remote peer briefly and observe DPD events, SA state change and successful renegotiation after connectivity returns.
  4. For the regional office deployment: Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

Answer & Explanations

Correct answer: D

A.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. This check would help evaluate the distinct objective “Design redundant IPsec paths with measurable failover”, but not the required result. For this case, perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

B.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. This check would help evaluate the distinct objective “Use certificate-based peer identity when policy requires it”, but not the required result. For this case, perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

C.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. This check would help evaluate the distinct objective “Use dead peer detection to clear broken sessions”, but not the required result. For this case, perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

D.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction. This is the relevant test because IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

Question 589

A regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. Which proposed shortcut would most directly cause flooded diagnostic logs without isolating the actual negotiation failure, and therefore must be avoided for this requirement?

  1. For the regional office deployment: Run unrestricted debug sessions for hours and conclude the cause solely from a generic failed ping.
  2. For the regional office deployment: Declare redundancy complete because a second tunnel object exists without any valid backup route.
  3. For the regional office deployment: Accept any self-presented peer certificate without checking its issuing trust chain or identity.
  4. For the regional office deployment: Set the tunnel to trust stale SAs indefinitely whenever the peer goes offline.

Answer & Explanations

Correct answer: A

A.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. Run unrestricted debug sessions for hours and conclude the cause solely from a generic failed ping. The proposed shortcut bypasses the needed control: IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate. The appropriate response is to capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures.

B.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. That shortcut would relate to the distinct objective “Design redundant IPsec paths with measurable failover”, rather than the specific configuration or use described. The unsafe step in this case is to run unrestricted debug sessions for hours and conclude the cause solely from a generic failed ping.

C.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. That shortcut would relate to the distinct objective “Use certificate-based peer identity when policy requires it”, rather than the specific configuration or use described. The unsafe step in this case is to run unrestricted debug sessions for hours and conclude the cause solely from a generic failed ping.

D.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. 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 run unrestricted debug sessions for hours and conclude the cause solely from a generic failed ping.

Question 590

A regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the regional office 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 regional office deployment: Implement: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. Verify: Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.
  3. For the regional office deployment: Implement: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. Verify: Inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.
  4. For the regional office 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.

Answer & Explanations

Correct answer: B

A.

This action and check address the alternate operation “For the regional office 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 capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. Its confirming test is to perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

B.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. Implement: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. Verify: Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction. This pairing is justified because IKE negotiation traces can expose peer ID, proposal and selector mismatches that generic interface counters or a ping alone cannot isolate.

C.

This action and check address the alternate operation “For the regional office deployment: Implement: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one,…” instead of the stated acceptance requirement. The matching action is to capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. Its confirming test is to perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

D.

The situation is that a regional office sees an up physical interface but a tunnel that alternates between IKE failure and missing routes. This action and check address the distinct objective “Use dead peer detection to clear broken sessions” instead of the stated acceptance requirement. The matching action is to capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures. Its confirming test is to perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

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