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 35

Question 340

A design agency migrated a policy from proxy to flow and lost a particular URL-filtering behavior. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the design agency migrated a policy from proxy to flow and deployment: Implement: Match the supported flow-based or proxy-based inspection mode to the web-filter feature set and performance constraints. Verify: Repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.
  2. For the design agency migrated a policy from proxy to flow and 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 design agency migrated a policy from proxy to flow and deployment: Implement: Use a narrowly scoped URL filter entry and verify its action and order relative to FortiGuard category filtering. Verify: Confirm the requested web-filter action appears in the configured mode and reproduce its result on a controlled test URL.
  4. For the design agency migrated a policy from proxy to flow and deployment: Implement: Match the supported flow-based or proxy-based inspection mode to the web-filter feature set and performance constraints. Verify: Confirm the requested web-filter action appears in the configured mode and reproduce its result on a controlled test URL.

Answer & Explanations

Correct answer: D

A.

This action and check address the alternate operation “For the design agency migrated a policy from proxy to flow and deployment: Implement: Match the supported flow-based or…” instead of the stated acceptance requirement. The matching action is to match the supported flow-based or proxy-based inspection mode to the web-filter feature set and performance constraints. Its confirming test is to confirm the requested web-filter action appears in the configured mode and reproduce its result on a controlled test URL.

B.

The situation is that a design agency migrated a policy from proxy to flow and lost a particular URL-filtering behavior. 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 match the supported flow-based or proxy-based inspection mode to the web-filter feature set and performance constraints. Its confirming test is to confirm the requested web-filter action appears in the configured mode and reproduce its result on a controlled test URL.

C.

This action and check address the alternate operation “For the design agency migrated a policy from proxy to flow and deployment: Implement: Use a narrowly scoped URL…” instead of the stated acceptance requirement. The matching action is to match the supported flow-based or proxy-based inspection mode to the web-filter feature set and performance constraints. Its confirming test is to confirm the requested web-filter action appears in the configured mode and reproduce its result on a controlled test URL.

D.

The situation is that a design agency migrated a policy from proxy to flow and lost a particular URL-filtering behavior. Implement: Match the supported flow-based or proxy-based inspection mode to the web-filter feature set and performance constraints. Verify: Confirm the requested web-filter action appears in the configured mode and reproduce its result on a controlled test URL. This pairing is justified because not every proxy-only or flow-specific inspection behavior is identical, and the chosen policy inspection mode affects the available filtering actions.

Question 341

A county library reports a legitimate tax website blocked after a rating update and needs a narrow evidence-led fix. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the county library deployment: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions.
  2. For the county library deployment: Use a narrowly scoped URL filter entry and verify its action and order relative to FortiGuard category filtering.
  3. For the county library deployment: Configure a web-filter profile with required FortiGuard category actions and attach it to the policy used by client traffic.
  4. For the county library deployment: Match the supported flow-based or proxy-based inspection mode to the web-filter feature set and performance constraints.

Answer & Explanations

Correct answer: A

A.

Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. This resolves the issue because a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision. To verify, repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

B.

This option addresses the distinct objective “Handle explicit URL exceptions with precise precedence”, not the immediate requirement. URL-specific rules and broader category actions interact through profile settings and evaluation precedence; an overly broad wildcard can override intended controls. For the stated case, a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

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, a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

D.

This option addresses the distinct objective “Choose flow or proxy inspection for required web-filter capability”, not the immediate requirement. Not every proxy-only or flow-specific inspection behavior is identical, and the chosen policy inspection mode affects the available filtering actions. For the stated case, a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

Question 342

A county library reports a legitimate tax website blocked after a rating update and needs a narrow evidence-led fix. The engineer proposes this change: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the county library deployment: URL-specific rules and broader category actions interact through profile settings and evaluation precedence; an overly broad wildcard can override intended controls.
  2. For the county library deployment: A blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.
  3. For the county library 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 county library deployment: Not every proxy-only or flow-specific inspection behavior is identical, and the chosen policy inspection mode affects the available filtering actions.

Answer & Explanations

Correct answer: B

A.

That statement explains the distinct objective “Handle explicit URL exceptions with precise precedence” rather than the cause in this case. The deciding mechanism here is that a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

B.

A blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision. It supports this action: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. To confirm, repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

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 a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

D.

That statement explains the distinct objective “Choose flow or proxy inspection for required web-filter capability” rather than the cause in this case. The deciding mechanism here is that a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

