FCP_FGT_AD-7.6 Premium File
- 128 Questions & Answers
- Last Update: Oct 26, 2026
During a configuration recovery exercise, a cloud-connected FortiGate negotiates through an upstream translator but data traffic fails without encapsulation. What should the FortiGate administrator change to meet the stated requirement?
Ensure compatible IPsec NAT traversal and upstream UDP 500/4500 reachability where NAT exists. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. This corrects the FortiGate behavior described by the specific NAT traversal UDP 4500 fault.
Changing this could help when the fault is preshared key disagreement, because a preshared key authenticates the expected IKE peer and must match at both ends. Here the evidence instead identifies NAT traversal UDP 4500; the recommended correction addresses that dependency.
The proposed setting concerns partial mesh branch IPsec design, not the actual source of failure. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. It would leave the cited symptom unresolved.
This correction targets IKE version mismatch. Peers must agree on the IKE protocol and associated negotiation capabilities. It does not repair the stated NAT traversal UDP 4500 condition: a cloud-connected FortiGate negotiates through an upstream translator but data traffic fails without encapsulation.
An e-commerce platform discovers a FortiGate control gap during a new branch activation: an IPsec peer sits behind NAT and IKE starts but ESP traffic cannot traverse the translation device; additionally, a cloud-connected FortiGate negotiates through an upstream translator but data traffic fails without encapsulation. Which targeted correction should the team implement?
Ensure compatible IPsec NAT traversal and upstream UDP 500/4500 reachability where NAT exists. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. This corrects the FortiGate behavior described by the specific NAT traversal UDP 4500 fault.
This correction targets redundant tunnel preferences. Redundant VPNs need routing or SD-WAN policy that distinguishes preferred and alternate protected paths. It does not repair the stated NAT traversal UDP 4500 condition: an IPsec peer sits behind NAT and IKE starts but ESP traffic cannot traverse the translation device.
Changing this could help when the fault is PFS group mismatch, because pFS contributes fresh key material to child-SA negotiation and requires peer agreement. Here the evidence instead identifies NAT traversal UDP 4500; the recommended correction addresses that dependency.
The proposed setting concerns partial mesh branch IPsec design, not the actual source of failure. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. It would leave the cited symptom unresolved.
The international service desk team is verifying its fix for an incident where an IPsec peer sits behind NAT and IKE starts but ESP traffic cannot traverse the translation device. Which specific observation most convincingly demonstrates the required FortiGate behavior?
Negotiated NAT-T traffic uses supported UDP encapsulation and tunnel packet counters increase. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. This is directly observable evidence for the NAT traversal UDP 4500 requirement, rather than a generic appliance-health indicator.
That observation is a useful test for IKE version mismatch, but not decisive proof of NAT traversal UDP 4500. Peers must agree on the IKE protocol and associated negotiation capabilities. The recorded acceptance check must demonstrate the actual requirement.
A result about DPD peer liveness can be true while the NAT traversal UDP 4500 defect persists. DPD detects IKE peer loss when a tunnel stops responding to liveness exchanges. It does not validate the tested dependency.
That observation is a useful test for backup tunnel health validation, but not decisive proof of NAT traversal UDP 4500. Redundancy is useful only when both candidate VPN paths can negotiate and forward traffic. The recorded acceptance check must demonstrate the actual requirement.
After a weekend failover rehearsal, administrators correct a problem where a cloud-connected FortiGate negotiates through an upstream translator but data traffic fails without encapsulation. Which test result should their acceptance record contain?
Negotiated NAT-T traffic uses supported UDP encapsulation and tunnel packet counters increase. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. This is directly observable evidence for the NAT traversal UDP 4500 requirement, rather than a generic appliance-health indicator.
This verifies a different control: certificate-based VPN peer trust. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. The stated incident requires evidence of its own packet, identity or policy behavior.
A result about IKE version mismatch can be true while the NAT traversal UDP 4500 defect persists. Peers must agree on the IKE protocol and associated negotiation capabilities. It does not validate the tested dependency.
This verifies a different control: IPsec tunnel diagnostics and logging. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. The stated incident requires evidence of its own packet, identity or policy behavior.
An auditor reviewing a financial services branch deployment finds that an IPsec peer sits behind NAT and IKE starts but ESP traffic cannot traverse the translation device. The team claims this is resolved; which concrete evidence would substantiate that claim?
Negotiated NAT-T traffic uses supported UDP encapsulation and tunnel packet counters increase. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. This is directly observable evidence for the NAT traversal UDP 4500 requirement, rather than a generic appliance-health indicator.
A result about IKE Phase 1 proposal mismatch can be true while the NAT traversal UDP 4500 defect persists. IKE Phase 1 establishes the protected control channel and needs mutually supported cryptographic negotiation. It does not validate the tested dependency.
That observation is a useful test for PFS group mismatch, but not decisive proof of NAT traversal UDP 4500. PFS contributes fresh key material to child-SA negotiation and requires peer agreement. The recorded acceptance check must demonstrate the actual requirement.
This verifies a different control: IPsec MTU and MSS fragmentation. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. The stated incident requires evidence of its own packet, identity or policy behavior.
If a multi-site university leaves the following FortiGate issue unresolved—an IPsec peer sits behind NAT and IKE starts but ESP traffic cannot traverse the translation device—what is the most direct operational or security consequence?
NAT devices may not forward raw ESP correctly without suitable NAT traversal. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. The described exposure follows from leaving the NAT traversal UDP 4500 dependency unresolved.
It would be a concern if preshared key disagreement were misconfigured. Here IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. The selected alternative does not follow from the observed fault.
This describes a separate VPN identity mismatch behind NAT failure. IKE identity matching is distinct from outer IP addressing and affects dynamic-peer authentication. It does not identify the most direct consequence of leaving NAT traversal UDP 4500 unresolved.
That risk is associated with IPsec MTU and MSS fragmentation rather than the failing NAT traversal UDP 4500 dependency. IPsec overhead reduces effective payload size and requires correct MTU or MSS handling on constrained paths. The present scenario establishes a different causal exposure.
During an incident-response triage, engineers discover that a cloud-connected FortiGate negotiates through an upstream translator but data traffic fails without encapsulation. What specific failure risk follows if the underlying fault remains?
NAT devices may not forward raw ESP correctly without suitable NAT traversal. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. The described exposure follows from leaving the NAT traversal UDP 4500 dependency unresolved.
It would be a concern if IPsec tunnel diagnostics and logging were misconfigured. Here IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. The selected alternative does not follow from the observed fault.
That risk is associated with redundant tunnel preferences rather than the failing NAT traversal UDP 4500 dependency. Redundant VPNs need routing or SD-WAN policy that distinguishes preferred and alternate protected paths. The present scenario establishes a different causal exposure.
It would be a concern if PFS group mismatch were misconfigured. Here IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. The selected alternative does not follow from the observed fault.
A post-incident review at a supply-chain company identifies that an IPsec peer sits behind NAT and IKE starts but ESP traffic cannot traverse the translation device. The same control is still uncorrected. Which exposure should the risk register record?
NAT devices may not forward raw ESP correctly without suitable NAT traversal. IPsec NAT-T encapsulates ESP in UDP for compatible paths that cross NAT. The described exposure follows from leaving the NAT traversal UDP 4500 dependency unresolved.
This describes a separate preshared key disagreement failure. A preshared key authenticates the expected IKE peer and must match at both ends. It does not identify the most direct consequence of leaving NAT traversal UDP 4500 unresolved.
That risk is associated with PFS group mismatch rather than the failing NAT traversal UDP 4500 dependency. PFS contributes fresh key material to child-SA negotiation and requires peer agreement. The present scenario establishes a different causal exposure.
This describes a separate certificate-based VPN peer trust failure. Certificate-based IKE authentication relies on chain validation, identity matching and acceptable certificate validity. It does not identify the most direct consequence of leaving NAT traversal UDP 4500 unresolved.
At a customer support center running FortiOS 7.6, small packets cross an IPsec tunnel but large HTTPS payloads stall after encapsulation overhead. Which configuration or investigative change most directly resolves this issue?
Diagnose tunnel PMTU and configure supported TCP MSS or interface MTU adjustments. IPsec overhead reduces effective payload size and requires correct MTU or MSS handling on constrained paths. This corrects the FortiGate behavior described by the specific IPsec MTU and MSS fragmentation fault.
This correction targets IKE Phase 1 proposal mismatch. IKE Phase 1 establishes the protected control channel and needs mutually supported cryptographic negotiation. It does not repair the stated IPsec MTU and MSS fragmentation condition: small packets cross an IPsec tunnel but large HTTPS payloads stall after encapsulation overhead.
Changing this could help when the fault is DPD peer liveness, because dPD detects IKE peer loss when a tunnel stops responding to liveness exchanges. Here the evidence instead identifies IPsec MTU and MSS fragmentation; the recommended correction addresses that dependency.
The proposed setting concerns wrong remote gateway identity, not the actual source of failure. IPsec overhead reduces effective payload size and requires correct MTU or MSS handling on constrained paths. It would leave the cited symptom unresolved.
During a segmentation review, a site-to-site VPN works for ping while larger TCP data flows blackhole with Path MTU discovery restricted. What should the FortiGate administrator change to meet the stated requirement?
Diagnose tunnel PMTU and configure supported TCP MSS or interface MTU adjustments. IPsec overhead reduces effective payload size and requires correct MTU or MSS handling on constrained paths. This corrects the FortiGate behavior described by the specific IPsec MTU and MSS fragmentation fault.
The proposed setting concerns NAT traversal UDP 4500, not the actual source of failure. IPsec overhead reduces effective payload size and requires correct MTU or MSS handling on constrained paths. It would leave the cited symptom unresolved.
This correction targets IPsec inter-site firewall policies. IPsec negotiation and FortiGate firewall authorization operate at separate layers. It does not repair the stated IPsec MTU and MSS fragmentation condition: a site-to-site VPN works for ping while larger TCP data flows blackhole with Path MTU discovery restricted.
Changing this could help when the fault is IKE version mismatch, because peers must agree on the IKE protocol and associated negotiation capabilities. Here the evidence instead identifies IPsec MTU and MSS fragmentation; the recommended correction addresses that dependency.
A managed services provider discovers a FortiGate control gap during a incident-response triage: small packets cross an IPsec tunnel but large HTTPS payloads stall after encapsulation overhead; additionally, a site-to-site VPN works for ping while larger TCP data flows blackhole with Path MTU discovery restricted. Which targeted correction should the team implement?
Diagnose tunnel PMTU and configure supported TCP MSS or interface MTU adjustments. IPsec overhead reduces effective payload size and requires correct MTU or MSS handling on constrained paths. This corrects the FortiGate behavior described by the specific IPsec MTU and MSS fragmentation fault.
The proposed setting concerns Phase 2 selector mismatch, not the actual source of failure. IPsec overhead reduces effective payload size and requires correct MTU or MSS handling on constrained paths. It would leave the cited symptom unresolved.
Changing this could help when the fault is IPsec inter-site firewall policies, because iPsec negotiation and FortiGate firewall authorization operate at separate layers. Here the evidence instead identifies IPsec MTU and MSS fragmentation; the recommended correction addresses that dependency.
The proposed setting concerns partial mesh branch IPsec design, not the actual source of failure. IPsec overhead reduces effective payload size and requires correct MTU or MSS handling on constrained paths. It would leave the cited symptom unresolved.
Please check your mailbox for a message from support@examlabs.com and follow the directions.