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 6

Question 50

A university is replacing a management VM and wants a measurable commissioning checklist for routing, time, DNS and admin access before restoring policies. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: 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. Verify: 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. Implement: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. Verify: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.
  3. Implement: Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan. Verify: 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.
  4. Implement: 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. Verify: In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A university is replacing a management VM and wants a measurable commissioning checklist for routing, time, DNS and admin access before restoring policies. 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. Confirm it through this test: 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. 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.

B.

The question is set in this situation: A university is replacing a management VM and wants a measurable commissioning checklist for routing, time, DNS and admin access before restoring policies. This action/test pair addresses “Protect FortiManager administrative access using scoped roles and external authentication”. Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout. The case instead calls for: 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.

C.

The question is set in this situation: A university is replacing a management VM and wants a measurable commissioning checklist for routing, time, DNS and admin access before restoring policies. The test would be relevant: 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. But the offered implementation—Use FortiManager's supported offline mode only for a documented disconnected management or staging workflow and confirm that operations requiring live FortiGuard or connected devices have a separate readiness plan.—addresses “Plan the FortiManager offline maintenance mode against connectivity requirements”. The action needed here is: 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.

D.

The question is set in this situation: A university is replacing a management VM and wants a measurable commissioning checklist for routing, time, DNS and admin access before restoring policies. The action is applicable: 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. But its proposed test—In a disconnected lab verify permitted local work, record which registration, update or installation actions are unavailable, then reconnect and demonstrate an explicitly reviewed synchronized change.—addresses “Plan the FortiManager offline maintenance mode against connectivity requirements”. This requirement is confirmed instead by: 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.

Question 51

A national retailer is planning management appliance replacement and needs to restore multiple customer ADOMs after a hardware failure. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Use the supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates.
  2. Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation.
  3. Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.
  4. Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

Answer & Explanations

Correct answer: D

A.

Use the supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates. This addresses “Complete initial FortiManager system networking and administrator hardening”, where the governing principle is: FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation. The stated case instead calls for: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

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: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

C.

Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. This addresses “Protect FortiManager administrative access using scoped roles and external authentication”, where the governing principle is: A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers. The stated case instead calls for: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

D.

Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records. Verify the result with this test: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

Question 52

A national retailer is planning management appliance replacement and needs to restore multiple customer ADOMs after a hardware failure. The engineer proposes the following change: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Which mechanism explains why it works?

  1. FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable.
  2. A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.
  3. Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.
  4. 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.

Answer & Explanations

Correct answer: C

A.

FortiManager coordinates intended configuration and deployment to registered FortiGates; the managed firewall continues packet processing under its installed policy even if the management appliance is unavailable. That explains “Explain central management versus FortiGate enforcement responsibilities”, not the mechanism behind the described change. The relevant principle is: Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.

B.

A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers. That explains “Protect FortiManager administrative access using scoped roles and external authentication”, not the mechanism behind the described change. The relevant principle is: Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.

C.

Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records. The corresponding implementation is: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

D.

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: Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.

Question 53

A national retailer is planning management appliance replacement and needs to restore multiple customer ADOMs after a hardware failure. After implementing this change—Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.—which test most directly validates its intended outcome?

  1. Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.
  2. 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.
  3. 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.
  4. Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

Answer & Explanations

Correct answer: A

A.

Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs. This check is decisive because device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.

B.

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: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

C.

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: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

D.

Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout. That would help test “Protect FortiManager administrative access using scoped roles and external authentication”, not the outcome required in this scenario. The relevant acceptance check is: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

Question 54

A national retailer is planning management appliance replacement and needs to restore multiple customer ADOMs after a hardware failure. Which proposed shortcut most directly risks unrecoverable centralized policy and object history when a damaged management appliance lacks a valid tested backup 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. Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords.
  3. Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations.
  4. Treat the FortiManager VM as the inline packet-forwarding firewall and move the production traffic gateway off the network because its manager is online.

Answer & Explanations

Correct answer: C

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: Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations.

B.

Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords. That shortcut risks unauthorized cross-tenant policy changes after conflating centralized authentication with least-privilege FortiManager authorization. Here the specific shortcut is: Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations.

C.

Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations. The foreseeable failure is unrecoverable centralized policy and object history when a damaged management appliance lacks a valid tested backup. The safer response is: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

D.

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: Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations.

Question 55

A national retailer is planning management appliance replacement and needs to restore multiple customer ADOMs after a hardware failure. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: 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. Verify: 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. Implement: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Verify: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.
  3. Implement: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Verify: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.
  4. Implement: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. Verify: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

Answer & Explanations

Correct answer: B

A.