Question 343

A county library reports a legitimate tax website blocked after a rating update and needs a narrow evidence-led fix. After implementing this change—Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions—which test best establishes that the intended outcome is actually working?

  1. For the county library deployment: Test the exact hostname and a neighboring disallowed hostname, checking matched URL-filter and category events separately.
  2. For the county library deployment: Access approved test sites in allowed and blocked categories, then correlate resulting web-filter events with the policy and rating.
  3. For the county library deployment: Repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.
  4. For the county library deployment: Confirm the requested web-filter action appears in the configured mode and reproduce its result on a controlled test URL.

Answer & Explanations

Correct answer: C

A.

This check would help evaluate the distinct objective “Handle explicit URL exceptions with precise precedence”, but not the required result. For this case, repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

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, repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

C.

Repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny. This is the relevant test because a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

D.

This check would help evaluate the distinct objective “Choose flow or proxy inspection for required web-filter capability”, but not the required result. For this case, repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

Question 344

A county library reports a legitimate tax website blocked after a rating update and needs a narrow evidence-led fix. Which proposed shortcut would most directly cause silent broadening of browsing access while the real classification issue remains, and therefore must be avoided for this requirement?

  1. For the county library deployment: Change global rating labels without applying any web-filter profile to the actual policy.
  2. For the county library deployment: Copy a proxy-specific filtering setting into flow mode and assume feature parity.
  3. For the county library deployment: Allow every domain containing a common word just to rescue one business application.
  4. For the county library deployment: Globally permit all uncategorized or newly rated sites before checking the blocked site's category.

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 globally permit all uncategorized or newly rated sites before checking the blocked site's category.

B.

That shortcut would relate to the distinct objective “Choose flow or proxy inspection for required web-filter capability”, rather than the specific configuration or use described. The unsafe step in this case is to globally permit all uncategorized or newly rated sites before checking the blocked site's category.

C.

That shortcut would relate to the distinct objective “Handle explicit URL exceptions with precise precedence”, rather than the specific configuration or use described. The unsafe step in this case is to globally permit all uncategorized or newly rated sites before checking the blocked site's category.

D.

Globally permit all uncategorized or newly rated sites before checking the blocked site's category. The proposed shortcut bypasses the needed control: A blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision. The appropriate response is to inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions.

Question 345

A county library reports a legitimate tax website blocked after a rating update and needs a narrow evidence-led fix. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the county library deployment: Implement: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. Verify: Repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.
  2. For the county library 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 county library deployment: Implement: Match the supported flow-based or proxy-based inspection mode to the web-filter feature set and performance constraints. Verify: Repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.
  4. For the county library deployment: Implement: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. Verify: Test the exact hostname and a neighboring disallowed hostname, checking matched URL-filter and category events separately.

Answer & Explanations

Correct answer: A

A.

Implement: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. Verify: Repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny. This pairing is justified because a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

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 inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. Its confirming test is to repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

C.

This action and check address the alternate operation “For the county library deployment: Implement: Match the supported flow-based or proxy-based inspection mode to the web-filter feature set…” instead of the stated acceptance requirement. The matching action is to inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. Its confirming test is to repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

D.

This action and check address the alternate operation “For the county library deployment: Implement: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match…” instead of the stated acceptance requirement. The matching action is to inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. Its confirming test is to repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

Question 346

A campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the campus researcher deployment: Configure a web-filter profile with required FortiGuard category actions and attach it to the policy used by client traffic.
  2. For the campus researcher deployment: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions.
  3. For the campus researcher deployment: Match the supported flow-based or proxy-based inspection mode to the web-filter feature set and performance constraints.
  4. For the campus researcher deployment: Use a narrowly scoped URL filter entry and verify its action and order relative to FortiGuard category filtering.

Answer & Explanations

Correct answer: B

A.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. 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, a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

B.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. This resolves the issue because a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision. To verify, repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

C.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. This option addresses the distinct objective “Choose flow or proxy inspection for required web-filter capability”, not the immediate requirement. Not every proxy-only or flow-specific inspection behavior is identical, and the chosen policy inspection mode affects the available filtering actions. For the stated case, a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

D.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. This option addresses the distinct objective “Handle explicit URL exceptions with precise precedence”, not the immediate requirement. URL-specific rules and broader category actions interact through profile settings and evaluation precedence; an overly broad wildcard can override intended controls. For the stated case, a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

