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 29

Question 280

A regional bank can ping the collector but staff group rules no longer match following a domain trust change. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the regional bank deployment: Implement: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Verify: Perform a domain login and observe the resulting user-IP-group mapping in the collector and FortiGate before testing the identity rule.
  2. For the regional bank deployment: Implement: Choose a supported active login or captive-portal method for users not already identified by a reliable passive single sign-on source. Verify: Test a new unmanaged endpoint and verify the presented login, authenticated user and resulting allowed policy; repeat with an unauthenticated endpoint.
  3. For the regional bank deployment: Implement: Inspect FSSO learned user, source address, group membership and logoff aging when a correct domain user unexpectedly misses a rule. Verify: Correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.
  4. For the regional bank deployment: Implement: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Verify: Correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.

Answer & Explanations

Correct answer: D

A.

This action and check address the alternate operation “For the regional bank deployment: Implement: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly…” instead of the stated acceptance requirement. The matching action is to compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Its confirming test is to correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.

B.

The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. This action and check address the distinct objective “Use active authentication when passive identity is unavailable” instead of the stated acceptance requirement. The matching action is to compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Its confirming test is to correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.

C.

This action and check address the alternate operation “For the regional bank deployment: Implement: Inspect FSSO learned user, source address, group membership and logoff aging when a…” instead of the stated acceptance requirement. The matching action is to compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Its confirming test is to correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector.

D.

The situation is that a regional bank can ping the collector but staff group rules no longer match following a domain trust change. Implement: Compare collector connectivity, logon events and allowed identity groups before adding a narrowly justified fallback authentication path. Verify: Correlate a timed sign-in event with collected identity and FortiGate policy match, then retest after repairing the connector. This pairing is justified because FSSO group misses may reflect identity-collection failures rather than network reachability; a broad unauthenticated bypass hides that distinction.

Question 281

A healthcare provider wants malware inspection of managed clinical workstations' encrypted web sessions without user certificate alerts. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the healthcare provider deployment: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy.
  2. For the healthcare provider deployment: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls.
  3. For the healthcare provider deployment: Configure a web-filter profile with required FortiGuard category actions and attach it to the policy used by client traffic.
  4. For the healthcare provider deployment: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads.

Answer & Explanations

Correct answer: A

A.

Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. This resolves the issue because full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections. To verify, on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

B.

This option addresses the distinct objective “Scope exceptions for certificate-pinned applications”, not the immediate requirement. Certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured. For the stated case, full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

C.

This option addresses the distinct objective “Apply FortiGuard category filtering through the matching web profile”, not the immediate requirement. Category rating enforcement requires both a valid rating result and the profile running on the matching firewall policy; categories alone do not block traffic. For the stated case, full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

D.

This option addresses the distinct objective “Understand the limits of certificate-only inspection”, not the immediate requirement. Certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection. For the stated case, full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

Question 282

A healthcare provider wants malware inspection of managed clinical workstations' encrypted web sessions without user certificate alerts. The engineer proposes this change: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the healthcare provider deployment: Certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.
  2. For the healthcare provider deployment: Full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.
  3. For the healthcare provider deployment: Category rating enforcement requires both a valid rating result and the profile running on the matching firewall policy; categories alone do not block traffic.
  4. For the healthcare provider deployment: Certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

Answer & Explanations

Correct answer: B

A.

That statement explains the distinct objective “Scope exceptions for certificate-pinned applications” rather than the cause in this case. The deciding mechanism here is that full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

B.

Full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections. It supports this action: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. To confirm, on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

C.

That statement explains the distinct objective “Apply FortiGuard category filtering through the matching web profile” rather than the cause in this case. The deciding mechanism here is that full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

D.

That statement explains the distinct objective “Understand the limits of certificate-only inspection” rather than the cause in this case. The deciding mechanism here is that full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

Question 283

A healthcare provider wants malware inspection of managed clinical workstations' encrypted web sessions without user certificate alerts. After implementing this change—Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy—which test best establishes that the intended outcome is actually working?

  1. For the healthcare provider deployment: Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.
  2. For the healthcare provider deployment: Access approved test sites in allowed and blocked categories, then correlate resulting web-filter events with the policy and rating.
  3. For the healthcare provider deployment: On a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.
  4. For the healthcare provider deployment: Compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

Answer & Explanations

Correct answer: C

A.

This check would help evaluate the distinct objective “Scope exceptions for certificate-pinned applications”, but not the required result. For this case, on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

B.

This check would help evaluate the distinct objective “Apply FortiGuard category filtering through the matching web profile”, but not the required result. For this case, on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

C.

On a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile. This is the relevant test because full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

D.

This check would help evaluate the distinct objective “Understand the limits of certificate-only inspection”, but not the required result. For this case, on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

Question 284

A healthcare provider wants malware inspection of managed clinical workstations' encrypted web sessions without user certificate alerts. Which proposed shortcut would most directly cause certificate warnings and broken TLS sessions on otherwise legitimate sites, and therefore must be avoided for this requirement?

  1. For the healthcare provider deployment: Change global rating labels without applying any web-filter profile to the actual policy.
  2. For the healthcare provider deployment: Claim that certificate inspection alone scans the entire encrypted download payload.
  3. For the healthcare provider deployment: Disable SSL inspection globally after one pinned client stops connecting.
  4. For the healthcare provider deployment: Enable deep inspection without distributing or trusting the FortiGate inspection CA.

Answer & Explanations

Correct answer: D

A.

That shortcut would relate to the distinct objective “Apply FortiGuard category filtering through the matching web profile”, rather than the specific configuration or use described. The unsafe step in this case is to enable deep inspection without distributing or trusting the FortiGate inspection CA.

B.

That shortcut would relate to the distinct objective “Understand the limits of certificate-only inspection”, rather than the specific configuration or use described. The unsafe step in this case is to enable deep inspection without distributing or trusting the FortiGate inspection CA.

C.

That shortcut would relate to the distinct objective “Scope exceptions for certificate-pinned applications”, rather than the specific configuration or use described. The unsafe step in this case is to enable deep inspection without distributing or trusting the FortiGate inspection CA.

D.

Enable deep inspection without distributing or trusting the FortiGate inspection CA. The proposed shortcut bypasses the needed control: Full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections. The appropriate response is to use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy.

Question 285

A healthcare provider wants malware inspection of managed clinical workstations' encrypted web sessions without user certificate alerts. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the healthcare provider deployment: Implement: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Verify: On a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.
  2. For the healthcare provider deployment: Implement: Configure a web-filter profile with required FortiGuard category actions and attach it to the policy used by client traffic. Verify: Access approved test sites in allowed and blocked categories, then correlate resulting web-filter events with the policy and rating.
  3. For the healthcare provider deployment: Implement: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Verify: On a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.
  4. For the healthcare provider deployment: Implement: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Verify: Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

Answer & Explanations

Correct answer: A

A.

Implement: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Verify: On a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile. This pairing is justified because full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

B.

This action and check address the distinct objective “Apply FortiGuard category filtering through the matching web profile” instead of the stated acceptance requirement. The matching action is to use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Its confirming test is to on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

C.

This action and check address the alternate operation “For the healthcare provider deployment: Implement: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not…” instead of the stated acceptance requirement. The matching action is to use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Its confirming test is to on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

D.

This action and check address the alternate operation “For the healthcare provider deployment: Implement: Use a supported full SSL inspection profile with an inspection CA trusted by…” instead of the stated acceptance requirement. The matching action is to use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Its confirming test is to on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

Question 286

A finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the finance training lab deployment: Configure a web-filter profile with required FortiGuard category actions and attach it to the policy used by client traffic.
  2. For the finance training lab deployment: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy.
  3. For the finance training lab deployment: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads.
  4. For the finance training lab deployment: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls.

Answer & Explanations

Correct answer: B

A.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. This option addresses the distinct objective “Apply FortiGuard category filtering through the matching web profile”, not the immediate requirement. Category rating enforcement requires both a valid rating result and the profile running on the matching firewall policy; categories alone do not block traffic. For the stated case, full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

B.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. This resolves the issue because full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections. To verify, on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

C.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. This option addresses the distinct objective “Understand the limits of certificate-only inspection”, not the immediate requirement. Certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection. For the stated case, full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

D.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. This option addresses the distinct objective “Scope exceptions for certificate-pinned applications”, not the immediate requirement. Certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured. For the stated case, full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

Question 287

A finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. The engineer proposes this change: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the finance training lab deployment: Category rating enforcement requires both a valid rating result and the profile running on the matching firewall policy; categories alone do not block traffic.
  2. For the finance training lab deployment: Certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.
  3. For the finance training lab deployment: Full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.
  4. For the finance training lab deployment: Certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

