cert
cert-1
cert-2

Pass Fortinet NSE4_FGT_AD-7.6 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
NSE4_FGT_AD-7.6 Exam - Verified By Experts
NSE4_FGT_AD-7.6 Premium File

NSE4_FGT_AD-7.6 Premium File

$69.99
$76.99
  • Premium File 94 Questions & Answers. Last Update: Nov 19, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 234 downloads in the last 7 days
block-screenshots
Fortinet NSE4_FGT_AD-7.6 Practice Test 8

Question 70

FortiGate IPS logs show repeated exploit signature matches, but the connection remains permitted. What is the most direct configuration check?

  1. Increase logging detail on the IPS sensor and track new signature events before changing the action assigned to that signature.
  2. Raise the IPS signature severity filter to Critical while retaining the matching signature’s current Pass action.
  3. Whether the matching IPS signature action is monitor/pass rather than block, and whether the correct sensor is applied.
  4. Raise the matching firewall policy priority without changing the effective IPS sensor or its signature action.

Explanation

Correct Answer

C:

An IPS signature may be configured to monitor, pass or block depending on profile and override settings. Inspect the actual sensor attached to the traffic policy, signature filter and event action. Test a safe reproduction, then confirm that the expected block occurs without creating false positives for legitimate service.

Incorrect Answers

A:

More detailed logs may support investigation, but they do not change a signature configured to Monitor or Pass. The scenario already has matches and permitted sessions; verify the effective sensor and its actual signature enforcement action.

B:

Severity filtering selects which IPS signatures are eligible but does not convert an explicitly configured Pass/Monitor action to Block. The observed match must be mapped to its signature action on the actual traffic policy.

D:

Policy order determines which firewall policy matches, but the incident already shows an IPS signature match on passing traffic. Moving the rule without correcting the attached sensor action can preserve the same observe-only behavior. Compare sensor override precedence and logs.

Question 71

A FortiGate VM is deployed between AWS subnets, but traffic between the two protected application subnets goes directly via cloud routing and never appears in firewall logs. What should be fixed?

  1. Attach an IPS profile to the FortiGate-VM before modifying source and destination subnet route tables that currently bypass the instance.
  2. Enable EC2 network-interface source/destination forwarding checks on the VM.
  3. Add an AWS security-group rule to allow HTTPS toward the FortiGate NIC.
  4. Steer both directions of intended traffic through the FortiGate inspection interfaces with appropriate VPC route tables and security controls.

Explanation

Correct Answer

D:

Cloud deployment requires deliberate route-table steering into FortiGate VM interfaces or the supported service insertion design, including a consistent return path. Check cloud security groups, NACLs and forwarding permissions alongside FortiGate policies. Verify actual packet traversal for both directions and failover conditions; a running VM alone provides no protection.

Incorrect Answers

A:

An IPS sensor can inspect only packets traversing the matching FortiGate-VM policy. AWS route tables must steer intended application traffic through the appliance for any security profile to act.

B:

Forwarding VMs generally need the EC2 source/destination check disabled, not enabled; even then, that alone does not redirect bypassing VPC traffic. Verify the next-hop routes and return path.

C:

A security group allow can permit traffic when it reaches an instance, but does not itself insert that NIC as the next hop for application subnets. Inspect effective routes in both directions.

Question 72

A FortiGate LAN-to-DMZ policy permits SSH to a sensitive administration host 10.60.9.10, but its destination address is set to all. The policy could therefore permit SSH to other hosts in the same zone when those hosts are added. What is the key policy correction?

  1. Replace the all-address destination with a specific address object for 10.60.9.10, preserve only the approved sources and SSH service, and verify rule matching.
  2. Restrict the SSH source object to the single authorized jump host while leaving the DMZ destination as all.
  3. Inspect the SSH service object and replace its existing TCP/22 definition with a dedicated management-only custom TCP/22 service.
  4. Review firewall rule ordering and place the destination-all SSH permit beneath the DMZ application-specific policies.

Explanation

Correct Answer

A:

Destination address objects are part of a FortiGate policy’s match criteria. Constrain the sensitive host permit to the required /32 destination and approved source network and service, then test new sessions for the named server and an unrelated DMZ host. A narrow destination prevents accidental authorization as the zone grows.

Incorrect Answers

B:

Restricting the source reduces who can initiate SSH, but the authorized jump host would still match every reachable DMZ server under the destination-all policy. The risk described is accidental permission to other hosts. Narrow the destination specifically to 10.60.9.10 as well.

C:

