Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 5
Question 40
A bank's change automation receives HTTP success but its expected FortiManager policy status is unchanged and requires diagnosis of JSON-RPC operation results. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The question is set in this situation: A bank's change automation receives HTTP success but its expected FortiManager policy status is unchanged and requires diagnosis of JSON-RPC operation results. This action/test pair addresses “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”. 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. 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. The case instead calls for: 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.
The question is set in this situation: A bank's change automation receives HTTP success but its expected FortiManager policy status is unchanged and requires diagnosis of JSON-RPC operation results. The action is applicable: 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. But its proposed 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.—addresses “Explain central management versus FortiGate enforcement responsibilities”. This requirement is confirmed instead by: 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 question is set in this situation: A bank's change automation receives HTTP success but its expected FortiManager policy status is unchanged and requires diagnosis of JSON-RPC operation results. 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. Confirm it through this test: Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM. 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 question is set in this situation: A bank's change automation receives HTTP success but its expected FortiManager policy status is unchanged and requires diagnosis of JSON-RPC operation results. The test would be relevant: 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. But the offered implementation—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.—addresses “Explain central management versus FortiGate enforcement responsibilities”. The action needed here is: 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.
Question 41
A manufacturing security team is turning on a newly deployed FortiManager appliance before any production firewall has been registered. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: 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. 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. Verify the result with 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.
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. This addresses “Plan the FortiManager offline maintenance mode against connectivity requirements”, where the governing 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 stated 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.
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: 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.
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 the supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates.
Question 42
A manufacturing security team is turning on a newly deployed FortiManager appliance before any production firewall has been registered. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
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: 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.
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: 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.
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. That explains “Plan the FortiManager offline maintenance mode against connectivity requirements”, not the mechanism behind the described change. The relevant 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.
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 corresponding implementation 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.
Question 43
A manufacturing security team is turning on a newly deployed FortiManager appliance before any production firewall has been registered. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
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: 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.
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. This check is decisive because 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.
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. That would help test “Plan the FortiManager offline maintenance mode against connectivity requirements”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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 44
A manufacturing security team is turning on a newly deployed FortiManager appliance before any production firewall has been registered. Which proposed shortcut most directly risks central management compromise or failed device onboarding from unprotected factory defaults and incomplete network bootstrap and should therefore be rejected?
Answer & Explanations
Correct answer: C
Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path. That shortcut risks stale management state and failed updates after treating offline staging capabilities as evidence of live connectivity. Here the specific shortcut is: 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.
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: 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.
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. The foreseeable failure is central management compromise or failed device onboarding from unprotected factory defaults and incomplete network bootstrap. The safer response 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.
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: 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.
Question 45
A manufacturing security team is turning on a newly deployed FortiManager appliance before any production firewall has been registered. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
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.
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.
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.
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.
Question 46
A university is replacing a management VM and wants a measurable commissioning checklist for routing, time, DNS and admin access before restoring policies. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: 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. 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. Verify the result with 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.
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. 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: 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.
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 the supported initial setup wizard or CLI to set management interfaces, routes, DNS, time synchronization and appropriately restricted administrator access before onboarding production FortiGates.
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 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. This addresses “Plan the FortiManager offline maintenance mode against connectivity requirements”, where the governing 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 stated 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.
Question 47
A university is replacing a management VM and wants a measurable commissioning checklist for routing, time, DNS and admin access before restoring policies. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: 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. 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. That explains “Plan the FortiManager offline maintenance mode against connectivity requirements”, not the mechanism behind the described change. The relevant 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 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. 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: 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 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. 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 corresponding implementation 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.
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: 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.
Question 48
A university is replacing a management VM and wants a measurable commissioning checklist for routing, time, DNS and admin access before restoring policies. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: 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. 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. That would help test “Plan the FortiManager offline maintenance mode against connectivity requirements”, not the outcome required in this scenario. The relevant acceptance check is: 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 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 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: 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.
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: 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 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. 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. This check is decisive because 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.
Question 49
A university is replacing a management VM and wants a measurable commissioning checklist for routing, time, DNS and admin access before restoring policies. Which proposed shortcut most directly risks central management compromise or failed device onboarding from unprotected factory defaults and incomplete network bootstrap 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: 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.
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. 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. The foreseeable failure is central management compromise or failed device onboarding from unprotected factory defaults and incomplete network bootstrap. The safer response 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.
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. Declare FortiManager permanently disconnected while promising live FortiGuard signatures and immediate policy installs to every remote gateway without any communication path. That shortcut risks stale management state and failed updates after treating offline staging capabilities as evidence of live connectivity. Here the specific shortcut is: 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.
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. 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: 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.
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?
Answer & Explanations
Correct answer: 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.
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.
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.
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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 3 - 10 Questions (Last Reviewed 18-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 4 - 10 Questions (Last Reviewed 17-Nov-2026)
- 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)