Practice Exams:

Fortinet FCP_FMG_AD-7.6 Dumps

EXAM: Fortinet NSE 5 - FortiManager 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

FCP_FMG_AD-7.6 Premium ETE File


  • Premium File 62 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet FCP_FMG_AD-7.6 Practice Test 1

Question 1

A retail network administrator is explaining why twenty store FortiGates continue protecting checkout traffic during a short outage of their central FortiManager. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Use the supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates.
  2. Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.
  3. Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed.
  4. Identify whether the FortiManager deployment uses supported FortiAnalyzer features or forwards events to an approved FortiAnalyzer service, and configure the intended logging and event-analysis path separately from policy provisioning.

Answer & Explanations

Correct answer: B

A.

Use the supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates. This addresses “Complete initial FortiManager system networking and administrator hardening”, where the governing principle is: FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation. The stated case instead calls for: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

B.

Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable. Verify the result with this test: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.

C.

Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed. This addresses “Use FortiManager network topology to validate managed estate visibility”, where the governing principle is: Topology visibility depends on device registration, supported telemetry and actual network relationships; a drawn fabric edge or visible hostname alone does not create device control or verify that firmware and policies are current. The stated case instead calls for: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

D.

Identify whether the FortiManager deployment uses supported FortiAnalyzer features or forwards events to an approved FortiAnalyzer service, and configure the intended logging and event-analysis path separately from policy provisioning. This addresses “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, where the governing principle is: Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received. The stated case instead calls for: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

Question 2

A retail network administrator is explaining why twenty store FortiGates continue protecting checkout traffic during a short outage of their central FortiManager. The engineer proposes the following change: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. Which mechanism explains why it works?

  1. FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.
  2. Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received.
  3. FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation.
  4. Topology visibility depends on device registration, supported telemetry and actual network relationships; a drawn fabric edge or visible hostname alone does not create device control or verify that firmware and policies are current.

Answer & Explanations

Correct answer: A

A.

FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable. The corresponding implementation is: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

B.

Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received. That explains “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, not the mechanism behind the described change. The relevant principle is: FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.

C.

FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation. That explains “Complete initial FortiManager system networking and administrator hardening”, not the mechanism behind the described change. The relevant principle is: FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.

D.

Topology visibility depends on device registration, supported telemetry and actual network relationships; a drawn fabric edge or visible hostname alone does not create device control or verify that firmware and policies are current. That explains “Use FortiManager network topology to validate managed estate visibility”, not the mechanism behind the described change. The relevant principle is: FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.

Question 3

A retail network administrator is explaining why twenty store FortiGates continue protecting checkout traffic during a short outage of their central FortiManager. After implementing this change—Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.—which test most directly validates its intended outcome?

  1. Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device.
  2. From an authorized management subnet connect to the new FortiManager, verify its route, clock and name resolution, deny an unapproved management source, and confirm no default shared administrator credential remains.
  3. Generate a harmless blocked connection on a test FortiGate, verify its log reaches the configured analysis destination and remains searchable, and separately confirm FortiManager can still install policy.
  4. Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.

Answer & Explanations

Correct answer: D

A.

Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device. That would help test “Use FortiManager network topology to validate managed estate visibility”, not the outcome required in this scenario. The relevant acceptance check is: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.

B.

From an authorized management subnet connect to the new FortiManager, verify its route, clock and name resolution, deny an unapproved management source, and confirm no default shared administrator credential remains. That would help test “Complete initial FortiManager system networking and administrator hardening”, not the outcome required in this scenario. The relevant acceptance check is: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.

C.

Generate a harmless blocked connection on a test FortiGate, verify its log reaches the configured analysis destination and remains searchable, and separately confirm FortiManager can still install policy. That would help test “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, not the outcome required in this scenario. The relevant acceptance check is: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.

D.

Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager. This check is decisive because fortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.

Question 4

A retail network administrator is explaining why twenty store FortiGates continue protecting checkout traffic during a short outage of their central FortiManager. Which proposed shortcut most directly risks loss of actual traffic filtering caused by confusing central configuration control with an enforcement gateway and should therefore be rejected?

  1. Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions.
  2. Expose a factory-default FortiManager management interface directly to the internet and begin registering branch gateways before setting a restricted administrator account or working route.
  3. Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online.
  4. Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation.

