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 4

Question 30

A research center is moving guest devices off an old router and must preserve fixed addresses reserved for network printers. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the research center deployment: Implement: Enable the FortiGate DHCP server on the intended LAN interface with a scoped pool, correct gateway and DNS values, and excluded static addresses. Verify: From an approved management station open the GUI or SSH, then verify the same login attempt is rejected from a nontrusted subnet.
  2. For the research center deployment: Implement: Enable the FortiGate DHCP server on the intended LAN interface with a scoped pool, correct gateway and DNS values, and excluded static addresses. Verify: Lease a test device on the target VLAN, inspect the allocated address, default gateway and DNS, and check the FortiGate lease table.
  3. For the research center deployment: Implement: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Verify: Generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.
  4. For the research center deployment: Implement: Register the FortiGate and verify applicable FortiGuard subscriptions and update connectivity before relying on licensed security services. Verify: Lease a test device on the target VLAN, inspect the allocated address, default gateway and DNS, and check the FortiGate lease table.

Answer & Explanations

Correct answer: B

A.

This action and check address the alternate operation “For the research center deployment: Implement: Enable the FortiGate DHCP server on the intended LAN interface with a scoped…” instead of the stated acceptance requirement. The matching action is to enable the FortiGate DHCP server on the intended LAN interface with a scoped pool, correct gateway and DNS values, and excluded static addresses. Its confirming test is to lease a test device on the target VLAN, inspect the allocated address, default gateway and DNS, and check the FortiGate lease table.

B.

The situation is that a research center is moving guest devices off an old router and must preserve fixed addresses reserved for network printers. Implement: Enable the FortiGate DHCP server on the intended LAN interface with a scoped pool, correct gateway and DNS values, and excluded static addresses. Verify: Lease a test device on the target VLAN, inspect the allocated address, default gateway and DNS, and check the FortiGate lease table. This pairing is justified because DHCP offers are sourced from the configured interface scope; overlapping static reservations or wrong options can create address conflicts and unusable client routes.

C.

The situation is that a research center is moving guest devices off an old router and must preserve fixed addresses reserved for network printers. This action and check address the distinct objective “Enable traceable traffic logging on relevant policies” instead of the stated acceptance requirement. The matching action is to enable the FortiGate DHCP server on the intended LAN interface with a scoped pool, correct gateway and DNS values, and excluded static addresses. Its confirming test is to lease a test device on the target VLAN, inspect the allocated address, default gateway and DNS, and check the FortiGate lease table.

D.

This action and check address the alternate operation “For the research center deployment: Implement: Register the FortiGate and verify applicable FortiGuard subscriptions and update connectivity before relying…” instead of the stated acceptance requirement. The matching action is to enable the FortiGate DHCP server on the intended LAN interface with a scoped pool, correct gateway and DNS values, and excluded static addresses. Its confirming test is to lease a test device on the target VLAN, inspect the allocated address, default gateway and DNS, and check the FortiGate lease table.

Question 31

An insurance office must demonstrate which firewall policy permitted access to its claims API during an audit. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the insurance office deployment: Enable the FortiGate DHCP server on the intended LAN interface with a scoped pool, correct gateway and DNS values, and excluded static addresses.
  2. For the insurance office deployment: Register the FortiGate and verify applicable FortiGuard subscriptions and update connectivity before relying on licensed security services.
  3. For the insurance office deployment: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector.
  4. For the insurance office deployment: Check FortiAnalyzer registration authorization, configured destination and log transport when forwarded events stop appearing.

Answer & Explanations

Correct answer: C

A.

This option addresses the distinct objective “Configure interface-bound DHCP service safely”, not the immediate requirement. DHCP offers are sourced from the configured interface scope; overlapping static reservations or wrong options can create address conflicts and unusable client routes. For the stated case, FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

B.

This option addresses the distinct objective “Register FortiGuard licensing before profile rollout”, not the immediate requirement. FortiGuard-backed ratings and signature services depend on valid entitlements and reachability; an installed security profile alone does not guarantee fresh intelligence. For the stated case, FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

