Fortinet NSE4_FGT_AD-7.6 Dumps
Fortinet NSE4_FGT_AD-7.6 Practice Test 70
Question 690
At a managed branch perimeter, a FortiGate running FortiOS 7.6 has this observation: A VPN uses certificates but one peer rejects the other's identity because its trust chain or ID does not match. The operator corrected the configuration by choosing to validate the certificate trust chain and IKE peer identity configuration on both gateways. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.
Explanation
Correct Answers
It measures the operational result after the correction to validate the certificate trust chain and IKE peer identity configuration on both gateways, and it directly checks the reported condition: a VPN uses certificates but one peer rejects the other's identity because its trust chain or ID does not match. For certificate-based ipsec identity, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.
The organization already encountered the failure where a VPN uses certificates but one peer rejects the other's identity because its trust chain or ID does not match, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to inspect certificate validation logs and confirm trusted peer identity on reconnection, this gate checks future revisions without claiming that the current configuration is permanently correct.
Incorrect Answers
The proposed evidence, to test branch-to-hub and authorized interbranch reachability through the planned hub, checks hub-and-spoke overlay in a situation such as several small branch sites need central secure reachability without maintaining a full mesh of direct tunnels, not the required certificate-based ipsec identity acceptance. For the affected firewall behavior the directly discriminating check is to inspect certificate validation logs and confirm trusted peer identity on reconnection, alongside a review of certificate-based ipsec identity rather than hub-and-spoke overlay settings.
The proposed evidence, to read the IKE transform error and confirm a shared proposal establishes phase one, checks phase-one encryption proposal in a situation such as two IKE peers reach one another but cannot negotiate a common phase-one transform, not the required certificate-based ipsec identity acceptance. For the affected firewall behavior the directly discriminating check is to inspect certificate validation logs and confirm trusted peer identity on reconnection, alongside a review of certificate-based ipsec identity rather than phase-one encryption proposal settings.
The proposed evidence, to inspect child-SA negotiation and verify the agreed PFS group is accepted, checks perfect forward secrecy mismatch in a situation such as peers establish IKE but phase-two negotiation fails after the PFS setting was changed on only one side, not the required certificate-based ipsec identity acceptance. For the affected firewall behavior the directly discriminating check is to inspect certificate validation logs and confirm trusted peer identity on reconnection, alongside a review of certificate-based ipsec identity rather than perfect forward secrecy mismatch settings.
Question 691
A FortiOS 7.6 review of a datacenter security boundary reports the following condition: Small pings succeed across the IPsec tunnel but large application transactions fail after encapsulation overhead is added. The requirement concerns vpn path mtu and fragmentation while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?
Explanation
Correct Answer
Choosing to investigate tunnel MTU and PMTU or MSS behavior and apply a supported scoped correction changes the component implicated by that observation, rather than masking the symptom through a different firewall feature. Operators can substantiate the choice by carrying out this test: test increasing payload sizes and verify the largest permitted application flow succeeds.
Incorrect Answers
Selecting align phase-two source and destination selectors with the mirrored protected subnets on both peers would focus the new configuration on phase-two traffic selectors, for which iKE phase one succeeds but no child SA protects the intended office subnets because selectors disagree may be a valid concern, but this vpn path mtu and fragmentation configuration has a different failure. Evidence for vpn path mtu and fragmentation requires staff to test increasing payload sizes and verify the largest permitted application flow succeeds; the proposed phase-two traffic selectors change cannot deliver that vpn path mtu and fragmentation result by itself.
Enabling compatible NAT traversal and ensure UDP 500 and 4500 reach the correct gateway would focus the new configuration on nat traversal for ipsec, for which a branch gateway is behind upstream address translation and the IPsec session cannot reliably use native ESP may be a valid concern, but this vpn path mtu and fragmentation configuration has a different failure. Evidence for vpn path mtu and fragmentation requires staff to test increasing payload sizes and verify the largest permitted application flow succeeds; the proposed nat traversal for ipsec change cannot deliver that vpn path mtu and fragmentation result by itself.
Using the configured interface-based IPsec tunnel consistently in routing and firewall policies would focus the new configuration on interface-based tunnel policy, for which an engineer mixes a route-based tunnel interface design with expectations from legacy policy-based VPN selectors may be a valid concern, but this vpn path mtu and fragmentation configuration has a different failure. Evidence for vpn path mtu and fragmentation requires staff to test increasing payload sizes and verify the largest permitted application flow succeeds; the proposed interface-based tunnel policy change cannot deliver that vpn path mtu and fragmentation result by itself.
Question 692
During FortiOS 7.6 operations at an enterprise gateway change window, the evidence is: Small pings succeed across the IPsec tunnel but large application transactions fail after encapsulation overhead is added. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this vpn path mtu and fragmentation failure?
Explanation
Correct Answer
The problem arises when administrators reduce firewall log retention to solve an encrypted packet-size failure, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to investigate tunnel MTU and PMTU or MSS behavior and apply a supported scoped correction.
Incorrect Answers
The alternative cause involving nat traversal for ipsec can produce a different failure, for example when a branch gateway is behind upstream address translation and the IPsec session cannot reliably use native ESP; it is not the vpn path mtu and fragmentation case. The more specific error here is the choice to reduce firewall log retention to solve an encrypted packet-size failure; check it by attempting to test increasing payload sizes and verify the largest permitted application flow succeeds before making an unrelated nat traversal for ipsec change.
The alternative cause involving phase-two traffic selectors can produce a different failure, for example when iKE phase one succeeds but no child SA protects the intended office subnets because selectors disagree; it is not the vpn path mtu and fragmentation case. The more specific error here is the choice to reduce firewall log retention to solve an encrypted packet-size failure; check it by attempting to test increasing payload sizes and verify the largest permitted application flow succeeds before making an unrelated phase-two traffic selectors change.
The alternative cause involving interface-based tunnel policy can produce a different failure, for example when an engineer mixes a route-based tunnel interface design with expectations from legacy policy-based VPN selectors; it is not the vpn path mtu and fragmentation case. The more specific error here is the choice to reduce firewall log retention to solve an encrypted packet-size failure; check it by attempting to test increasing payload sizes and verify the largest permitted application flow succeeds before making an unrelated interface-based tunnel policy change.
Question 693
At a redundant regional firewall pair, a FortiGate running FortiOS 7.6 has this observation: Small pings succeed across the IPsec tunnel but large application transactions fail after encapsulation overhead is added. Investigators confirmed this cause: administrators chose to reduce firewall log retention to solve an encrypted packet-size failure. Which action MOST directly corrects the confirmed error?
Explanation
Correct Answer
This addresses vpn path mtu and fragmentation without needlessly weakening separate security or routing controls. Given the observed condition—small pings succeed across the IPsec tunnel but large application transactions fail after encapsulation overhead is added—the operator should then test increasing payload sizes and verify the largest permitted application flow succeeds.
Incorrect Answers
Changing the mechanism to enable compatible NAT traversal and ensure UDP 500 and 4500 reach the correct gateway could be a sensible correction for nat traversal for ipsec when a branch gateway is behind upstream address translation and the IPsec session cannot reliably use native ESP. The targeted fix is to investigate tunnel MTU and PMTU or MSS behavior and apply a supported scoped correction; a review of nat traversal for ipsec would not, by itself, prove that the team can test increasing payload sizes and verify the largest permitted application flow succeeds.
The proposal repeats the confirmed vpn path mtu and fragmentation error by choosing to reduce firewall log retention to solve an encrypted packet-size failure. A corrective change must instead investigate tunnel MTU and PMTU or MSS behavior and apply a supported scoped correction and then produce the measurable result to test increasing payload sizes and verify the largest permitted application flow succeeds; repeating the failed setting cannot serve as a repair.
Changing the mechanism to use the configured interface-based IPsec tunnel consistently in routing and firewall policies could be a sensible correction for interface-based tunnel policy when an engineer mixes a route-based tunnel interface design with expectations from legacy policy-based VPN selectors. The targeted fix is to investigate tunnel MTU and PMTU or MSS behavior and apply a supported scoped correction; a review of interface-based tunnel policy would not, by itself, prove that the team can test increasing payload sizes and verify the largest permitted application flow succeeds.
Question 694
A FortiOS 7.6 review of a remote-office migration reports the following condition: Small pings succeed across the IPsec tunnel but large application transactions fail after encapsulation overhead is added. The incident has been fixed, and the owner wants to prevent a recurrence of the vpn path mtu and fragmentation problem. Which future change-control rule is MOST appropriate?
Explanation
Correct Answer
This change-control gate requires teams to require peer review for vpn path mtu and fragmentation changes and an acceptance check that will test increasing payload sizes and verify the largest permitted application flow succeeds before relevant releases, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to test increasing payload sizes and verify the largest permitted application flow succeeds.
Incorrect Answers
A review gate for interface-based tunnel policy, such as require peer review for interface-based tunnel policy changes and an acceptance check that will confirm the new session routes to the virtual IPsec interface and matches the tunnel policy before relevant releases, can be useful where an engineer mixes a route-based tunnel interface design with expectations from legacy policy-based VPN selectors, but it is not the approved vpn path mtu and fragmentation review. The preventive test must enforce that staff will investigate tunnel MTU and PMTU or MSS behavior and apply a supported scoped correction and subsequently can test increasing payload sizes and verify the largest permitted application flow succeeds; the proposed interface-based tunnel policy gate would not check that same control.
A review gate for phase-two traffic selectors, such as require peer review for phase-two traffic selectors changes and an acceptance check that will bring up a child SA and confirm traffic between the selected office subnets increments counters before relevant releases, can be useful where iKE phase one succeeds but no child SA protects the intended office subnets because selectors disagree, but it is not the approved vpn path mtu and fragmentation review. The preventive test must enforce that staff will investigate tunnel MTU and PMTU or MSS behavior and apply a supported scoped correction and subsequently can test increasing payload sizes and verify the largest permitted application flow succeeds; the proposed phase-two traffic selectors gate would not check that same control.
A review gate for nat traversal for ipsec, such as require peer review for nat traversal for ipsec changes and an acceptance check that will observe UDP-encapsulated IPsec negotiation and successful tunnel traffic behind the NAT before relevant releases, can be useful where a branch gateway is behind upstream address translation and the IPsec session cannot reliably use native ESP, but it is not the approved vpn path mtu and fragmentation review. The preventive test must enforce that staff will investigate tunnel MTU and PMTU or MSS behavior and apply a supported scoped correction and subsequently can test increasing payload sizes and verify the largest permitted application flow succeeds; the proposed nat traversal for ipsec gate would not check that same control.
Question 695
During FortiOS 7.6 operations at a monitored business uplink, the evidence is: Small pings succeed across the IPsec tunnel but large application transactions fail after encapsulation overhead is added. The operator corrected the configuration by choosing to investigate tunnel MTU and PMTU or MSS behavior and apply a supported scoped correction. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.
Explanation
Correct Answers
It measures the operational result after the correction to investigate tunnel MTU and PMTU or MSS behavior and apply a supported scoped correction, and it directly checks the reported condition: small pings succeed across the IPsec tunnel but large application transactions fail after encapsulation overhead is added. For vpn path mtu and fragmentation, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.
The organization already encountered the failure where small pings succeed across the IPsec tunnel but large application transactions fail after encapsulation overhead is added, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to test increasing payload sizes and verify the largest permitted application flow succeeds, this gate checks future revisions without claiming that the current configuration is permanently correct.
Incorrect Answers
The proposed evidence, to bring up a child SA and confirm traffic between the selected office subnets increments counters, checks phase-two traffic selectors in a situation such as iKE phase one succeeds but no child SA protects the intended office subnets because selectors disagree, not the required vpn path mtu and fragmentation acceptance. For the affected firewall behavior the directly discriminating check is to test increasing payload sizes and verify the largest permitted application flow succeeds, alongside a review of vpn path mtu and fragmentation rather than phase-two traffic selectors settings.
The proposed evidence, to confirm the new session routes to the virtual IPsec interface and matches the tunnel policy, checks interface-based tunnel policy in a situation such as an engineer mixes a route-based tunnel interface design with expectations from legacy policy-based VPN selectors, not the required vpn path mtu and fragmentation acceptance. For the affected firewall behavior the directly discriminating check is to test increasing payload sizes and verify the largest permitted application flow succeeds, alongside a review of vpn path mtu and fragmentation rather than interface-based tunnel policy settings.
The proposed evidence, to observe UDP-encapsulated IPsec negotiation and successful tunnel traffic behind the NAT, checks nat traversal for ipsec in a situation such as a branch gateway is behind upstream address translation and the IPsec session cannot reliably use native ESP, not the required vpn path mtu and fragmentation acceptance. For the affected firewall behavior the directly discriminating check is to test increasing payload sizes and verify the largest permitted application flow succeeds, alongside a review of vpn path mtu and fragmentation rather than nat traversal for ipsec settings.
Question 696
At an internal application segment, a FortiGate running FortiOS 7.6 has this observation: The branch moves to its secondary tunnel during an outage but fails to return preferred new flows when the primary is restored. The requirement concerns redundant tunnel failback while retaining existing unrelated controls. Which FortiGate change MOST directly meets the requirement?
Explanation
Correct Answer
Choosing to review tunnel health monitoring and route priority for orderly primary recovery and new-flow selection changes the component implicated by that observation, rather than masking the symptom through a different firewall feature. Operators can substantiate the choice by carrying out this test: restore the primary transport and inspect new session routing and tunnel health.
Incorrect Answers
Configuring and test an appropriate dead-peer detection policy for the IPsec link would focus the new configuration on dead-peer detection, for which a primary tunnel remains considered usable long after its remote peer disappears, delaying redundant VPN recovery may be a valid concern, but this redundant tunnel failback configuration has a different failure. Evidence for redundant tunnel failback requires staff to restore the primary transport and inspect new session routing and tunnel health; the proposed dead-peer detection change cannot deliver that redundant tunnel failback result by itself.
Selecting align phase-two PFS settings and compatible Diffie-Hellman groups across the endpoints would focus the new configuration on perfect forward secrecy mismatch, for which peers establish IKE but phase-two negotiation fails after the PFS setting was changed on only one side may be a valid concern, but this redundant tunnel failback configuration has a different failure. Evidence for redundant tunnel failback requires staff to restore the primary transport and inspect new session routing and tunnel health; the proposed perfect forward secrecy mismatch change cannot deliver that redundant tunnel failback result by itself.
Inspecting phase-two proposals, selector symmetry, and PFS alignment instead of rebuilding phase one blindly would focus the new configuration on phase-one up phase-two down, for which vPN status shows IKE SA established but traffic selectors cannot negotiate a usable child SA may be a valid concern, but this redundant tunnel failback configuration has a different failure. Evidence for redundant tunnel failback requires staff to restore the primary transport and inspect new session routing and tunnel health; the proposed phase-one up phase-two down change cannot deliver that redundant tunnel failback result by itself.
Question 697
A FortiOS 7.6 review of a hybrid-network deployment reports the following condition: The branch moves to its secondary tunnel during an outage but fails to return preferred new flows when the primary is restored. Basic reachability and unrelated systems have already been checked. Which configuration mistake BEST explains this redundant tunnel failback failure?
Explanation
Correct Answer
The problem arises when administrators give the secondary VPN route permanently better preference than the intended primary, so the failing behavior has a concrete configuration cause and is not inferred from an unrelated metric. The relevant repair is to review tunnel health monitoring and route priority for orderly primary recovery and new-flow selection.
Incorrect Answers
The alternative cause involving phase-one up phase-two down can produce a different failure, for example when vPN status shows IKE SA established but traffic selectors cannot negotiate a usable child SA; it is not the redundant tunnel failback case. The more specific error here is the choice to give the secondary VPN route permanently better preference than the intended primary; check it by attempting to restore the primary transport and inspect new session routing and tunnel health before making an unrelated phase-one up phase-two down change.
The alternative cause involving perfect forward secrecy mismatch can produce a different failure, for example when peers establish IKE but phase-two negotiation fails after the PFS setting was changed on only one side; it is not the redundant tunnel failback case. The more specific error here is the choice to give the secondary VPN route permanently better preference than the intended primary; check it by attempting to restore the primary transport and inspect new session routing and tunnel health before making an unrelated perfect forward secrecy mismatch change.
The alternative cause involving dead-peer detection can produce a different failure, for example when a primary tunnel remains considered usable long after its remote peer disappears, delaying redundant VPN recovery; it is not the redundant tunnel failback case. The more specific error here is the choice to give the secondary VPN route permanently better preference than the intended primary; check it by attempting to restore the primary transport and inspect new session routing and tunnel health before making an unrelated dead-peer detection change.
Question 698
During FortiOS 7.6 operations at an operations incident response, the evidence is: The branch moves to its secondary tunnel during an outage but fails to return preferred new flows when the primary is restored. Investigators confirmed this cause: administrators chose to give the secondary VPN route permanently better preference than the intended primary. Which action MOST directly corrects the confirmed error?
Explanation
Correct Answer
This addresses redundant tunnel failback without needlessly weakening separate security or routing controls. Given the observed condition—the branch moves to its secondary tunnel during an outage but fails to return preferred new flows when the primary is restored—the operator should then restore the primary transport and inspect new session routing and tunnel health.
Incorrect Answers
Changing the mechanism to configure and test an appropriate dead-peer detection policy for the IPsec link could be a sensible correction for dead-peer detection when a primary tunnel remains considered usable long after its remote peer disappears, delaying redundant VPN recovery. The targeted fix is to review tunnel health monitoring and route priority for orderly primary recovery and new-flow selection; a review of dead-peer detection would not, by itself, prove that the team can restore the primary transport and inspect new session routing and tunnel health.
Changing the mechanism to inspect phase-two proposals, selector symmetry, and PFS alignment instead of rebuilding phase one blindly could be a sensible correction for phase-one up phase-two down when vPN status shows IKE SA established but traffic selectors cannot negotiate a usable child SA. The targeted fix is to review tunnel health monitoring and route priority for orderly primary recovery and new-flow selection; a review of phase-one up phase-two down would not, by itself, prove that the team can restore the primary transport and inspect new session routing and tunnel health.
The proposal repeats the confirmed redundant tunnel failback error by choosing to give the secondary VPN route permanently better preference than the intended primary. A corrective change must instead review tunnel health monitoring and route priority for orderly primary recovery and new-flow selection and then produce the measurable result to restore the primary transport and inspect new session routing and tunnel health; repeating the failed setting cannot serve as a repair.
Question 699
At a network segmentation review, a FortiGate running FortiOS 7.6 has this observation: The branch moves to its secondary tunnel during an outage but fails to return preferred new flows when the primary is restored. The incident has been fixed, and the owner wants to prevent a recurrence of the redundant tunnel failback problem. Which future change-control rule is MOST appropriate?
Explanation
Correct Answer
This change-control gate requires teams to require peer review for redundant tunnel failback changes and an acceptance check that will restore the primary transport and inspect new session routing and tunnel health before relevant releases, so it catches a repeat of the known misconfiguration before broad deployment. Its success can be checked against the operational evidence to restore the primary transport and inspect new session routing and tunnel health.
Incorrect Answers
A review gate for phase-one up phase-two down, such as require peer review for phase-one up phase-two down changes and an acceptance check that will examine IKE diagnostics and confirm the child SA builds with intended selectors before relevant releases, can be useful where vPN status shows IKE SA established but traffic selectors cannot negotiate a usable child SA, but it is not the approved redundant tunnel failback review. The preventive test must enforce that staff will review tunnel health monitoring and route priority for orderly primary recovery and new-flow selection and subsequently can restore the primary transport and inspect new session routing and tunnel health; the proposed phase-one up phase-two down gate would not check that same control.
A review gate for dead-peer detection, such as require peer review for dead-peer detection changes and an acceptance check that will disconnect the test peer and measure DPD detection and redundant path activation before relevant releases, can be useful where a primary tunnel remains considered usable long after its remote peer disappears, delaying redundant VPN recovery, but it is not the approved redundant tunnel failback review. The preventive test must enforce that staff will review tunnel health monitoring and route priority for orderly primary recovery and new-flow selection and subsequently can restore the primary transport and inspect new session routing and tunnel health; the proposed dead-peer detection gate would not check that same control.
A review gate for perfect forward secrecy mismatch, such as require peer review for perfect forward secrecy mismatch changes and an acceptance check that will inspect child-SA negotiation and verify the agreed PFS group is accepted before relevant releases, can be useful where peers establish IKE but phase-two negotiation fails after the PFS setting was changed on only one side, but it is not the approved redundant tunnel failback review. The preventive test must enforce that staff will review tunnel health monitoring and route priority for orderly primary recovery and new-flow selection and subsequently can restore the primary transport and inspect new session routing and tunnel health; the proposed perfect forward secrecy mismatch gate would not check that same control.
Question 700
A FortiOS 7.6 review of a managed branch perimeter reports the following condition: The branch moves to its secondary tunnel during an outage but fails to return preferred new flows when the primary is restored. The operator corrected the configuration by choosing to review tunnel health monitoring and route priority for orderly primary recovery and new-flow selection. Select TWO answers that together provide a falsifiable acceptance test and a preventive change gate.
Explanation
Correct Answers
The organization already encountered the failure where the branch moves to its secondary tunnel during an outage but fails to return preferred new flows when the primary is restored, so every relevant future change should be reviewed for the same hazard. Combined with the separate acceptance test to restore the primary transport and inspect new session routing and tunnel health, this gate checks future revisions without claiming that the current configuration is permanently correct.
It measures the operational result after the correction to review tunnel health monitoring and route priority for orderly primary recovery and new-flow selection, and it directly checks the reported condition: the branch moves to its secondary tunnel during an outage but fails to return preferred new flows when the primary is restored. For redundant tunnel failback, a saved profile or healthy dashboard alone would not verify that the affected flow behaves as required.
Incorrect Answers
The proposed evidence, to disconnect the test peer and measure DPD detection and redundant path activation, checks dead-peer detection in a situation such as a primary tunnel remains considered usable long after its remote peer disappears, delaying redundant VPN recovery, not the required redundant tunnel failback acceptance. For the affected firewall behavior the directly discriminating check is to restore the primary transport and inspect new session routing and tunnel health, alongside a review of redundant tunnel failback rather than dead-peer detection settings.
The proposed evidence, to inspect child-SA negotiation and verify the agreed PFS group is accepted, checks perfect forward secrecy mismatch in a situation such as peers establish IKE but phase-two negotiation fails after the PFS setting was changed on only one side, not the required redundant tunnel failback acceptance. For the affected firewall behavior the directly discriminating check is to restore the primary transport and inspect new session routing and tunnel health, alongside a review of redundant tunnel failback rather than perfect forward secrecy mismatch settings.
The proposed evidence, to examine IKE diagnostics and confirm the child SA builds with intended selectors, checks phase-one up phase-two down in a situation such as vPN status shows IKE SA established but traffic selectors cannot negotiate a usable child SA, not the required redundant tunnel failback acceptance. For the affected firewall behavior the directly discriminating check is to restore the primary transport and inspect new session routing and tunnel health, alongside a review of redundant tunnel failback rather than phase-one up phase-two down settings.
Fortinet NSE 4 - FortiOS 7.6 Administrator (NSE4_FGT_AD-7.6) Practice Tests
- Fortinet NSE4_FGT_AD-7.6 Practice Test 68 - 10 Questions (Last Reviewed 10-Nov-2026)
- Fortinet NSE4_FGT_AD-7.6 Practice Test 69 - 10 Questions (Last Reviewed 09-Nov-2026)
- Fortinet NSE4_FGT_AD-7.6 Practice Test 70 - 10 Questions (Last Reviewed 08-Nov-2026)