Answer & Explanations

Correct answer: C

A.

Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions. That shortcut risks unauthorized management assumptions after confusing discovered network relationships with authenticated managed-device inventory. Here the specific shortcut is: Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online.

B.

Expose a factory-default FortiManager management interface directly to the internet and begin registering branch gateways before setting a restricted administrator account or working route. That shortcut risks central management compromise or failed device onboarding from unprotected factory defaults and incomplete network bootstrap. Here the specific shortcut is: Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online.

C.

Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online. The foreseeable failure is loss of actual traffic filtering caused by confusing central configuration control with an enforcement gateway. The safer response is: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

D.

Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation. That shortcut risks missing security visibility after assuming central configuration automatically delivers usable analytics and log retention. Here the specific shortcut is: Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online.

Question 5

A retail network administrator is explaining why twenty store FortiGates continue protecting checkout traffic during a short outage of their central FortiManager. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed. Verify: Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device.
  2. Implement: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. Verify: Generate a harmless blocked connection on a test FortiGate, verify its log reaches the configured analysis destination and remains searchable, and separately confirm FortiManager can still install policy.
  3. Implement: Identify whether the FortiManager deployment uses supported FortiAnalyzer features or forwards events to an approved FortiAnalyzer service, and configure the intended logging and event-analysis path separately from policy provisioning. Verify: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.
  4. Implement: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. Verify: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.

Answer & Explanations

Correct answer: D

A.

This action/test pair addresses “Use FortiManager network topology to validate managed estate visibility”. Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed. Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device. The case instead calls for: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

B.

The action is applicable: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. But its proposed test—Generate a harmless blocked connection on a test FortiGate, verify its log reaches the configured analysis destination and remains searchable, and separately confirm FortiManager can still install policy.—addresses “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”. This requirement is confirmed instead by: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.

C.

The test would be relevant: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager. But the offered implementation—Identify whether the FortiManager deployment uses supported FortiAnalyzer features or forwards events to an approved FortiAnalyzer service, and configure the intended logging and event-analysis path separately from policy provisioning.—addresses “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”. The action needed here is: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

D.

Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. Confirm it through this test: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager. FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.

Question 6

A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Choose the supported ADOM operation and device modes based on whether central FortiManager will own policy packages or inventory and device settings, then test the intended editing and installation workflow.
  2. Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.
  3. Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed.
  4. Identify whether the FortiManager deployment uses supported FortiAnalyzer features or forwards events to an approved FortiAnalyzer service, and configure the intended logging and event-analysis path separately from policy provisioning.

Answer & Explanations

Correct answer: B

A.

Choose the supported ADOM operation and device modes based on whether central FortiManager will own policy packages or inventory and device settings, then test the intended editing and installation workflow. This addresses “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, where the governing principle is: ADOM operating choices determine which central policy and device-management functions apply; selecting a more restricted mode cannot be fixed by simply labeling a firewall package as managed. The stated case instead calls for: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

B.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable. Verify the result with this test: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.

C.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed. This addresses “Use FortiManager network topology to validate managed estate visibility”, where the governing principle is: Topology visibility depends on device registration, supported telemetry and actual network relationships; a drawn fabric edge or visible hostname alone does not create device control or verify that firmware and policies are current. The stated case instead calls for: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

D.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Identify whether the FortiManager deployment uses supported FortiAnalyzer features or forwards events to an approved FortiAnalyzer service, and configure the intended logging and event-analysis path separately from policy provisioning. This addresses “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, where the governing principle is: Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received. The stated case instead calls for: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

Question 7

A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. The engineer proposes the following change: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. Which mechanism explains why it works?

  1. Topology visibility depends on device registration, supported telemetry and actual network relationships; a drawn fabric edge or visible hostname alone does not create device control or verify that firmware and policies are current.
  2. ADOM operating choices determine which central policy and device-management functions apply; selecting a more restricted mode cannot be fixed by simply labeling a firewall package as managed.
  3. FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.
  4. Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received.

Answer & Explanations

Correct answer: C

