Fortinet FCP_FMG_AD-7.6 Dumps
Fortinet FCP_FMG_AD-7.6 Practice Test 66
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.
Question 651
A nationwide retailer has FortiGates behind residential or carrier NAT circuits and must centrally manage them without requesting universal public IP addresses. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: D
Inspect the FortiManager policy import report, identify the specific missing device interface or unresolved address object, repair the corresponding ADOM database mapping and retry the import after a scoped backup. This addresses “Localize a FortiManager import failure to missing interface mappings or objects”, where the governing principle is: Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid. The stated case instead calls for: 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.
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. This addresses “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, where the governing 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 stated case instead calls for: 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.
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: 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.
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. 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. Verify the result with this 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.
Question 652
A nationwide retailer has FortiGates behind residential or carrier NAT circuits and must centrally manage them without requesting universal public IP addresses. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: B
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: 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.
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 corresponding implementation is: 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.
Policy import depends on translating device-specific configuration into centrally defined ADOM objects; a successful FGFM connection does not make absent central mappings or unsupported fields valid. That explains “Localize a FortiManager import failure to missing interface mappings or objects”, not the mechanism behind the described change. The relevant 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.
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. That explains “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, not the mechanism behind the described change. The relevant 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.
Question 653
A nationwide retailer has FortiGates behind residential or carrier NAT circuits and must centrally manage them without requesting universal public IP addresses. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: D
Import a staging firewall with a deliberately missing interface alias, reproduce the failed import report, correct the mapping and verify the imported package represents existing rules without unwanted replacement. That would help test “Localize a FortiManager import failure to missing interface mappings or objects”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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. That would help test “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, not the outcome required in this scenario. The relevant acceptance check is: 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.
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: 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.
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. This check is decisive because 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.
Question 654
A nationwide retailer has FortiGates behind residential or carrier NAT circuits and must centrally manage them without requesting universal public IP addresses. Which proposed shortcut most directly risks remote branch management failure after ignoring direction and address reachability of the FGFM channel and should therefore be rejected?
Answer & Explanations
Correct answer: B
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. That shortcut risks unreachable central policy control after an address translation hides the actual management server from remote branches. Here the specific shortcut is: 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.
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. The foreseeable failure is remote branch management failure after ignoring direction and address reachability of the FGFM channel. The safer response is: 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.
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: 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.
Unregister and factory-reset the FortiGate whenever an import wizard reports an unresolved interface reference, without examining or preserving the live firewall policy. That shortcut risks lost production configuration and repeated import failure after troubleshooting an object mapping as a hardware fault. Here the specific shortcut is: 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.
Question 655
A nationwide retailer has FortiGates behind residential or carrier NAT circuits and must centrally manage them without requesting universal public IP addresses. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: A
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. Confirm it through this 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. 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 action is applicable: 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. 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: 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 test would be relevant: 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. 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: 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 action/test pair addresses “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”. 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. 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 case instead calls for: 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.
Question 656
An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. Which Fortinet FortiManager 7.6 administration action best addresses this requirement?
Answer & Explanations
Correct answer: C
The question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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. This addresses “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, where the governing 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 stated case instead calls for: 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.
The question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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: 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.
The question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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. 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. Verify the result with this 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.
Compare the managed device's target-specific database and retrieved FortiGate configuration with shared ADOM policy objects, identifying which layer diverges before selecting retrieve, import or install operations. This addresses “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”, where the governing principle is: Shared policy/object databases and device-specific configuration records serve different purposes; a status mismatch can arise from a local change, an uninstalled ADOM package or a missing interface map. The stated case instead calls for: 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.
Question 657
An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. The engineer proposes the following change: 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. Which mechanism explains why it works?
Answer & Explanations
Correct answer: D
The question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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: 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.
Shared policy/object databases and device-specific configuration records serve different purposes; a status mismatch can arise from a local change, an uninstalled ADOM package or a missing interface map. That explains “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”, not the mechanism behind the described change. The relevant 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 question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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. That explains “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, not the mechanism behind the described change. The relevant 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 question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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 corresponding implementation is: 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.
Question 658
An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. After implementing this change—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.—which test most directly validates its intended outcome?
Answer & Explanations
Correct answer: A
The question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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. This check is decisive because 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.
Create a harmless shared ADOM service edit and a separate local device change, inspect both database views, classify each drift and reconcile them independently through approved operations. That would help test “Compare FortiManager device-level database against ADOM-level policy objects to locate drift”, not the outcome required in this scenario. The relevant acceptance check is: 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 question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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. That would help test “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”, not the outcome required in this scenario. The relevant acceptance check is: 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 question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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: 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.
Question 659
An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. Which proposed shortcut most directly risks remote branch management failure after ignoring direction and address reachability of the FGFM channel and should therefore be rejected?
Answer & Explanations
Correct answer: B
Fix an out-of-sync device by deleting the entire customer ADOM because central and device databases must always be byte-for-byte identical at all times. That shortcut risks avoidable loss of shared policy state when device-specific drift is mistaken for corruption of the ADOM database. Here the specific shortcut is: 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.
The question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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. The foreseeable failure is remote branch management failure after ignoring direction and address reachability of the FGFM channel. The safer response is: 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.
The question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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. That shortcut risks unreachable central policy control after an address translation hides the actual management server from remote branches. Here the specific shortcut is: 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.
The question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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: 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.
Question 660
An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. Which combined implementation and verification plan is the best match for this workload?
Answer & Explanations
Correct answer: C
The action is applicable: 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. But its proposed 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.—addresses “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”. This requirement is confirmed instead by: 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 test would be relevant: 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. But the offered implementation—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.—addresses “Diagnose FortiManager behind-NAT connectivity for managed remote FortiGates”. The action needed here is: 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.
The question is set in this situation: An MSP is troubleshooting registration for a customer firewall behind an office gateway and needs to distinguish manager reachability from device-side NAT state. 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. Confirm it through this 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. 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.
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: 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.
Fortinet NSE 5 - FortiManager 7.6 Administrator (FCP_FMG_AD-7.6) Practice Tests
- 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)
- Fortinet FCP_FMG_AD-7.6 Practice Test 68 - 10 Questions (Last Reviewed 10-Nov-2026)