Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 4
Question 30
A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: B
The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. The action is applicable: Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed. But its proposed test—Run a read-only API request for the allowed test ADOM installation target, inspect both transport and JSON result status, and prove the same identity cannot change an excluded ADOM.—addresses “Authenticate and scope FortiManager JSON API operations using the correct methods”. This requirement is confirmed instead by: Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device.
The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed. Confirm it through this test: Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device. Topology visibility depends on device registration, supported telemetry and actual network relationships; a drawn fabric edge or visible hostname alone does not create device control or verify that firmware and policies are current.
The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. This action/test pair addresses “Explain central management versus FortiGate enforcement responsibilities”. Use FortiManager for centrally stored device configurations, policy packages, objects, and installation workflows while retaining each FortiGate as the traffic-enforcement point, then demonstrate which component owns each operation. Disconnect the management lab briefly, verify a FortiGate still enforces its previously installed security policy, reconnect FGFM management, and perform a documented policy installation from FortiManager. The case instead calls for: Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed.
The question is set in this situation: A public agency sees a missing firewall in its central topology map and requires a measured inventory and communication diagnosis before replacing hardware. The test would be relevant: Compare a known branch FortiGate and its neighboring devices against the topology view, inspect registration and last-contact status, and explain one deliberately disconnected test device. But the offered implementation—Use the documented FortiManager JSON-RPC API with an appropriately authorized automation identity, correct session handling and supported methods to read approved device or policy-package data before attempting a change.—addresses “Authenticate and scope FortiManager JSON API operations using the correct methods”. The action needed here is: Open the supported FortiManager topology or Fabric views for registered devices, correlate reported relationships with the approved network inventory, and investigate unexpected missing neighbors instead of presuming every discovered node is managed.
Question 31
A managed services provider is automating read-only policy-target inventory checks across customers and must prove each API identity has a limited ADOM scope. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: D
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 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.
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. This addresses “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, where the governing principle is: Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received. The stated 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.
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 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.
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. 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. Verify the result with 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.
Question 32
A managed services provider is automating read-only policy-target inventory checks across customers and must prove each API identity has a limited ADOM scope. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
FGFM management and authenticated administrator sessions depend on reachable control-plane addressing and trustworthy timing; leaving default settings or an unreachable management path can prevent device discovery and secure operation. That explains “Complete initial FortiManager system networking and administrator hardening”, not the mechanism behind the described change. The relevant principle is: 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.
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: 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.
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 corresponding implementation 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.
Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received. That explains “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, not the mechanism behind the described change. The relevant principle is: FortiManager management API requests use defined endpoints, JSON-RPC methods and session or token authorization; a successful HTTP transport response alone does not prove an internal API operation succeeded or was permitted.
Question 33
A managed services provider is automating read-only policy-target inventory checks across customers and must prove each API identity has a limited ADOM scope. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: B
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. That would help test “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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. This check is decisive because 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.
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: 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.
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: 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.
Question 34
A managed services provider is automating read-only policy-target inventory checks across customers and must prove each API identity has a limited ADOM scope. Which proposed shortcut most directly risks misreported automation success or cross-domain configuration access caused by ignoring FortiManager API authorization and status fields and should therefore be rejected?
Answer & Explanations
Correct answer: D
Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation. That shortcut risks missing security visibility after assuming central configuration automatically delivers usable analytics and log retention. Here the specific shortcut is: Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed.
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: Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed.
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: Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed.
Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed. The foreseeable failure is misreported automation success or cross-domain configuration access caused by ignoring FortiManager API authorization and status fields. The safer response 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 35
A managed services provider is automating read-only policy-target inventory checks across customers and must prove each API identity has a limited ADOM scope. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
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.
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.
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.
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.
Question 36
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 Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: A
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. 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. Verify the result with 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.
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 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. 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 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. 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. This addresses “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, where the governing principle is: Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received. The stated 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.
Question 37
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 engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: A
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. 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 corresponding implementation 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.
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. Central policy management and log analytics are related but separate functions; naming a FortiAnalyzer integration does not make FortiManager an unrestricted long-term log repository or guarantee that gateway event data is received. That explains “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, not the mechanism behind the described change. The relevant principle is: FortiManager management API requests use defined endpoints, JSON-RPC methods and session or token authorization; a successful HTTP transport response alone does not prove an internal API operation succeeded or was permitted.
The 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. 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: 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.
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: 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.
Question 38
A bank's change automation receives HTTP success but its expected FortiManager policy status is unchanged and requires diagnosis of JSON-RPC operation results. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
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. 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: 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.
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: 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. 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. That would help test “Choose FortiManager integrated logging versus dedicated FortiAnalyzer capabilities”, not the outcome required in this scenario. The relevant acceptance check is: 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. 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. This check is decisive because 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.
Question 39
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 proposed shortcut most directly risks misreported automation success or cross-domain configuration access caused by ignoring FortiManager API authorization and status fields and should therefore be rejected?
Answer & Explanations
Correct answer: B
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. Deploy FortiManager, leave every gateway without any logging destination, and report that FortiAnalyzer security reports must appear automatically after policy installation. That shortcut risks missing security visibility after assuming central configuration automatically delivers usable analytics and log retention. Here the specific shortcut is: Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed.
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. Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed. The foreseeable failure is misreported automation success or cross-domain configuration access caused by ignoring FortiManager API authorization and status fields. The safer response 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.
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. 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: Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed.
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: Send unauthenticated arbitrary HTTP PUT bodies to the FortiManager root URL and assume every HTTP 200 result means an approved configuration change was installed.
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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 2 - 10 Questions (Last Reviewed 19-Nov-2026)
- 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)