This action/test pair addresses “Complete initial FortiManager system networking and administrator hardening”. 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. 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. The case instead calls for: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

B.

Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Confirm it through this test: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs. Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.

C.

The action is applicable: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. But its proposed test—Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.—addresses “Protect FortiManager administrative access using scoped roles and external authentication”. This requirement is confirmed instead by: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

D.

The test would be relevant: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs. But the offered implementation—Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.—addresses “Protect FortiManager administrative access using scoped roles and external authentication”. The action needed here is: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

Question 56

A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?

  1. Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.
  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 supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates.
  4. Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

Answer & Explanations

Correct answer: D

A.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. This addresses “Protect FortiManager administrative access using scoped roles and external authentication”, where the governing principle is: A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers. The stated case instead calls for: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

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: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

C.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. 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: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

D.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records. Verify the result with this test: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

Question 57

A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. The engineer proposes the following change: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. 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. Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.
  3. 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.
  4. A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers.

Answer & Explanations

Correct answer: B

A.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. 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: Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.

B.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records. The corresponding implementation is: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

C.

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: Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.

D.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. A successful external login proves identity but does not automatically impose correct FortiManager administrative scope; explicit profile privileges and ADOM assignments enforce authorization across isolated management customers. That explains “Protect FortiManager administrative access using scoped roles and external authentication”, not the mechanism behind the described change. The relevant principle is: Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.

Question 58

A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. After implementing this change—Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.—which test most directly validates its intended outcome?

  1. 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.
  2. From an authorized management subnet connect to the new FortiManager, verify its route, clock and name resolution, deny an unapproved management source, and confirm no default shared administrator credential remains.
  3. Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.
  4. Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

Answer & Explanations

Correct answer: D

A.

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: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

B.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. 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: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

C.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout. That would help test “Protect FortiManager administrative access using scoped roles and external authentication”, not the outcome required in this scenario. The relevant acceptance check is: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

D.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs. This check is decisive because device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.

Question 59

A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. Which proposed shortcut most directly risks unrecoverable centralized policy and object history when a damaged management appliance lacks a valid tested backup 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. Turn on a mode that omits required central policy management and assume FortiManager will still author and install the organization's shared firewall rule base exactly as before.
  3. Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations.
  4. Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords.

Answer & Explanations

Correct answer: C

A.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. 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: Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations.

B.

Turn on a mode that omits required central policy management and assume FortiManager will still author and install the organization's shared firewall rule base exactly as before. That shortcut risks missing centralized policy functionality after selecting an ADOM management mode inconsistent with operational requirements. Here the specific shortcut is: Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations.

C.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations. The foreseeable failure is unrecoverable centralized policy and object history when a damaged management appliance lacks a valid tested backup. The safer response is: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

D.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. Grant every externally authenticated contractor a Super_User profile for all ADOMs because the enterprise RADIUS server already authenticated their passwords. That shortcut risks unauthorized cross-tenant policy changes after conflating centralized authentication with least-privilege FortiManager authorization. Here the specific shortcut is: Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations.

Question 60

A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. Which combined implementation and verification plan is the best match for this workload?

  1. Implement: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Verify: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.
  2. Implement: Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant. Verify: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.
  3. Implement: 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. Verify: 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.
  4. Implement: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Verify: Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.

Answer & Explanations

Correct answer: A

A.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. Confirm it through this test: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs. Device and ADOM database contents plus administrator settings are management-plane assets; keeping only a FortiGate running configuration does not provide a full replacement of FortiManager's object and policy records.

B.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. The test would be relevant: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs. But the offered implementation—Configure restricted administrator profiles and approved external authentication for central FortiManager administrators, assign only needed ADOM privileges, and validate that a denied role cannot edit a different tenant.—addresses “Protect FortiManager administrative access using scoped roles and external authentication”. The action needed here is: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

C.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. This action/test pair addresses “Complete initial FortiManager system networking and administrator hardening”. 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. 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. The case instead calls for: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance.

D.

The question is set in this situation: A financial services security lead requires proof that FortiManager's historical policy packages survive disaster recovery, not merely that branch firewalls keep forwarding traffic. The action is applicable: Create and protect a FortiManager configuration backup with version information and authorized recovery credentials, document restore dependencies, and rehearse recovery on an isolated compatible test appliance. But its proposed test—Use two fictional lab administrators with different ADOM assignments, test allowed and denied object edits and installations, and inspect administrative sessions and authentication logs after logout.—addresses “Protect FortiManager administrative access using scoped roles and external authentication”. This requirement is confirmed instead by: Backup the lab FortiManager, record software version and file integrity, restore into a disposable compatible instance, and confirm ADOMs, registered-device records and policy package revision IDs.

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