C.

Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. This resolves the issue because FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence. To verify, generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

D.

This option addresses the distinct objective “Repair FortiAnalyzer registration and logging path”, not the immediate requirement. A FortiGate may generate local logs while a denied device registration or broken connection prevents those records from reaching FortiAnalyzer. For the stated case, FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

Question 32

An insurance office must demonstrate which firewall policy permitted access to its claims API during an audit. The engineer proposes this change: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the insurance office deployment: FortiGuard-backed ratings and signature services depend on valid entitlements and reachability; an installed security profile alone does not guarantee fresh intelligence.
  2. For the insurance office deployment: A FortiGate may generate local logs while a denied device registration or broken connection prevents those records from reaching FortiAnalyzer.
  3. For the insurance office deployment: DHCP offers are sourced from the configured interface scope; overlapping static reservations or wrong options can create address conflicts and unusable client routes.
  4. For the insurance office deployment: FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

Answer & Explanations

Correct answer: D

A.

That statement explains the distinct objective “Register FortiGuard licensing before profile rollout” rather than the cause in this case. The deciding mechanism here is that FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

B.

That statement explains the distinct objective “Repair FortiAnalyzer registration and logging path” rather than the cause in this case. The deciding mechanism here is that FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

C.

That statement explains the distinct objective “Configure interface-bound DHCP service safely” rather than the cause in this case. The deciding mechanism here is that FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

D.

FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence. It supports this action: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. To confirm, generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

Question 33

An insurance office must demonstrate which firewall policy permitted access to its claims API during an audit. After implementing this change—Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector—which test best establishes that the intended outcome is actually working?

  1. For the insurance office deployment: Generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.
  2. For the insurance office deployment: Inspect license and update status, force an authorized rating or signature lookup, and confirm its status in logs.
  3. For the insurance office deployment: Compare a locally observed event with the FortiAnalyzer device status and ingestion view, and verify a fresh timestamp after reconnection.
  4. For the insurance office deployment: Lease a test device on the target VLAN, inspect the allocated address, default gateway and DNS, and check the FortiGate lease table.

Answer & Explanations

Correct answer: A

A.

Generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs. This is the relevant test because FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

B.

This check would help evaluate the distinct objective “Register FortiGuard licensing before profile rollout”, but not the required result. For this case, generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

C.

This check would help evaluate the distinct objective “Repair FortiAnalyzer registration and logging path”, but not the required result. For this case, generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

D.

This check would help evaluate the distinct objective “Configure interface-bound DHCP service safely”, but not the required result. For this case, generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

Question 34

An insurance office must demonstrate which firewall policy permitted access to its claims API during an audit. Which proposed shortcut would most directly cause a missing per-session traffic trail during incident investigation, and therefore must be avoided for this requirement?

  1. For the insurance office deployment: Assume copying an antivirus or web-filter profile automatically activates all associated FortiGuard subscriptions.
  2. For the insurance office deployment: Enable system event logs only and assume they document every permitted user session.
  3. For the insurance office deployment: Delete local logging to mask a FortiAnalyzer ingestion problem.
  4. For the insurance office deployment: Copy the production DHCP range onto another VLAN without changing gateway or exclusions.

Answer & Explanations

Correct answer: B

A.

That shortcut would relate to the distinct objective “Register FortiGuard licensing before profile rollout”, rather than the specific configuration or use described. The unsafe step in this case is to enable system event logs only and assume they document every permitted user session.

B.

Enable system event logs only and assume they document every permitted user session. The proposed shortcut bypasses the needed control: FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence. The appropriate response is to select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector.

C.

That shortcut would relate to the distinct objective “Repair FortiAnalyzer registration and logging path”, rather than the specific configuration or use described. The unsafe step in this case is to enable system event logs only and assume they document every permitted user session.

D.

That shortcut would relate to the distinct objective “Configure interface-bound DHCP service safely”, rather than the specific configuration or use described. The unsafe step in this case is to enable system event logs only and assume they document every permitted user session.

Question 35

