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 60

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.

Question 591

A legal records cooperative replaces shared VPN secrets with certificate-authenticated peers across three offices. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the legal records cooperative replaces deployment: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures.
  2. For the legal records cooperative replaces deployment: Create redundant tunnels and route or SD-WAN preferences that use actual tunnel health to direct protected traffic during one peer outage.
  3. For the legal records cooperative replaces deployment: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication.
  4. For the legal records cooperative replaces 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, certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

B.

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, certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

C.

Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. This resolves the issue because certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key. To verify, inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

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, certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

Question 592

A legal records cooperative replaces shared VPN secrets with certificate-authenticated peers across three offices. The engineer proposes this change: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the legal records cooperative replaces 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 legal records cooperative replaces 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 legal records cooperative replaces 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 legal records cooperative replaces 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: D

A.

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 certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

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 certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

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 certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

D.

Certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key. It supports this action: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. To confirm, inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

Question 593

A legal records cooperative replaces shared VPN secrets with certificate-authenticated peers across three offices. After implementing this change—Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication—which test best establishes that the intended outcome is actually working?

  1. For the legal records cooperative replaces 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 legal records cooperative replaces 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 legal records cooperative replaces deployment: Disconnect the remote peer briefly and observe DPD events, SA state change and successful renegotiation after connectivity returns.
  4. For the legal records cooperative replaces deployment: Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.

Answer & Explanations

Correct answer: A

A.

Inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA. This is the relevant test because certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

B.

This check would help evaluate the distinct objective “Design redundant IPsec paths with measurable failover”, but not the required result. For this case, inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

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, inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

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, inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

Question 594

A legal records cooperative replaces shared VPN secrets with certificate-authenticated peers across three offices. Which proposed shortcut would most directly cause unauthorized or misidentified peers establishing or attempting protected tunnels, and therefore must be avoided for this requirement?

  1. For the legal records cooperative replaces deployment: Declare redundancy complete because a second tunnel object exists without any valid backup route.
  2. For the legal records cooperative replaces deployment: Accept any self-presented peer certificate without checking its issuing trust chain or identity.
  3. For the legal records cooperative replaces deployment: Set the tunnel to trust stale SAs indefinitely whenever the peer goes offline.
  4. For the legal records cooperative replaces 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 “Design redundant IPsec paths with measurable failover”, rather than the specific configuration or use described. The unsafe step in this case is to accept any self-presented peer certificate without checking its issuing trust chain or identity.

B.

Accept any self-presented peer certificate without checking its issuing trust chain or identity. The proposed shortcut bypasses the needed control: Certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key. The appropriate response is to install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication.

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 accept any self-presented peer certificate without checking its issuing trust chain or identity.

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 accept any self-presented peer certificate without checking its issuing trust chain or identity.

Question 595

A legal records cooperative replaces shared VPN secrets with certificate-authenticated peers across three offices. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the legal records cooperative replaces deployment: Implement: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. 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 legal records cooperative replaces 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 legal records cooperative replaces deployment: Implement: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. 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 legal records cooperative replaces 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: C

A.

This action and check address the alternate operation “For the legal records cooperative replaces deployment: Implement: Install valid CA trust and peer certificates with correct identity and…” instead of the stated acceptance requirement. The matching action is to install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. Its confirming test is to inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

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 install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. Its confirming test is to inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

C.

Implement: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. Verify: Inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA. This pairing is justified because certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

D.

This action and check address the alternate operation “For the legal records cooperative replaces deployment: Implement: Capture relevant IKE and IPsec diagnostic output for one peer while…” instead of the stated acceptance requirement. The matching action is to install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. Its confirming test is to inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

Question 596

A regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the regional public health network deployment: Tune supported dead peer detection and recovery behavior appropriate to a tunnel's expected intermittent connectivity.
  2. For the regional public health network deployment: Capture relevant IKE and IPsec diagnostic output for one peer while correlating phase-one, phase-two and policy failures.
  3. For the regional public health network 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 public health network 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: D

A.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. 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, certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

B.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. 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, certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

C.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. 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, certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

D.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. This resolves the issue because certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key. To verify, inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

Question 597

A regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. The engineer proposes this change: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the regional public health network deployment: Certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.
  2. For the regional public health network 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 regional public health network 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 public health network 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: A

A.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. Certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key. It supports this action: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. To confirm, inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

B.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. 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 certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

C.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. 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 certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

D.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. 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 certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

Question 598

A regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. After implementing this change—Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication—which test best establishes that the intended outcome is actually working?

  1. For the regional public health network deployment: Disconnect the remote peer briefly and observe DPD events, SA state change and successful renegotiation after connectivity returns.
  2. For the regional public health network 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 public health network deployment: Perform one controlled negotiation, examine timestamps and SA messages, then verify tunnel counters after the identified correction.
  4. For the regional public health network 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: B

A.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. This check would help evaluate the distinct objective “Use dead peer detection to clear broken sessions”, but not the required result. For this case, inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

B.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. Inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA. This is the relevant test because certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

C.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. This check would help evaluate the distinct objective “Use constrained IKE diagnostics to distinguish negotiation faults”, but not the required result. For this case, inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

D.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. This check would help evaluate the distinct objective “Design redundant IPsec paths with measurable failover”, but not the required result. For this case, inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

Question 599

A regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. Which proposed shortcut would most directly cause unauthorized or misidentified peers establishing or attempting protected tunnels, and therefore must be avoided for this requirement?

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

Answer & Explanations

Correct answer: C

A.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. 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 accept any self-presented peer certificate without checking its issuing trust chain or identity.

B.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. 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 accept any self-presented peer certificate without checking its issuing trust chain or identity.

C.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. Accept any self-presented peer certificate without checking its issuing trust chain or identity. The proposed shortcut bypasses the needed control: Certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key. The appropriate response is to install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication.

D.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. 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 accept any self-presented peer certificate without checking its issuing trust chain or identity.

Question 600

A regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the regional public health network 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.
  2. For the regional public health network deployment: Implement: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. 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 regional public health network 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.
  4. For the regional public health network deployment: Implement: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. 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: D

A.

This action and check address the alternate operation “For the regional public health network deployment: Implement: Capture relevant IKE and IPsec diagnostic output for one peer while…” instead of the stated acceptance requirement. The matching action is to install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. Its confirming test is to inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

B.

This action and check address the alternate operation “For the regional public health network deployment: Implement: Install valid CA trust and peer certificates with correct identity and…” instead of the stated acceptance requirement. The matching action is to install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. Its confirming test is to inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

C.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. 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 install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. Its confirming test is to inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA.

D.

The situation is that a regional public health network requires device identity validation before accepting a new clinic's site-to-site VPN. Implement: Install valid CA trust and peer certificates with correct identity and validity checks where the approved IPsec design uses certificate authentication. Verify: Inspect certificate chain, validity and peer ID during a controlled IKE negotiation, then verify only the approved peer establishes an SA. This pairing is justified because certificate-authenticated IKE validates peer identity through certificate trust and configured identities, not merely possession of a shared preshared key.

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