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 3

Question 20

A university wants to evaluate built-in FortiAnalyzer features versus a dedicated analysis platform without risking policy-management functions during a telemetry migration. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Use the documented FortiManager JSON-RPC API with an appropriately authorized automation identity, correct session handling and supported methods to read approved device or policy-package data before attempting a change. Verify: Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM.
  2. 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: 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: 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: 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. 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: 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: B

A.

The question is set in this situation: A university wants to evaluate built-in FortiAnalyzer features versus a dedicated analysis platform without risking policy-management functions during a telemetry migration. This action/test pair addresses “Authenticate and scope FortiManager JSON API operations using the correct methods”. Use the documented FortiManager JSON-RPC API with an appropriately authorized automation identity, correct session handling and supported methods to read approved device or policy-package data before attempting a change. Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM. The case instead calls for: 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.

B.

The question is set in this situation: A university wants to evaluate built-in FortiAnalyzer features versus a dedicated analysis platform without risking policy-management functions during a telemetry migration. 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. Confirm it through this 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. 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.

C.

The question is set in this situation: A university wants to evaluate built-in FortiAnalyzer features versus a dedicated analysis platform without risking policy-management functions during a telemetry migration. The test would be relevant: 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. But the offered implementation—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.—addresses “Use FortiManager network topology to validate managed estate visibility”. The action needed here is: 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.

D.

The question is set in this situation: A university wants to evaluate built-in FortiAnalyzer features versus a dedicated analysis platform without risking policy-management functions during a telemetry migration. The action is applicable: 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. But its proposed test—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.—addresses “Use FortiManager network topology to validate managed estate visibility”. This requirement is confirmed instead by: 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.

Question 21

A transport company has hundreds of branches and needs operations staff to distinguish discovered fabric devices from FortiGates actually registered in FortiManager ADOMs. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  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. 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.
  4. Use the documented FortiManager JSON-RPC API with an appropriately authorized automation identity, correct session handling and supported methods to read approved device or policy-package data before attempting a change.

Answer & Explanations

Correct answer: A

A.

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. 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. Verify the result with this test: 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.

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. This addresses “Explain central management versus FortiGate enforcement responsibilities”, where the governing 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. The stated case instead calls for: 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.

C.

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: 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.

D.

Use the documented FortiManager JSON-RPC API with an appropriately authorized automation identity, correct session handling and supported methods to read approved device or policy-package data before attempting a change. This addresses “Authenticate and scope FortiManager JSON API operations using the correct methods”, where the governing principle is: FortiManager management API requests use defined endpoints, JSON-RPC methods and session or token authorization; a successful HTTP transport response alone does not prove an internal API operation succeeded or was permitted. The stated case instead calls for: 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.

Question 22

A transport company has hundreds of branches and needs operations staff to distinguish discovered fabric devices from FortiGates actually registered in FortiManager ADOMs. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. 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.
  3. 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.
  4. FortiManager management API requests use defined endpoints, JSON-RPC methods and session or token authorization; a successful HTTP transport response alone does not prove an internal API operation succeeded or was permitted.

Answer & Explanations

Correct answer: C

A.

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: 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.

B.

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. That explains “Explain central management versus FortiGate enforcement responsibilities”, not the mechanism behind the described change. The relevant 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.

C.

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 corresponding implementation is: 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.

D.

FortiManager management API requests use defined endpoints, JSON-RPC methods and session or token authorization; a successful HTTP transport response alone does not prove an internal API operation succeeded or was permitted. That explains “Authenticate and scope FortiManager JSON API operations using the correct methods”, not the mechanism behind the described change. The relevant 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.

Question 23

A transport company has hundreds of branches and needs operations staff to distinguish discovered fabric devices from FortiGates actually registered in FortiManager ADOMs. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  2. 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.
  3. 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. Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM.

Answer & Explanations

Correct answer: B

A.

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: 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.

B.

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. This check is decisive because 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.

C.

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. That would help test “Explain central management versus FortiGate enforcement responsibilities”, not the outcome required in this scenario. The relevant acceptance check is: 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.

D.

Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM. That would help test “Authenticate and scope FortiManager JSON API operations using the correct methods”, not the outcome required in this scenario. The relevant acceptance check is: 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.

Question 24

A transport company has hundreds of branches and needs operations staff to distinguish discovered fabric devices from FortiGates actually registered in FortiManager ADOMs. Which proposed shortcut most directly risks unauthorized management assumptions after confusing discovered network relationships with authenticated managed-device inventory and should therefore be rejected?

  1. Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online.
  2. Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed.
  3. 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.
  4. Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions.

Answer & Explanations

Correct answer: D

A.

Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online. That shortcut risks loss of actual traffic filtering caused by confusing central configuration control with an enforcement gateway. Here the specific shortcut is: Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions.

B.

Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed. That shortcut risks misreported automation success or cross-domain configuration access caused by ignoring FortiManager API authorization and status fields. Here the specific shortcut is: Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions.

C.

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 all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions.