A dedicated SSH service object is valid least-privilege practice, yet the stated exposure is the destination-address match of ALL DMZ hosts. Either SSH object can still reach any permitted DMZ destination. Restrict the firewall destination to 10.60.9.10/32 and preserve the authorized source scope.

D:

Order changes can reduce shadowing but do not remove the insecure match when earlier policies fail to apply. A lower all-destination SSH rule can still authorize new management connections to unrelated hosts. Change the actual destination object to the approved host address and verify policy lookup.

Question 73

An SD-WAN rule intended for voice traffic uses application and destination selectors, but voice sessions follow a general internet rule instead. Which troubleshooting method is most direct?

  1. Lower the jitter and latency thresholds of the voice performance SLA to make the low-quality WAN member ineligible.
  2. Refresh FortiGuard application-control signatures so the voice application can be recognized more consistently.
  3. Inspect SD-WAN service rule order, actual session selectors, application classification and selected member for a fresh call.
  4. Pin the voice destination to wan1 with a more specific static route while leaving the existing SD-WAN service order unchanged.

Explanation

Correct Answer

C:

Check which ordered SD-WAN rule first matches the real source, destination, service or identified application. Compare classification and the route/zone used by the firewall policy; inspect service diagnostics for the chosen member. Test a new voice session and verify the intended SLA rule rather than assuming the application name is detected as expected.

Incorrect Answers

A:

SLA tuning determines which member qualifies after the correct SD-WAN service rule matches. Here the sessions first match a general internet rule, so changing thresholds on the unused voice rule does not fix selection. Establish actual service order, source/destination and application identity before adjusting quality thresholds.

B:

Signature classification can influence application-based steering and is a plausible candidate if the rule depends on an app ID. It does not diagnose an earlier matching general SD-WAN rule or the actual session selectors on its own. Inspect the selected service and app classification before deciding on updates.

D:

A destination route can influence forwarding eligibility, but it does not explain why the wrong ordered SD-WAN service matched the application. It may also break quality-based failover when wan1 degrades. Resolve the policy/service selection and health rule using fresh call traffic evidence.

Question 74

Managed Windows laptops accept FortiGate-issued inspection certificates and can use internal HTTPS apps. Unmanaged BYOD devices reject the same full-inspection policy. Which design response is defensible?

  1. Push the inspection CA public certificate to an unmanaged BYOD browser despite the organization not controlling its trust store or its certificate-pinning requirements.
  2. Apply a differentiated HTTPS inspection approach based on managed trust and policy, with controlled exceptions and measured security coverage.
  3. Export the private key of the inspection CA to every BYOD user.
  4. Exempt all BYOD and managed traffic from SSL inspection after seeing errors on one unmanaged device.

Explanation

Correct Answer

B:

Managed devices can receive the approved inspection CA and support full inspection where authorized. Unmanaged devices may need separate access controls or limited certificate inspection according to privacy and compatibility requirements. Segment policies by device trust and test the remaining security controls rather than broadly turning off TLS validation.

Incorrect Answers

A:

Importing an authorized CA can help a managed endpoint, but unmanaged BYOD may not permit reliable enterprise trust deployment and may have privacy or pinning constraints. Segment inspection policy by device trust and validate supported content visibility and exceptions.

C:

The signing CA private key must remain protected because it can issue substitute certificates. Distributing it to BYOD endpoints would compromise trust for every managed client. Devices require only appropriately protected public trust roots when that approach is authorized.

D:

An enterprise-wide bypass unnecessarily removes payload inspection for the managed devices that already trust the inspection CA. Define a policy scoped to BYOD and applicable business needs, preserve stronger inspection on managed endpoints, and document residual coverage.

Question 75

A remote office adds 10.77.8.0/24 behind its FortiGate. Its existing IPsec phase one is healthy, but traffic from headquarters cannot reach the new subnet. What should change?

  1. Inspect the headquarters routing table and add 10.77.8.0/24 toward the existing route-based VPN without changing its narrow phase-two selectors.
  2. Check the headquarters VPN security-policy destinations and add 10.77.8.0/24 to its existing branch allow without changing phase-two scope.
  3. Extend the headquarters destination address group to include 10.77.8.0/24 on the existing tunnel policy.
  4. Update or confirm phase-two protected selectors, the route to the new prefix and the relevant inbound/outbound firewall policies on both ends.

Explanation

Correct Answer

D:

Both FortiGates must recognize and permit the new protected network in the intended tunnel design. Check phase-two local/remote selectors, destination routing, policy source/destination objects and return path. Verify new sessions and IPsec counters while preserving access to the previously working prefixes. Confirm that a headquarters-to-branch test packet increments the expected tunnel counters.

Incorrect Answers

A:

A correct route is one prerequisite for the new subnet, but a narrow negotiated child SA may still exclude that prefix. The site-to-site design must reconcile both protected traffic selectors, relevant directional firewall policies and routes on each peer. A route-only change cannot guarantee the new subnet is encrypted.

B:

A directional allow policy can authorize a new network only if the route and negotiated IPsec selectors actually carry it. The case says the new subnet was just added, so an existing narrow child-SA selector may be insufficient. Verify both ends of the protected prefix and routes with the policy.

C:

A matching destination object is necessary in many designs and is a plausible first configuration step. It cannot on its own extend narrow phase-two selectors or create a route to the new remote network; compare the protected subnet definitions and both peers’ routing and policy paths.

Question 76

A FortiSASE user is authenticated and FortiClient reports Connected. A policy assignment audit shows that this endpoint did not receive the private-application traffic-steering profile assigned to working users; its private-app access packets never enter the protected path. The app name resolves correctly in a separate controlled test. What should be corrected?

  1. Assume the FortiClient Connected indicator proves all private-application steering rules were delivered and change only the application server certificate.
  2. Compare the user/device’s actual FortiSASE onboarding and assigned private-access traffic-steering profile with a working identity; restore the missing authorized profile and verify private-app policy, connector and packet forwarding.
  3. Change the private application’s correctly resolving DNS record to the remote client’s public IP.
  4. Inspect the FortiSASE public-web security profile assigned to the user and expand the allowed application categories to include the private application portal.

Explanation

Correct Answer

B:

Compare tenant/user-group assignment, endpoint enrollment and the actual steering profile for the protected private application against a working client. After correcting the specific missing assignment, verify the right entitlement, private connector route and packets/records through the service.

Incorrect Answers

A:

Connection to the tenant is not proof that a private-application steering profile has been assigned or is carrying the relevant flows. The case supplies a missing assignment and correct DNS evidence, so repair policy delivery rather than a separate origin certificate.

C:

The supplied application hostname already resolves correctly during the controlled test. Redirecting the server DNS entry to an unrelated client is not supported private-app routing and does not put eligible traffic into the protected steering path.

D:

Web-category authorization may affect a browser session destined for a public SaaS application, but the named private application packets never enter the required protected traffic-steering path. The user is authenticated yet was not assigned the working private-access profile. A public-web category adjustment neither supplies private steering nor repairs connector routing; restore the correct assignment and test packet path.

Question 77

A network engineer creates a VIP mapping 198.51.100.80:443 to a private DMZ web server, but external clients receive no response. The server listens on 443 and WAN reachability is proven. What FortiGate requirement should be checked?

  1. Whether an incoming policy accepts the appropriate WAN-to-DMZ traffic with the VIP as destination and the correct service.
  2. Create another WAN-to-LAN policy with destination set to the public WAN interface IP rather than the configured VIP object.
  3. Enable a source-NAT pool on an existing LAN-to-WAN policy.
  4. Increase the VIP external port range to all TCP services.

Explanation

Correct Answer

A:

A VIP provides destination translation, but eligible inbound traffic also needs a matching security policy. Confirm the correct incoming interface, VIP destination, service, source restrictions, and egress interface. Inspect a new external session and counters, then verify the return route and any upstream filtering if the policy is correct.

Incorrect Answers

B:

For an incoming published service, the policy destination should reference the correct VIP and match the incoming interface/service. An unrelated public-interface destination object may not authorize the translated server flow.

C:

Source NAT for ordinary outbound client sessions does not provide the inbound destination mapping and permission needed to reach a private DMZ server. Check the VIP and its WAN-to-DMZ rule.

D:

Broadening published ports unnecessarily increases exposure and does not repair a missing or nonmatching inbound firewall policy. Keep the intended TCP/443 tuple and inspect policy ID, VIP match and return route.

Question 78

In FortiOS 7.6.0, a policy must block the base host unwanted.example.org and its intended subdomains without denying approved.example.org. One teammate suggests using only the page-specific URL unwanted.example.org/login. Which static URL-filter design achieves the specified host scope without relying on later-version options?

  1. Add a Simple Block entry for the observed login path unwanted.example.org/login to cover the known entry point.
  2. Add a regular-expression block matching every hostname ending in example.org and permit the approved host by a later explicit Allow entry.
  3. Configure a hostname-scoped Simple or carefully bounded wildcard Block entry for unwanted.example.org, verify intended subdomain matching in 7.6.0 and test approved.example.org separately.
  4. Inspect the existing FortiGuard rating for unwanted.example.org and block the associated web category in the effective profile to include its subdomains.

Explanation

Correct Answer

C:

Use the supported URL filter Simple/domain or bounded wildcard matching rules available in 7.6.0. A Simple entry for a base domain can match subdomains under the documented behavior; confirm which hosts and HTTPS paths the effective inspection reveals. Test unwanted.example.org, an intended subdomain and approved.example.org in the actual policy before deployment.

Incorrect Answers

A:

A single URL-path entry can be useful when the requirement is limited to that exact resource, but the scenario requires the base host and all intended subdomains. The chosen path does not prove coverage of unrelated pages and nested hostnames. Use a supported host-scoped expression and test the stated subdomain cases.

B:

A parent-domain expression would also match approved.example.org. Depending on matching order and FortiGuard/category controls, a later URL Allow may not reliably undo an earlier broad block, while an exemption may bypass more security checks. A bounded unwanted.example.org hostname expression avoids the unnecessary overlap.

D:

Category blocking is a real FortiOS web-filter control, but categories describe site classifications rather than the requested exact hostname and subdomain boundary. Other approved destinations can share a category, and separate subdomain ratings may differ. A hostname-scoped static URL expression must be tested against wanted and approved sibling hosts under the pinned 7.6.0 matching semantics.

Question 79

FortiGate has a blackhole route to 10.200.0.0/16 to prevent private-destination leakage to the default internet gateway. A host sends to 10.200.4.5, and there is no more-specific usable route. What should happen?

  1. The packet automatically chooses the default route because the blackhole has no gateway.
  2. The packet is dropped by the more-specific blackhole route rather than leaking onto the internet default.
  3. Keep the blackhole installed but force the 0.0.0.0/0 internet default to take precedence solely by lowering its administrative distance below the blackhole route.
  4. Add a 10.200.0.0/16 static route toward an IPsec interface that is administratively down.

Explanation

Correct Answer

B:

Longest-prefix matching selects the active 10.200.0.0/16 discard path over the less-specific default, so the destination is intentionally not forwarded. Validate the route table and any authorized more-specific VPN route before changing the blackhole; deletion could cause private traffic leakage. Do not assume the default internet route is an acceptable fallback for reserved private networks.

Incorrect Answers

A:

A blackhole route is still an installed destination route and can be more specific than 0.0.0.0/0. The absence of a forwarding gateway is intentional: it prevents the fallback route from receiving this protected destination.

C:

Administrative distance only compares competing eligible routes for the same prefix. The active /16 blackhole is a longer destination-prefix match than /0, so changing the default distance alone cannot make the default outrank it for 10.200.4.5. Add an authorized more-specific route if needed.

D:

An inactive or unresolved same-prefix route to a down tunnel is not an eligible forwarding path, and the question states there is no more-specific usable route. The installed blackhole /16 remains more specific than the internet default /0, so the addressed packet is intentionally discarded. Verify actual active routes, not merely configured objects.

Question 80

A site-to-site tunnel shows phase one up, but phase two rejects the partner proposal after a security change. The logs identify a perfect-forward-secrecy DH-group mismatch. What should be aligned?

  1. Rebuild the already established phase-one IKE proposal.
  2. Enable IPsec NAT traversal on both endpoints and assume UDP encapsulation automatically resolves mismatched phase-two Diffie–Hellman groups.
  3. Install a static route for the partner subnet before aligning the incompatible phase-two ESP/PFS proposals on the peers.
  4. Compatible phase-two PFS/DH group and ESP settings on the peers, preserving the agreed security requirements.

Explanation

Correct Answer

D:

Phase-two PFS requires both sides to negotiate compatible groups and ESP settings for the child SA. Compare proposals, security policy requirements and debug messages before choosing a mutually approved configuration. After phase two establishes, confirm protected-subnet selectors, routes and firewall policies separately. A compatible configuration should still meet the organization's approved cryptographic strength requirements.

Incorrect Answers

A:

Phase-one negotiation can be established while phase-two fails on its separate cryptographic settings. The log identifies a child-SA PFS mismatch, so compare the configured phase-two Diffie–Hellman groups and ESP settings instead of restarting unrelated phase-one negotiation.

B:

NAT traversal deals with carriage of IPsec through NAT devices, not the mutual agreement of cryptographic parameters for a child security association. A PFS mismatch persists after enabling UDP encapsulation unless the peer proposals are also aligned.

C:

The correct route is needed to carry protected traffic after a tunnel is usable, but it cannot cause incompatible child-SA proposals to negotiate. Align matching phase-two PFS and ESP settings first, then validate routing, selectors and firewall policies.

Fortinet NSE 4 - FortiOS 7.6 Administrator (NSE4_FGT_AD-7.6) Practice Tests