An insurance office must demonstrate which firewall policy permitted access to its claims API during an audit. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the insurance office deployment: Implement: Register the FortiGate and verify applicable FortiGuard subscriptions and update connectivity before relying on licensed security services. Verify: Inspect license and update status, force an authorized rating or signature lookup, and confirm its status in logs.
  2. For the insurance office deployment: Implement: Check FortiAnalyzer registration authorization, configured destination and log transport when forwarded events stop appearing. Verify: Generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.
  3. For the insurance office deployment: Implement: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Verify: Generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.
  4. For the insurance office deployment: Implement: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Verify: Lease a test device on the target VLAN, inspect the allocated address, default gateway and DNS, and check the FortiGate lease table.

Answer & Explanations

Correct answer: C

A.

This action and check address the distinct objective “Register FortiGuard licensing before profile rollout” instead of the stated acceptance requirement. The matching action is to select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Its confirming test is to generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

B.

This action and check address the alternate operation “For the insurance office deployment: Implement: Check FortiAnalyzer registration authorization, configured destination and log transport when forwarded events stop…” instead of the stated acceptance requirement. The matching action is to select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Its confirming test is to generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

C.

Implement: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Verify: Generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs. This pairing is justified because FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

D.

This action and check address the alternate operation “For the insurance office deployment: Implement: Select the required traffic logging mode on a matching firewall policy and send…” instead of the stated acceptance requirement. The matching action is to select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Its confirming test is to generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

Question 36

A campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the campus SOC deployment: Check FortiAnalyzer registration authorization, configured destination and log transport when forwarded events stop appearing.
  2. For the campus SOC deployment: Enable the FortiGate DHCP server on the intended LAN interface with a scoped pool, correct gateway and DNS values, and excluded static addresses.
  3. For the campus SOC deployment: Register the FortiGate and verify applicable FortiGuard subscriptions and update connectivity before relying on licensed security services.
  4. For the campus SOC deployment: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector.

Answer & Explanations

Correct answer: D

A.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. This option addresses the distinct objective “Repair FortiAnalyzer registration and logging path”, not the immediate requirement. A FortiGate may generate local logs while a denied device registration or broken connection prevents those records from reaching FortiAnalyzer. For the stated case, FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

B.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. This option addresses the distinct objective “Configure interface-bound DHCP service safely”, not the immediate requirement. DHCP offers are sourced from the configured interface scope; overlapping static reservations or wrong options can create address conflicts and unusable client routes. For the stated case, FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

C.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. This option addresses the distinct objective “Register FortiGuard licensing before profile rollout”, not the immediate requirement. FortiGuard-backed ratings and signature services depend on valid entitlements and reachability; an installed security profile alone does not guarantee fresh intelligence. For the stated case, FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

D.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. This resolves the issue because FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence. To verify, generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

Question 37

A campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. The engineer proposes this change: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the campus SOC deployment: FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.
  2. For the campus SOC deployment: A FortiGate may generate local logs while a denied device registration or broken connection prevents those records from reaching FortiAnalyzer.
  3. For the campus SOC deployment: DHCP offers are sourced from the configured interface scope; overlapping static reservations or wrong options can create address conflicts and unusable client routes.
  4. For the campus SOC deployment: FortiGuard-backed ratings and signature services depend on valid entitlements and reachability; an installed security profile alone does not guarantee fresh intelligence.

Answer & Explanations

Correct answer: A

A.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence. It supports this action: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. To confirm, generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

B.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. That statement explains the distinct objective “Repair FortiAnalyzer registration and logging path” rather than the cause in this case. The deciding mechanism here is that FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

C.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. That statement explains the distinct objective “Configure interface-bound DHCP service safely” rather than the cause in this case. The deciding mechanism here is that FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

D.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. That statement explains the distinct objective “Register FortiGuard licensing before profile rollout” rather than the cause in this case. The deciding mechanism here is that FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

Question 38

A campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. After implementing this change—Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector—which test best establishes that the intended outcome is actually working?

  1. For the campus SOC deployment: Compare a locally observed event with the FortiAnalyzer device status and ingestion view, and verify a fresh timestamp after reconnection.
  2. For the campus SOC deployment: Generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.
  3. For the campus SOC deployment: Lease a test device on the target VLAN, inspect the allocated address, default gateway and DNS, and check the FortiGate lease table.
  4. For the campus SOC deployment: Inspect license and update status, force an authorized rating or signature lookup, and confirm its status in logs.

Answer & Explanations

Correct answer: B

A.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. This check would help evaluate the distinct objective “Repair FortiAnalyzer registration and logging path”, but not the required result. For this case, generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

B.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. Generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs. This is the relevant test because FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

C.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. This check would help evaluate the distinct objective “Configure interface-bound DHCP service safely”, but not the required result. For this case, generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

D.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. This check would help evaluate the distinct objective “Register FortiGuard licensing before profile rollout”, but not the required result. For this case, generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

Question 39

A campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. Which proposed shortcut would most directly cause a missing per-session traffic trail during incident investigation, and therefore must be avoided for this requirement?

  1. For the campus SOC deployment: Delete local logging to mask a FortiAnalyzer ingestion problem.
  2. For the campus SOC deployment: Copy the production DHCP range onto another VLAN without changing gateway or exclusions.
  3. For the campus SOC deployment: Enable system event logs only and assume they document every permitted user session.
  4. For the campus SOC deployment: Assume copying an antivirus or web-filter profile automatically activates all associated FortiGuard subscriptions.

Answer & Explanations

Correct answer: C

A.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. That shortcut would relate to the distinct objective “Repair FortiAnalyzer registration and logging path”, rather than the specific configuration or use described. The unsafe step in this case is to enable system event logs only and assume they document every permitted user session.

B.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. That shortcut would relate to the distinct objective “Configure interface-bound DHCP service safely”, rather than the specific configuration or use described. The unsafe step in this case is to enable system event logs only and assume they document every permitted user session.

C.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. Enable system event logs only and assume they document every permitted user session. The proposed shortcut bypasses the needed control: FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence. The appropriate response is to select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector.

D.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. That shortcut would relate to the distinct objective “Register FortiGuard licensing before profile rollout”, rather than the specific configuration or use described. The unsafe step in this case is to enable system event logs only and assume they document every permitted user session.

Question 40

A campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the campus SOC deployment: Implement: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Verify: Lease a test device on the target VLAN, inspect the allocated address, default gateway and DNS, and check the FortiGate lease table.
  2. For the campus SOC deployment: Implement: Register the FortiGate and verify applicable FortiGuard subscriptions and update connectivity before relying on licensed security services. Verify: Inspect license and update status, force an authorized rating or signature lookup, and confirm its status in logs.
  3. For the campus SOC deployment: Implement: Check FortiAnalyzer registration authorization, configured destination and log transport when forwarded events stop appearing. Verify: Generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.
  4. For the campus SOC deployment: Implement: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Verify: Generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

Answer & Explanations

Correct answer: D

A.

This action and check address the alternate operation “For the campus SOC deployment: Implement: Select the required traffic logging mode on a matching firewall policy and send…” instead of the stated acceptance requirement. The matching action is to select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Its confirming test is to generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

B.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. This action and check address the distinct objective “Register FortiGuard licensing before profile rollout” instead of the stated acceptance requirement. The matching action is to select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Its confirming test is to generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

C.

This action and check address the alternate operation “For the campus SOC deployment: Implement: Check FortiAnalyzer registration authorization, configured destination and log transport when forwarded events stop…” instead of the stated acceptance requirement. The matching action is to select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Its confirming test is to generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs.

D.

The situation is that a campus SOC is tracing a suspicious outbound session and needs traffic entries from the relevant policy rather than only login events. Implement: Select the required traffic logging mode on a matching firewall policy and send logs to an authorized supported collector. Verify: Generate a permitted test session, then locate its policy ID, source, destination, action and timestamp in FortiGate or FortiAnalyzer traffic logs. This pairing is justified because FortiGate log generation depends on policy logging configuration and a working destination or local storage path; a permitted session may otherwise leave no useful traffic evidence.

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