Question 347

A campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. The engineer proposes this change: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the campus researcher 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 campus researcher deployment: Not every proxy-only or flow-specific inspection behavior is identical, and the chosen policy inspection mode affects the available filtering actions.
  3. For the campus researcher deployment: A blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.
  4. For the campus researcher deployment: URL-specific rules and broader category actions interact through profile settings and evaluation precedence; an overly broad wildcard can override intended controls.

Answer & Explanations

Correct answer: C

A.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. 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 a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

B.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. That statement explains the distinct objective “Choose flow or proxy inspection for required web-filter capability” rather than the cause in this case. The deciding mechanism here is that a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

C.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. A blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision. It supports this action: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. To confirm, repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

D.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. That statement explains the distinct objective “Handle explicit URL exceptions with precise precedence” rather than the cause in this case. The deciding mechanism here is that a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

Question 348

A campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. After implementing this change—Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions—which test best establishes that the intended outcome is actually working?

  1. For the campus researcher deployment: Confirm the requested web-filter action appears in the configured mode and reproduce its result on a controlled test URL.
  2. For the campus researcher deployment: Test the exact hostname and a neighboring disallowed hostname, checking matched URL-filter and category events separately.
  3. For the campus researcher deployment: Access approved test sites in allowed and blocked categories, then correlate resulting web-filter events with the policy and rating.
  4. For the campus researcher deployment: Repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

Answer & Explanations

Correct answer: D

A.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. This check would help evaluate the distinct objective “Choose flow or proxy inspection for required web-filter capability”, but not the required result. For this case, repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

B.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. This check would help evaluate the distinct objective “Handle explicit URL exceptions with precise precedence”, but not the required result. For this case, repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

C.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. 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, repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

D.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. Repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny. This is the relevant test because a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

Question 349

A campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. Which proposed shortcut would most directly cause silent broadening of browsing access while the real classification issue remains, and therefore must be avoided for this requirement?

  1. For the campus researcher deployment: Globally permit all uncategorized or newly rated sites before checking the blocked site's category.
  2. For the campus researcher deployment: Copy a proxy-specific filtering setting into flow mode and assume feature parity.
  3. For the campus researcher deployment: Allow every domain containing a common word just to rescue one business application.
  4. For the campus researcher 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 campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. Globally permit all uncategorized or newly rated sites before checking the blocked site's category. The proposed shortcut bypasses the needed control: A blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision. The appropriate response is to inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions.

B.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. That shortcut would relate to the distinct objective “Choose flow or proxy inspection for required web-filter capability”, rather than the specific configuration or use described. The unsafe step in this case is to globally permit all uncategorized or newly rated sites before checking the blocked site's category.

C.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. That shortcut would relate to the distinct objective “Handle explicit URL exceptions with precise precedence”, rather than the specific configuration or use described. The unsafe step in this case is to globally permit all uncategorized or newly rated sites before checking the blocked site's category.

D.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. 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 globally permit all uncategorized or newly rated sites before checking the blocked site's category.

Question 350

A campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the campus researcher deployment: Implement: Match the supported flow-based or proxy-based inspection mode to the web-filter feature set and performance constraints. Verify: Repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.
  2. For the campus researcher deployment: Implement: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. Verify: Repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.
  3. For the campus researcher deployment: Implement: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. Verify: Test the exact hostname and a neighboring disallowed hostname, checking matched URL-filter and category events separately.
  4. For the campus researcher 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 campus researcher deployment: Implement: Match the supported flow-based or proxy-based inspection mode to the web-filter feature set…” instead of the stated acceptance requirement. The matching action is to inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. Its confirming test is to repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

B.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. Implement: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. Verify: Repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny. This pairing is justified because a blocked site may be denied by category, explicit URL entry or failed rating behavior; the log and rating context identify the real decision.

C.

This action and check address the alternate operation “For the campus researcher deployment: Implement: Inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match…” instead of the stated acceptance requirement. The matching action is to inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. Its confirming test is to repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

D.

The situation is that a campus researcher cannot reach a journal archive and the firewall shows a web-filter deny with an unexpected category. 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 inspect the matching web-filter log, FortiGuard category lookup, local overrides and URL-filter match before changing actions. Its confirming test is to repeat a controlled request and confirm the displayed category, applied rule and profile action explain the observed deny.

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