A.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Topology visibility depends on device registration, supported telemetry and actual network relationships; a drawn fabric edge or visible hostname alone does not create device control or verify that firmware and policies are current. That explains “Use FortiManager network topology to validate managed estate visibility”, not the mechanism behind the described change. The relevant principle is: FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.

B.

ADOM operating choices determine which central policy and device-management functions apply; selecting a more restricted mode cannot be fixed by simply labeling a firewall package as managed. That explains “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, not the mechanism behind the described change. The relevant principle is: FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.

C.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable. The corresponding implementation is: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

D.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received. That explains “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, not the mechanism behind the described change. The relevant principle is: FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.

Question 8

A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. After implementing this change—Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.—which test most directly validates its intended outcome?

  1. Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.
  2. Generate a harmless blocked connection on a test FortiGate, verify its log reaches the configured analysis destination and remains searchable, and separately confirm FortiManager can still install policy.
  3. Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device.
  4. Configure a test ADOM in the intended supported mode, verify which policy-editor, device database and installation operations are exposed, and compare them with a deliberately alternate mode.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager. This check is decisive because fortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.

B.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Generate a harmless blocked connection on a test FortiGate, verify its log reaches the configured analysis destination and remains searchable, and separately confirm FortiManager can still install policy. That would help test “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, not the outcome required in this scenario. The relevant acceptance check is: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.

C.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device. That would help test “Use FortiManager network topology to validate managed estate visibility”, not the outcome required in this scenario. The relevant acceptance check is: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.

D.

Configure a test ADOM in the intended supported mode, verify which policy-editor, device database and installation operations are exposed, and compare them with a deliberately alternate mode. That would help test “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, not the outcome required in this scenario. The relevant acceptance check is: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.

Question 9

A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Which proposed shortcut most directly risks loss of actual traffic filtering caused by confusing central configuration control with an enforcement gateway and should therefore be rejected?

  1. Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation.
  2. Turn on a mode that omits required central policy management and assume FortiManager will still author and install the organization's shared firewall rule base exactly as before.
  3. Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions.
  4. Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online.

Answer & Explanations

Correct answer: D

A.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation. That shortcut risks missing security visibility after assuming central configuration automatically delivers usable analytics and log retention. Here the specific shortcut is: Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online.

B.

Turn on a mode that omits required central policy management and assume FortiManager will still author and install the organization's shared firewall rule base exactly as before. That shortcut risks missing centralized policy functionality after selecting an ADOM management mode inconsistent with operational requirements. Here the specific shortcut is: Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online.

C.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions. That shortcut risks unauthorized management assumptions after confusing discovered network relationships with authenticated managed-device inventory. Here the specific shortcut is: Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online.

D.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online. The foreseeable failure is loss of actual traffic filtering caused by confusing central configuration control with an enforcement gateway. The safer response is: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

Question 10

A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Identify whether the FortiManager deployment uses supported FortiAnalyzer features or forwards events to an approved FortiAnalyzer service, and configure the intended logging and event-analysis path separately from policy provisioning. Verify: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.
  2. Implement: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. Verify: Generate a harmless blocked connection on a test FortiGate, verify its log reaches the configured analysis destination and remains searchable, and separately confirm FortiManager can still install policy.
  3. Implement: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. Verify: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.
  4. Implement: Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed. Verify: Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device.

Answer & Explanations

Correct answer: C

A.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. The test would be relevant: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager. But the offered implementation—Identify whether the FortiManager deployment uses supported FortiAnalyzer features or forwards events to an approved FortiAnalyzer service, and configure the intended logging and event-analysis path separately from policy provisioning.—addresses “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”. The action needed here is: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

B.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. The action is applicable: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. But its proposed test—Generate a harmless blocked connection on a test FortiGate, verify its log reaches the configured analysis destination and remains searchable, and separately confirm FortiManager can still install policy.—addresses “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”. This requirement is confirmed instead by: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager.

C.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. Confirm it through this test: Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager. FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.

D.

The question is set in this situation: A medical campus separates firewall policy authors from data-path operators and needs a test proving the management plane is distinct from the enforcement plane. This action/test pair addresses “Use FortiManager network topology to validate managed estate visibility”. Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed. Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device. The case instead calls for: Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.

Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests