Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 65
Question 640
A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. 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 university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. The action is applicable: Preview how a Global ADOM header or footer policy combines with a local ADOM package, inspect applicable object mappings and rule order, and authorize the resulting configuration before installing it. But its proposed test—Create a harmless global deny rule for a test environment, assign it only to two permitted ADOMs, preview merged policy output and verify an unselected ADOM stays unchanged.—addresses “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”. This requirement is confirmed instead by: Build a lab package with a global header deny and local permit for the same test service, preview final ordering, install to a designated gateway and verify the intended deny takes precedence.
The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. The test would be relevant: Build a lab package with a global header deny and local permit for the same test service, preview final ordering, install to a designated gateway and verify the intended deny takes precedence. But the offered implementation—Create reviewed shared policy and object definitions in the supported Global ADOM, assign appropriate global policy packages to selected customer ADOMs and validate generated header or footer behavior.—addresses “Use the FortiManager Global ADOM for shared header policy without abandoning tenant isolation”. The action needed here is: Preview how a Global ADOM header or footer policy combines with a local ADOM package, inspect applicable object mappings and rule order, and authorize the resulting configuration before installing it.
The question is set in this situation: A university is testing shared global management rules and needs to show how local package order changes the effective FortiGate policy after installation. Preview how a Global ADOM header or footer policy combines with a local ADOM package, inspect applicable object mappings and rule order, and authorize the resulting configuration before installing it. Confirm it through this test: Build a lab package with a global header deny and local permit for the same test service, preview final ordering, install to a designated gateway and verify the intended deny takes precedence. A global policy section can alter effective rule evaluation order relative to local ADOM rules; merely reviewing the global rule in isolation may miss unintended permitted or denied traffic when the package is installed.
This action/test pair addresses “Rehearse supported FortiManager HA failover and operator access recovery”. Plan a supported FortiManager HA failover test including management endpoint reachability, administrator login, database state and FGFM recovery for a pilot FortiGate, then document the observed behavior and required operator actions. In an isolated lab fail the active management peer under a supported procedure, verify the expected surviving peer takes the correct role and demonstrate a harmless controlled policy installation to one test gateway. The case instead calls for: Preview how a Global ADOM header or footer policy combines with a local ADOM package, inspect applicable object mappings and rule order, and authorize the resulting configuration before installing it.
Question 641
A retail company moves FortiManager into a private data center behind an edge firewall while its remote stores retain cloud-connected FortiGates. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
When both management and managed FortiGate systems reside behind NAT, explicitly verify supported central management addresses, session direction, translated routing and firewall allowances from each side before declaring the design operational. This addresses “Plan FortiManager and FortiGate both behind separate NAT boundaries”, where the governing principle is: Two private address realms can each work locally while no valid end-to-end FGFM session exists; consistent external reachability and session initiation are separate from local ping success. The stated case instead calls for: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate. A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct. Verify the result with this test: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install.
Review which side initiates the supported FGFM management session for a FortiGate behind NAT, configure reachable control-plane addresses and permitted outbound paths, and validate authenticated enrollment before using policy installation. This addresses “Handle FortiGate behind-NAT registration without assuming direct inbound connectivity”, where the governing principle is: Branch firewalls behind address translation may not be directly dialable from FortiManager; the deployment must account for the supported device-initiated management channel and stateful NAT behavior. The stated case instead calls for: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
When FortiManager experiences a failed reload or abrupt power loss, review documented system and database integrity checks, confirm usable configuration backups and identify affected services before restarting or restoring management state. This addresses “Investigate a failed reload and central database integrity after an unclean shutdown”, where the governing principle is: Database and filesystem integrity problems differ from individual device connectivity faults; repeatedly pushing policy from a damaged manager can produce inconsistent state rather than recover the underlying management records. The stated case instead calls for: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
Question 642
A retail company moves FortiManager into a private data center behind an edge firewall while its remote stores retain cloud-connected FortiGates. The engineer proposes the following change: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate. Which mechanism explains why it works?
Answer & Explanations
Correct answer: C
Branch firewalls behind address translation may not be directly dialable from FortiManager; the deployment must account for the supported device-initiated management channel and stateful NAT behavior. That explains “Handle FortiGate behind-NAT registration without assuming direct inbound connectivity”, not the mechanism behind the described change. The relevant principle is: A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct.
Database and filesystem integrity problems differ from individual device connectivity faults; repeatedly pushing policy from a damaged manager can produce inconsistent state rather than recover the underlying management records. That explains “Investigate a failed reload and central database integrity after an unclean shutdown”, not the mechanism behind the described change. The relevant principle is: A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct.
A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct. The corresponding implementation is: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
Two private address realms can each work locally while no valid end-to-end FGFM session exists; consistent external reachability and session initiation are separate from local ping success. That explains “Plan FortiManager and FortiGate both behind separate NAT boundaries”, not the mechanism behind the described change. The relevant principle is: A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct.
Question 643
A retail company moves FortiManager into a private data center behind an edge firewall while its remote stores retain cloud-connected FortiGates. After implementing this change—When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
After a controlled laboratory unclean shutdown inspect safe supported status checks, service logs and revision availability, restore from a verified backup if needed and validate a test ADOM package. That would help test “Investigate a failed reload and central database integrity after an unclean shutdown”, not the outcome required in this scenario. The relevant acceptance check is: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install.
Build a safe lab with two independent NAT devices, establish the intended FGFM connection, inspect translated flows and show both registration and an authorized policy installation succeed. That would help test “Plan FortiManager and FortiGate both behind separate NAT boundaries”, not the outcome required in this scenario. The relevant acceptance check is: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install.
Place a test FortiGate behind a simulated branch NAT device, inspect the management session initiation and return route, and verify a central device status query and policy operation after authorization. That would help test “Handle FortiGate behind-NAT registration without assuming direct inbound connectivity”, not the outcome required in this scenario. The relevant acceptance check is: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install.
From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install. This check is decisive because a private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct.
Question 644
A retail company moves FortiManager into a private data center behind an edge firewall while its remote stores retain cloud-connected FortiGates. Which proposed shortcut most directly risks unreachable central policy control after an address translation hides the actual management server from remote branches and should therefore be rejected?
Answer & Explanations
Correct answer: A
Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test. The foreseeable failure is unreachable central policy control after an address translation hides the actual management server from remote branches. The safer response is: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
Dismiss a FortiManager database reload failure and repeatedly install the same policy to production gateways without inspecting management storage or backup integrity. That shortcut risks wider management database corruption and inconsistent installations after ignoring an underlying reload or filesystem error. Here the specific shortcut is: Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test.
Assume the identical private IP on the FortiManager and FortiGate sides guarantees mutual management through separate internet connections without routing or NAT configuration. That shortcut risks unrecoverable central connection failures caused by overlapping private addresses and unverified double-NAT design. Here the specific shortcut is: Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test.
Register a private branch FortiGate using its unroutable internal address from the public internet and assume FortiManager can initiate arbitrary inbound connections through NAT without any session setup. That shortcut risks remote branch management failure after ignoring direction and address reachability of the FGFM channel. Here the specific shortcut is: Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test.
Question 645
A retail company moves FortiManager into a private data center behind an edge firewall while its remote stores retain cloud-connected FortiGates. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate. Confirm it through this test: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install. A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct.
The test would be relevant: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install. But the offered implementation—Review which side initiates the supported FGFM management session for a FortiGate behind NAT, configure reachable control-plane addresses and permitted outbound paths, and validate authenticated enrollment before using policy installation.—addresses “Handle FortiGate behind-NAT registration without assuming direct inbound connectivity”. The action needed here is: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
The action is applicable: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate. But its proposed test—Place a test FortiGate behind a simulated branch NAT device, inspect the management session initiation and return route, and verify a central device status query and policy operation after authorization.—addresses “Handle FortiGate behind-NAT registration without assuming direct inbound connectivity”. This requirement is confirmed instead by: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install.
This action/test pair addresses “Plan FortiManager and FortiGate both behind separate NAT boundaries”. When both management and managed FortiGate systems reside behind NAT, explicitly verify supported central management addresses, session direction, translated routing and firewall allowances from each side before declaring the design operational. Build a safe lab with two independent NAT devices, establish the intended FGFM connection, inspect translated flows and show both registration and an authorized policy installation succeed. The case instead calls for: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
Question 646
A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: B
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. Review which side initiates the supported FGFM management session for a FortiGate behind NAT, configure reachable control-plane addresses and permitted outbound paths, and validate authenticated enrollment before using policy installation. This addresses “Handle FortiGate behind-NAT registration without assuming direct inbound connectivity”, where the governing principle is: Branch firewalls behind address translation may not be directly dialable from FortiManager; the deployment must account for the supported device-initiated management channel and stateful NAT behavior. The stated case instead calls for: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate. A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct. Verify the result with this test: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install.
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. When both management and managed FortiGate systems reside behind NAT, explicitly verify supported central management addresses, session direction, translated routing and firewall allowances from each side before declaring the design operational. This addresses “Plan FortiManager and FortiGate both behind separate NAT boundaries”, where the governing principle is: Two private address realms can each work locally while no valid end-to-end FGFM session exists; consistent external reachability and session initiation are separate from local ping success. The stated case instead calls for: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
Check FortiManager ADOM compatibility settings, managed FortiOS versions and feature availability when a package cannot import or install on one gateway, then plan a supported version or ADOM migration path. This addresses “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, where the governing principle is: Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM. The stated case instead calls for: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
Question 647
A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. The engineer proposes the following change: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. Two private address realms can each work locally while no valid end-to-end FGFM session exists; consistent external reachability and session initiation are separate from local ping success. That explains “Plan FortiManager and FortiGate both behind separate NAT boundaries”, not the mechanism behind the described change. The relevant principle is: A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct.
Policy and object schema is tied to supported ADOM versions; a configuration that works on one firmware generation may be invalid on another, even with healthy FGFM. That explains “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, not the mechanism behind the described change. The relevant principle is: A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct.
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. Branch firewalls behind address translation may not be directly dialable from FortiManager; the deployment must account for the supported device-initiated management channel and stateful NAT behavior. That explains “Handle FortiGate behind-NAT registration without assuming direct inbound connectivity”, not the mechanism behind the described change. The relevant principle is: A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct.
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct. The corresponding implementation is: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
Question 648
A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. After implementing this change—When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: C
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. Place a test FortiGate behind a simulated branch NAT device, inspect the management session initiation and return route, and verify a central device status query and policy operation after authorization. That would help test “Handle FortiGate behind-NAT registration without assuming direct inbound connectivity”, not the outcome required in this scenario. The relevant acceptance check is: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install.
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. Build a safe lab with two independent NAT devices, establish the intended FGFM connection, inspect translated flows and show both registration and an authorized policy installation succeed. That would help test “Plan FortiManager and FortiGate both behind separate NAT boundaries”, not the outcome required in this scenario. The relevant acceptance check is: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install.
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install. This check is decisive because a private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct.
In a lab compare a policy feature across two FortiGate versions, inspect FortiManager ADOM compatibility warnings and select a supported remediated target before installation. That would help test “Diagnose an ADOM version compatibility warning on a mixed-firmware FortiGate fleet”, not the outcome required in this scenario. The relevant acceptance check is: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install.
Question 649
A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. Which proposed shortcut most directly risks unreachable central policy control after an address translation hides the actual management server from remote branches and should therefore be rejected?
Answer & Explanations
Correct answer: A
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test. The foreseeable failure is unreachable central policy control after an address translation hides the actual management server from remote branches. The safer response is: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. Register a private branch FortiGate using its unroutable internal address from the public internet and assume FortiManager can initiate arbitrary inbound connections through NAT without any session setup. That shortcut risks remote branch management failure after ignoring direction and address reachability of the FGFM channel. Here the specific shortcut is: Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test.
Ignore a FortiOS compatibility warning and force a new unsupported policy feature to every branch simply because the latest FortiManager UI can display it. That shortcut risks rejected policy and inconsistent enforcement across device firmware variants after version support is assumed. Here the specific shortcut is: Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test.
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. Assume the identical private IP on the FortiManager and FortiGate sides guarantees mutual management through separate internet connections without routing or NAT configuration. That shortcut risks unrecoverable central connection failures caused by overlapping private addresses and unverified double-NAT design. Here the specific shortcut is: Ping the FortiManager from its own private subnet and declare all remote FortiGates correctly managed through the public NAT path without any branch-side FGFM test.
Question 650
A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The test would be relevant: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install. But the offered implementation—When both management and managed FortiGate systems reside behind NAT, explicitly verify supported central management addresses, session direction, translated routing and firewall allowances from each side before declaring the design operational.—addresses “Plan FortiManager and FortiGate both behind separate NAT boundaries”. The action needed here is: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
The action is applicable: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate. But its proposed test—Build a safe lab with two independent NAT devices, establish the intended FGFM connection, inspect translated flows and show both registration and an authorized policy installation succeed.—addresses “Plan FortiManager and FortiGate both behind separate NAT boundaries”. This requirement is confirmed instead by: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install.
The question is set in this situation: A regional bank is diagnosing why an offsite branch cannot register with FortiManager after its management VLAN was placed behind new NAT equipment. When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate. Confirm it through this test: From a branch lab firewall test the intended external manager address, inspect upstream NAT and FGFM session state, authorize registration and complete a harmless policy install. A private management IP may respond locally while a remote gateway cannot establish FGFM to the translated address; an HTTPS port-forward test alone does not prove management control traffic and identity are correct.
This action/test pair addresses “Handle FortiGate behind-NAT registration without assuming direct inbound connectivity”. Review which side initiates the supported FGFM management session for a FortiGate behind NAT, configure reachable control-plane addresses and permitted outbound paths, and validate authenticated enrollment before using policy installation. Place a test FortiGate behind a simulated branch NAT device, inspect the management session initiation and return route, and verify a central device status query and policy operation after authorization. The case instead calls for: When FortiManager is behind an upstream NAT device, plan the correct reachable management endpoint and supported FGFM routing and firewall rules, then test registration and policy delivery from an actual external FortiGate.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- Fortinet FCP_FMG_AD-7.6 Practice Test 63 - 10 Questions (Last Reviewed 15-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 64 - 10 Questions (Last Reviewed 14-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 65 - 10 Questions (Last Reviewed 13-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 66 - 10 Questions (Last Reviewed 12-Nov-2026)
- Fortinet FCP_FMG_AD-7.6 Practice Test 67 - 10 Questions (Last Reviewed 11-Nov-2026)