D.

Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions. The foreseeable failure is unauthorized management assumptions after confusing discovered network relationships with authenticated managed-device inventory. The safer response is: 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.

Question 25

A transport company has hundreds of branches and needs operations staff to distinguish discovered fabric devices from FortiGates actually registered in FortiManager ADOMs. 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: 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: Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM.
  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: Use the documented FortiManager JSON-RPC API with an appropriately authorized automation identity, correct session handling and supported methods to read approved device or policy-package data before attempting a change. 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: A

A.

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. Confirm it through this test: 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. 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.

B.

The action is applicable: 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. But its proposed test—Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM.—addresses “Authenticate and scope FortiManager JSON API operations using the correct methods”. This requirement is confirmed instead by: 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.

C.

This action/test pair addresses “Explain central management versus FortiGate enforcement responsibilities”. 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. 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. The case instead calls for: 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.

D.

The test would be relevant: 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. But the offered implementation—Use the documented FortiManager JSON-RPC API with an appropriately authorized automation identity, correct session handling and supported methods to read approved device or policy-package data before attempting a change.—addresses “Authenticate and scope FortiManager JSON API operations using the correct methods”. The action needed here is: 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.

Question 26

A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  3. 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.
  4. Use the documented FortiManager JSON-RPC API with an appropriately authorized automation identity, correct session handling and supported methods to read approved device or policy-package data before attempting a change.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. 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. This addresses “Explain central management versus FortiGate enforcement responsibilities”, where the governing 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. The stated case instead calls for: 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.

B.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. 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. 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. Verify the result with this test: 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.

C.

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: 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.

D.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. Use the documented FortiManager JSON-RPC API with an appropriately authorized automation identity, correct session handling and supported methods to read approved device or policy-package data before attempting a change. This addresses “Authenticate and scope FortiManager JSON API operations using the correct methods”, where the governing principle is: FortiManager management API requests use defined endpoints, JSON-RPC methods and session or token authorization; a successful HTTP transport response alone does not prove an internal API operation succeeded or was permitted. The stated case instead calls for: 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.

Question 27

A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. The engineer proposes the following change: 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. Which mechanism explains why it works?

  1. 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.
  2. FortiManager management API requests use defined endpoints, JSON-RPC methods and session or token authorization; a successful HTTP transport response alone does not prove an internal API operation succeeded or was permitted.
  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. 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: D

A.

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: 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.

B.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. FortiManager management API requests use defined endpoints, JSON-RPC methods and session or token authorization; a successful HTTP transport response alone does not prove an internal API operation succeeded or was permitted. That explains “Authenticate and scope FortiManager JSON API operations using the correct methods”, not the mechanism behind the described change. The relevant 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.

C.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. 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. That explains “Explain central management versus FortiGate enforcement responsibilities”, not the mechanism behind the described change. The relevant 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.

D.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. 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 corresponding implementation is: 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.

Question 28

A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. After implementing this change—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.—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. 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.
  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. Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM.

Answer & Explanations

Correct answer: C

A.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. 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. That would help test “Explain central management versus FortiGate enforcement responsibilities”, not the outcome required in this scenario. The relevant acceptance check is: 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.

B.

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: 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.

C.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. 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. This check is decisive because 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.

D.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM. That would help test “Authenticate and scope FortiManager JSON API operations using the correct methods”, not the outcome required in this scenario. The relevant acceptance check is: 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.

Question 29

A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. Which proposed shortcut most directly risks unauthorized management assumptions after confusing discovered network relationships with authenticated managed-device inventory 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. Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed.
  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. 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.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions. The foreseeable failure is unauthorized management assumptions after confusing discovered network relationships with authenticated managed-device inventory. The safer response is: 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.

B.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed. That shortcut risks misreported automation success or cross-domain configuration access caused by ignoring FortiManager API authorization and status fields. Here the specific shortcut is: Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions.

C.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online. That shortcut risks loss of actual traffic filtering caused by confusing central configuration control with an enforcement gateway. Here the specific shortcut is: Treat all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions.

D.

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 all automatically discovered topology icons as trusted FortiManager-managed firewalls and install a corporate policy on them without verifying registration or permissions.

Question 30

A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. 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: Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM.
  2. 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.
  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: Use the documented FortiManager JSON-RPC API with an appropriately authorized automation identity, correct session handling and supported methods to read approved device or policy-package data before attempting a change. 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: B

A.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. The action is applicable: 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. But its proposed test—Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM.—addresses “Authenticate and scope FortiManager JSON API operations using the correct methods”. This requirement is confirmed instead by: 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.

B.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. 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. Confirm it through this test: 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. 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.

C.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. This action/test pair addresses “Explain central management versus FortiGate enforcement responsibilities”. 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. 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. The case instead calls for: 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.

D.

The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. The test would be relevant: 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. But the offered implementation—Use the documented FortiManager JSON-RPC API with an appropriately authorized automation identity, correct session handling and supported methods to read approved device or policy-package data before attempting a change.—addresses “Authenticate and scope FortiManager JSON API operations using the correct methods”. The action needed here is: 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.

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