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 31

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.

Question 301

A pharmacy uses a vendor app with certificate pinning that breaks under otherwise valid deep-inspection policy. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the pharmacy uses deployment: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls.
  2. For the pharmacy uses deployment: Use certificate inspection when checking TLS certificate metadata is sufficient, and do not claim it reads encrypted HTTP payloads.
  3. For the pharmacy uses deployment: Use a supported full SSL inspection profile with an inspection CA trusted by managed endpoints and appropriately scoped policy.
  4. For the pharmacy uses 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: A

A.

Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. This resolves the issue because certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured. To verify, reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

B.

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, certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

C.

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-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

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-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

Question 302

A pharmacy uses a vendor app with certificate pinning that breaks under otherwise valid deep-inspection policy. The engineer proposes this change: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the pharmacy uses 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 pharmacy uses deployment: Certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.
  3. For the pharmacy uses 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 pharmacy uses 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.

Answer & Explanations

Correct answer: B

A.

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 certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

B.

Certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured. It supports this action: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. To confirm, reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

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-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

D.

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-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

Question 303

A pharmacy uses a vendor app with certificate pinning that breaks under otherwise valid deep-inspection policy. After implementing this change—Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls—which test best establishes that the intended outcome is actually working?

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

Answer & Explanations

Correct answer: C

A.

This check would help evaluate the distinct objective “Understand the limits of certificate-only inspection”, but not the required result. For this case, reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

B.

This check would help evaluate the distinct objective “Trust the CA used for deep SSL inspection”, but not the required result. For this case, reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

C.

Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected. This is the relevant test because certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

D.

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, reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

Question 304

A pharmacy uses a vendor app with certificate pinning that breaks under otherwise valid deep-inspection policy. Which proposed shortcut would most directly cause loss of broad encrypted-traffic inspection for unrelated applications, and therefore must be avoided for this requirement?

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

Answer & Explanations

Correct answer: D

A.

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 disable SSL inspection globally after one pinned client stops connecting.

B.

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 disable SSL inspection globally after one pinned client stops connecting.

C.

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 disable SSL inspection globally after one pinned client stops connecting.

D.

Disable SSL inspection globally after one pinned client stops connecting. The proposed shortcut bypasses the needed control: Certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured. The appropriate response is to identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls.

Question 305

A pharmacy uses a vendor app with certificate pinning that breaks under otherwise valid deep-inspection policy. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the pharmacy uses deployment: Implement: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. Verify: Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.
  2. For the pharmacy uses deployment: Implement: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. 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 pharmacy uses 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 pharmacy uses 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.

Answer & Explanations

Correct answer: A

A.

Implement: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. Verify: Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected. This pairing is justified because certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

B.

This action and check address the alternate operation “For the pharmacy uses deployment: Implement: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with…” instead of the stated acceptance requirement. The matching action is to identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. Its confirming test is to reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

C.

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 identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. Its confirming test is to reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

D.

This action and check address the alternate operation “For the pharmacy uses 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 identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. Its confirming test is to reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

Question 306

A field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

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

Answer & Explanations

Correct answer: B

A.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. 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-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

B.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. This resolves the issue because certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured. To verify, reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

C.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. 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-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

D.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. 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, certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

Question 307

A field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. The engineer proposes this change: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the field-service tablet application fails deployment: Full SSL inspection establishes a new TLS session toward clients, so browsers must trust the issuing inspection CA for inspected connections.
  2. For the field-service tablet application fails 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 field-service tablet application fails deployment: Certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.
  4. For the field-service tablet application fails 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: C

A.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. 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-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

B.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. 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-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

C.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. Certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured. It supports this action: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. To confirm, reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

D.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. 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 certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

Question 308

A field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. After implementing this change—Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls—which test best establishes that the intended outcome is actually working?

  1. For the field-service tablet application fails deployment: Access approved test sites in allowed and blocked categories, then correlate resulting web-filter events with the policy and rating.
  2. For the field-service tablet application fails deployment: Compare a certificate-only test with a controlled full-inspection test and observe which application-layer events appear.
  3. For the field-service tablet application fails 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 field-service tablet application fails 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: D

A.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. 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, reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

B.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. This check would help evaluate the distinct objective “Understand the limits of certificate-only inspection”, but not the required result. For this case, reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

C.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. This check would help evaluate the distinct objective “Trust the CA used for deep SSL inspection”, but not the required result. For this case, reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

D.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected. This is the relevant test because certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

Question 309

A field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. Which proposed shortcut would most directly cause loss of broad encrypted-traffic inspection for unrelated applications, and therefore must be avoided for this requirement?

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

Answer & Explanations

Correct answer: A

A.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. Disable SSL inspection globally after one pinned client stops connecting. The proposed shortcut bypasses the needed control: Certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured. The appropriate response is to identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls.

B.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. 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 disable SSL inspection globally after one pinned client stops connecting.

C.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. 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 disable SSL inspection globally after one pinned client stops connecting.

D.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. 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 disable SSL inspection globally after one pinned client stops connecting.

Question 310

A field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the field-service tablet application fails 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.
  2. For the field-service tablet application fails deployment: Implement: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. Verify: Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.
  3. For the field-service tablet application fails 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.
  4. For the field-service tablet application fails deployment: Implement: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. Verify: 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: B

A.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. 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 identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. Its confirming test is to reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

B.

The situation is that a field-service tablet application fails only when a TLS-inspection rule intercepts its API endpoint. Implement: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. Verify: Reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected. This pairing is justified because certificate-pinned clients verify expected peer keys or chains and may reject a TLS interception proxy even when ordinary browser trust was configured.

C.

This action and check address the alternate operation “For the field-service tablet application fails deployment: Implement: Use certificate inspection when checking TLS certificate metadata is sufficient, and…” instead of the stated acceptance requirement. The matching action is to identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. Its confirming test is to reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

D.

This action and check address the alternate operation “For the field-service tablet application fails deployment: Implement: Identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection…” instead of the stated acceptance requirement. The matching action is to identify confirmed certificate-pinning or mutual-TLS incompatibility and apply narrowly targeted deep-inspection exemptions with compensating controls. Its confirming test is to reproduce the failing application, verify its TLS cause, then retest a destination-scoped exception while normal inspected sites remain inspected.

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