Answer & Explanations

Correct answer: C

A.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. That statement explains the distinct objective “Apply FortiGuard category filtering through the matching web profile” rather than the cause in this case. The deciding mechanism here is that full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

B.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. That statement explains the distinct objective “Understand the limits of certificate-only inspection” rather than the cause in this case. The deciding mechanism here is that full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

C.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. Full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections. It supports this action: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. To confirm, on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

D.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. That statement explains the distinct objective “Scope exceptions for certificate-pinned applications” rather than the cause in this case. The deciding mechanism here is that full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

Question 288

A finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. After implementing this change—Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy—which test best establishes that the intended outcome is actually working?

  1. For the finance training lab deployment: Compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.
  2. For the finance training lab deployment: Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.
  3. For the finance training lab deployment: Access approved test sites in allowed and blocked categories, then correlate resulting web-filter events with the policy and rating.
  4. For the finance training lab deployment: On a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

Answer & Explanations

Correct answer: D

A.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. This check would help evaluate the distinct objective “Understand the limits of certificate-only inspection”, but not the required result. For this case, on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

B.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. This check would help evaluate the distinct objective “Scope exceptions for certificate-pinned applications”, but not the required result. For this case, on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

C.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. This check would help evaluate the distinct objective “Apply FortiGuard category filtering through the matching web profile”, but not the required result. For this case, on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

D.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. On a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile. This is the relevant test because full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

Question 289

A finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. Which proposed shortcut would most directly cause certificate warnings and broken TLS sessions on otherwise legitimate sites, and therefore must be avoided for this requirement?

  1. For the finance training lab deployment: Enable deep inspection without distributing or trusting the FortiGate inspection CA.
  2. For the finance training lab deployment: Claim that certificate inspection alone scans the entire encrypted download payload.
  3. For the finance training lab deployment: Disable SSL inspection globally after one pinned client stops connecting.
  4. For the finance training lab deployment: Change global rating labels without applying any web-filter profile to the actual policy.

Answer & Explanations

Correct answer: A

A.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. Enable deep inspection without distributing or trusting the FortiGate inspection CA. The proposed shortcut bypasses the needed control: Full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections. The appropriate response is to use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy.

B.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. That shortcut would relate to the distinct objective “Understand the limits of certificate-only inspection”, rather than the specific configuration or use described. The unsafe step in this case is to enable deep inspection without distributing or trusting the FortiGate inspection CA.

C.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. That shortcut would relate to the distinct objective “Scope exceptions for certificate-pinned applications”, rather than the specific configuration or use described. The unsafe step in this case is to enable deep inspection without distributing or trusting the FortiGate inspection CA.

D.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. That shortcut would relate to the distinct objective “Apply FortiGuard category filtering through the matching web profile”, rather than the specific configuration or use described. The unsafe step in this case is to enable deep inspection without distributing or trusting the FortiGate inspection CA.

Question 290

A finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the finance training lab deployment: Implement: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Verify: On a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.
  2. For the finance training lab deployment: Implement: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Verify: On a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.
  3. For the finance training lab deployment: Implement: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Verify: Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.
  4. For the finance training lab deployment: Implement: Configure a web-filter profile with required FortiGuard category actions and attach it to the policy used by client traffic. Verify: Access approved test sites in allowed and blocked categories, then correlate resulting web-filter events with the policy and rating.

Answer & Explanations

Correct answer: B

A.

This action and check address the alternate operation “For the finance training lab deployment: Implement: Use certificate inspection when checking TLS certificate metadata is sufficient, and do…” instead of the stated acceptance requirement. The matching action is to use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Its confirming test is to on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

B.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. Implement: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Verify: On a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile. This pairing is justified because full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.

C.

This action and check address the alternate operation “For the finance training lab deployment: Implement: Use a supported full SSL inspection profile with an inspection CA trusted…” instead of the stated acceptance requirement. The matching action is to use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Its confirming test is to on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

D.

The situation is that a finance training lab introduces deep HTTPS inspection and observes browser certificate-chain warnings on employee laptops. This action and check address the distinct objective “Apply FortiGuard category filtering through the matching web profile” instead of the stated acceptance requirement. The matching action is to use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Its confirming test is to on a managed test endpoint validate the presented certificate chain and confirm a harmless security test is visible under the inspection profile.

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