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 2

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.

Question 11

An insurance SOC has FortiManager managing remote branches and is deciding where to send security logs for audit retention and incident review. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  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. 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.

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

B.

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

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

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

Question 12

An insurance SOC has FortiManager managing remote branches and is deciding where to send security logs for audit retention and incident review. The engineer proposes the following change: 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. 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. 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. 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: B

A.

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

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. The corresponding implementation 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.

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

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

Question 13

An insurance SOC has FortiManager managing remote branches and is deciding where to send security logs for audit retention and incident review. After implementing this change—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.—which test most directly validates its intended outcome?

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

Answer & Explanations

Correct answer: C

A.

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

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

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

D.

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

An insurance SOC has FortiManager managing remote branches and is deciding where to send security logs for audit retention and incident review. Which proposed shortcut most directly risks missing security visibility after assuming central configuration automatically delivers usable analytics and log retention and should therefore be rejected?

  1. 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.
  2. Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation.
  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. Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed.

Answer & Explanations

Correct answer: B

A.

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: Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation.

B.

Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation. The foreseeable failure is missing security visibility after assuming central configuration automatically delivers usable analytics and log retention. The safer response 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.

C.

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: Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation.

D.

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: Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation.

Question 15

An insurance SOC has FortiManager managing remote branches and is deciding where to send security logs for audit retention and incident review. 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: 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.
  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: 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. 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.

Answer & Explanations

Correct answer: D

A.

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

C.

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.

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

Question 16

A university wants to evaluate built-in FortiAnalyzer features versus a dedicated analysis platform without risking policy-management functions during a telemetry migration. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer & Explanations

Correct answer: A

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

B.

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

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

Question 17

A university wants to evaluate built-in FortiAnalyzer features versus a dedicated analysis platform without risking policy-management functions during a telemetry migration. The engineer proposes the following change: 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. 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. 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.
  3. 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.
  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: 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: 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.

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

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

Question 18

A university wants to evaluate built-in FortiAnalyzer features versus a dedicated analysis platform without risking policy-management functions during a telemetry migration. After implementing this change—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.—which test most directly validates its intended outcome?

  1. 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.
  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. 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.
  4. 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.

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

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

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

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

A university wants to evaluate built-in FortiAnalyzer features versus a dedicated analysis platform without risking policy-management functions during a telemetry migration. Which proposed shortcut most directly risks missing security visibility after assuming central configuration automatically delivers usable analytics and log retention and should therefore be rejected?

  1. 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.
  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. Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation.
  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: C

A.

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: Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation.

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. 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: Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation.

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. Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation. The foreseeable failure is missing security visibility after assuming central configuration automatically delivers usable analytics and log retention. The safer response 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. 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: Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation.

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.

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