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 30

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.

Question 291

A regional archive must document exactly what its privacy-preserving TLS certificate checks can and cannot detect. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

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

Answer & Explanations

Correct answer: C

A.

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

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, certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

C.

Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. This resolves the issue because certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection. To verify, compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

D.

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, certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

Question 292

A regional archive must document exactly what its privacy-preserving TLS certificate checks can and cannot detect. The engineer proposes this change: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the regional archive 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 regional archive 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.
  3. For the regional archive 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 regional archive 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: D

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 certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

B.

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 certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

C.

That statement explains the distinct objective “Trust the CA used for deep SSL inspection” rather than the cause in this case. The deciding mechanism here is that certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

D.

Certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection. It supports this action: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. To confirm, compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

Question 293

A regional archive must document exactly what its privacy-preserving TLS certificate checks can and cannot detect. After implementing this change—Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads—which test best establishes that the intended outcome is actually working?

  1. For the regional archive deployment: Compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.
  2. For the regional archive deployment: Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.
  3. For the regional archive deployment: Access approved test sites in allowed and blocked categories, then correlate resulting web-filter events with the policy and rating.
  4. For the regional archive 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: A

A.

Compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear. This is the relevant test because certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

B.

This check would help evaluate the distinct objective “Scope exceptions for certificate-pinned applications”, but not the required result. For this case, compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

C.

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, compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

D.

This check would help evaluate the distinct objective “Trust the CA used for deep SSL inspection”, but not the required result. For this case, compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

Question 294

A regional archive must document exactly what its privacy-preserving TLS certificate checks can and cannot detect. Which proposed shortcut would most directly cause false assurance that hidden application content has been inspected, and therefore must be avoided for this requirement?

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

Answer & Explanations

Correct answer: B

A.

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 claim that certificate inspection alone scans the entire encrypted download payload.

B.

Claim that certificate inspection alone scans the entire encrypted download payload. The proposed shortcut bypasses the needed control: Certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection. The appropriate response is to use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads.

C.

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 claim that certificate inspection alone scans the entire encrypted download payload.

D.

That shortcut would relate to the distinct objective “Trust the CA used for deep SSL inspection”, rather than the specific configuration or use described. The unsafe step in this case is to claim that certificate inspection alone scans the entire encrypted download payload.

Question 295

A regional archive must document exactly what its privacy-preserving TLS certificate checks can and cannot detect. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the regional archive deployment: Implement: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Verify: Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.
  2. For the regional archive 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 regional archive deployment: Implement: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Verify: Compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.
  4. For the regional archive deployment: Implement: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Verify: 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 action and check address the alternate operation “For the regional archive 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 certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Its confirming test is to compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

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 certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Its confirming test is to compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

C.

Implement: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Verify: Compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear. This pairing is justified because certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

D.

This action and check address the alternate operation “For the regional archive 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 certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Its confirming test is to compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

Question 296

A legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the legal services provider deployment: Configure a web-filter profile with required FortiGuard category actions and attach it to the policy used by client traffic.
  2. For the legal services provider deployment: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy.
  3. For the legal services provider deployment: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls.
  4. For the legal services 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: D

A.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. 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, certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

B.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. This option addresses the distinct objective “Trust the CA used for deep SSL inspection”, not the immediate requirement. Full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections. For the stated case, certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

C.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. 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, certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

D.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. This resolves the issue because certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection. To verify, compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

Question 297

A legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. The engineer proposes this change: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the legal services 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.
  2. For the legal services 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.
  3. For the legal services provider 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 legal services 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.

Answer & Explanations

Correct answer: A

A.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. Certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection. It supports this action: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. To confirm, compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

B.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. 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 certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

C.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. That statement explains the distinct objective “Trust the CA used for deep SSL inspection” rather than the cause in this case. The deciding mechanism here is that certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

D.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. 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 certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

Question 298

A legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. After implementing this change—Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads—which test best establishes that the intended outcome is actually working?

  1. For the legal services provider deployment: Access approved test sites in allowed and blocked categories, then correlate resulting web-filter events with the policy and rating.
  2. For the legal services provider deployment: Compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.
  3. For the legal services 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 legal services provider deployment: Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

Answer & Explanations

Correct answer: B

A.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. 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, compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

B.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. Compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear. This is the relevant test because certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

C.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. This check would help evaluate the distinct objective “Trust the CA used for deep SSL inspection”, but not the required result. For this case, compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

D.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. This check would help evaluate the distinct objective “Scope exceptions for certificate-pinned applications”, but not the required result. For this case, compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

Question 299

A legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. Which proposed shortcut would most directly cause false assurance that hidden application content has been inspected, and therefore must be avoided for this requirement?

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

Answer & Explanations

Correct answer: C

A.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. 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 claim that certificate inspection alone scans the entire encrypted download payload.

B.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. That shortcut would relate to the distinct objective “Trust the CA used for deep SSL inspection”, rather than the specific configuration or use described. The unsafe step in this case is to claim that certificate inspection alone scans the entire encrypted download payload.

C.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. Claim that certificate inspection alone scans the entire encrypted download payload. The proposed shortcut bypasses the needed control: Certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection. The appropriate response is to use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads.

D.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. 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 claim that certificate inspection alone scans the entire encrypted download payload.

Question 300

A legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the legal services provider deployment: Implement: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy. Verify: Compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.
  2. For the legal services provider deployment: Implement: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Verify: Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.
  3. For the legal services 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.
  4. For the legal services provider deployment: Implement: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Verify: Compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

Answer & Explanations

Correct answer: D

A.

This action and check address the alternate operation “For the legal services provider 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 certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Its confirming test is to compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

B.

This action and check address the alternate operation “For the legal services provider 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 certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Its confirming test is to compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

C.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. 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 certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Its confirming test is to compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.

D.

The situation is that a legal services provider sees no URL path details in certificate-only logs and needs to understand the visibility limit. Implement: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads. Verify: Compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear. This pairing is justified because certificate inspection evaluates visible handshake and certificate attributes without decrypting application content, so it cannot supply the same payload visibility as full inspection.

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