Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 7
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?
Answer & Explanations
Correct answer: 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.
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.
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.
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.
Question 61
A defense contractor operates an isolated training network and wants to configure policies before linking its FortiManager to managed firewalls. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: 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: 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.
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. An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available. Verify the result with this 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.
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. This addresses “Preserve FortiManager configuration with a tested backup and restore method”, where the governing 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. The stated case instead calls for: 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.
Use the supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates. This addresses “Complete initial FortiManager system networking and administrator hardening”, where the governing principle is: FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation. The stated case instead calls for: Use FortiManager'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.
Question 62
A defense contractor operates an isolated training network and wants to configure policies before linking its FortiManager to managed firewalls. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available. The corresponding implementation is: 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.
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: An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.
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. That explains “Preserve FortiManager configuration with a tested backup and restore method”, not the mechanism behind the described change. The relevant principle is: An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.
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: An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.
Question 63
A defense contractor operates an isolated training network and wants to configure policies before linking its FortiManager to managed firewalls. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager. That would help test “Explain central management versus FortiGate enforcement responsibilities”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
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. This check is decisive because an offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.
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. That would help test “Preserve FortiManager configuration with a tested backup and restore method”, not the outcome required in this scenario. The relevant acceptance check is: 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.
Question 64
A defense contractor operates an isolated training network and wants to configure policies before linking its FortiManager to managed firewalls. Which proposed shortcut most directly risks stale management state and failed updates after treating offline staging capabilities as evidence of live connectivity and should therefore be rejected?
Answer & Explanations
Correct answer: D
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: Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path.
Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations. That shortcut risks unrecoverable centralized policy and object history when a damaged management appliance lacks a valid tested backup. Here the specific shortcut is: Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path.
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: Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path.
Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path. The foreseeable failure is stale management state and failed updates after treating offline staging capabilities as evidence of live connectivity. The safer response is: 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.
Question 65
A defense contractor operates an isolated training network and wants to configure policies before linking its FortiManager to managed firewalls. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
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. Confirm it through this 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. An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.
The test would be relevant: 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. But the offered implementation—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.—addresses “Complete initial FortiManager system networking and administrator hardening”. The action needed here is: 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.
The action is applicable: 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. But its proposed 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.—addresses “Complete initial FortiManager system networking and administrator hardening”. This requirement is confirmed instead by: 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.
This action/test pair addresses “Preserve FortiManager configuration with a tested backup and restore method”. 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. 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. The case instead calls for: 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.
Question 66
A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: C
Choose the supported ADOM operation and device modes based on whether central FortiManager will own policy packages or inventory and device settings, then test the intended editing and installation workflow. This addresses “Select FortiManager ADOM mode that matches FortiGate and policy responsibilities”, where the governing principle is: ADOM operating choices determine which central policy and device-management functions apply; selecting a more restricted mode cannot be fixed by simply labeling a firewall package as managed. The stated case instead calls for: 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.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. 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. This addresses “Preserve FortiManager configuration with a tested backup and restore method”, where the governing 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. The stated case instead calls for: 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.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. 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. An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available. Verify the result with this 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.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. Use the supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates. This addresses “Complete initial FortiManager system networking and administrator hardening”, where the governing principle is: FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation. The stated case instead calls for: Use FortiManager'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.
Question 67
A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. 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: An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. 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. That explains “Preserve FortiManager configuration with a tested backup and restore method”, not the mechanism behind the described change. The relevant principle is: An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.
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: An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available. The corresponding implementation is: 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.
Question 68
A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. 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: 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.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. 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. This check is decisive because an offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. 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. That would help test “Preserve FortiManager configuration with a tested backup and restore method”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
Question 69
A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. Which proposed shortcut most directly risks stale management state and failed updates after treating offline staging capabilities as evidence of live connectivity and should therefore be rejected?
Answer & Explanations
Correct answer: 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: Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path. The foreseeable failure is stale management state and failed updates after treating offline staging capabilities as evidence of live connectivity. The safer response is: 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.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. 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: Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. Save one screenshot of the policy list and assume every FortiManager administrator, ADOM and workflow record can be reconstructed from managed FortiGate running configurations. That shortcut risks unrecoverable centralized policy and object history when a damaged management appliance lacks a valid tested backup. Here the specific shortcut is: Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path.
Question 70
A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. 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. Confirm it through this 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. An offline management state changes what external or live configuration interactions can complete; cached object editing does not imply current FortiGuard information or device synchronization is available.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. The test would be relevant: 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. But the offered implementation—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.—addresses “Complete initial FortiManager system networking and administrator hardening”. The action needed here is: 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.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. The action is applicable: 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. But its proposed 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.—addresses “Complete initial FortiManager system networking and administrator hardening”. This requirement is confirmed instead by: 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.
The question is set in this situation: A remote energy facility plans brief disconnected operations and needs to distinguish safe cached editing from actions requiring FortiManager connectivity. This action/test pair addresses “Preserve FortiManager configuration with a tested backup and restore method”. 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. 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. The case instead calls for: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 5 - 10 Questions (Last Reviewed 16-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 6 - 10 Questions (Last Reviewed 15-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 7 - 10 Questions (Last Reviewed 14-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 8 - 10 Questions (Last Reviewed 13-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 9 - 10 Questions (Last Reviewed 12-Nov-2026)