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 17

Question 160

A FortiGate has an IPS sensor on the WAN-to-DMZ policy protecting public servers, but outbound client connections use a different LAN-to-WAN rule without IPS. A known exploit test leaves from a client and creates no IPS alert. What correction addresses coverage without disabling the server protection?

  1. Increase the inbound WAN-to-DMZ IPS sensor severity coverage to also detect the exploit observed from the LAN client.
  2. Apply an IPS blocking sensor on the actual outbound LAN-to-WAN policy while retaining inbound server protection, for the observed client-originated exploit signature.
  3. Enable an IPS profile in Monitor mode on the outbound policy as the complete corrective action for a required exploit block.
  4. Enable the IPS signature filter globally at critical severity while keeping its profile attached only to the inbound server policy.

Explanation

Correct Answer

B:

The existing IPS profile protects requests handled by the WAN-to-DMZ policy but cannot inspect separate LAN-to-WAN client sessions that never match that rule. Identify the outbound policy ID, attach an appropriate sensor, inspect TLS visibility where needed and test a benign signature demonstration. Keep the server protection active and avoid an unrestricted global IPS disable.

Incorrect Answers

A:

An enhanced sensor on the inbound server policy may strengthen that server path, but it still does not inspect outgoing LAN-to-WAN sessions matched by a different rule. The client-path policy needs its own appropriate IPS sensor and action.

C:

Monitor can establish visibility into signatures and can be appropriate for a pilot, but it does not satisfy the scenario’s requirement to stop a known exploit. The effective LAN-to-WAN sensor needs the relevant signature enabled with its intended blocking action.

D:

Global signature criteria do not cause a sensor on one firewall policy to inspect traffic matched by another. The outbound client traffic must be associated with a sensor on its actual egress permit; only then does signature severity or action matter.

Question 161

The security team sees deny records for a guest subnet but cannot find logs of permitted outbound sessions. Traffic is forwarding normally. Which FortiGate change is most relevant to its audit requirement?

  1. Enable IPS security-event logging on the guest access policy and use detected signature events as the record of every permitted session.
  2. Enable logging at the end of denied sessions and treat those deny records as a complete report of previously permitted outbound traffic.
  3. Enable the required accepted-session logging on the effective permitted outbound policies, confirm the deny-log setting and verify delivery to the configured collector.
  4. Collect administrator configuration-change events from the same FortiGate and correlate those events with client policy IDs.

Explanation

Correct Answer

C:

A FortiGate can permit data sessions without producing the accepted-traffic events that an auditor expects. Inspect the matched policy IDs, session logging at start/end as appropriate, event classes and FortiAnalyzer or syslog delivery. Generate a known permitted test and compare its timestamp with the logged denial evidence; do not confuse a permit rule hit counter with a durable audit record.

Incorrect Answers

A:

IPS security events occur only for matching detections and do not represent a complete forwarding-session ledger. For the audit’s allowed traffic records, enable the appropriate traffic-logging setting on the effective accepted policies and validate delivery.

B:

Denied traffic records are already present; they cannot document flows that were accepted. FortiGate log generation is action- and policy-dependent, so the matching permit must produce the accepted-session records required by the audit.

D:

Configuration audit events can show when rules changed but do not report each permitted client connection. The use case requires traffic logs with session, policy, source/destination and action information on the matching outbound permit.

Question 162

A FortiGate rejects a TLS connection to an internal service although the leaf certificate is valid. The server fails to present an intermediate certificate. What is the appropriate fix?

  1. Import the missing intermediate CA to FortiGate’s trusted certificate store while leaving the application server’s incomplete served chain unchanged.
  2. Repair the upstream server’s intermediate CA chain and validate trusted TLS certificate path and hostname, without bypassing the upstream server certificate validation.
  3. Inspect the matched static URL-filter entry for the internal hostname and add a local Allow action to the current web-filter profile.
  4. Use certificate-only inspection on the affected policy and accept the TLS server as trustworthy because the leaf certificate is within its validity dates.

Explanation

Correct Answer

B:

A valid leaf certificate may still fail chain building when the server omits an issuing intermediate CA that the validator cannot obtain. Inspect the TLS handshake and issuer path, fix the server chain or an explicitly trusted intermediate under approved policy, and retest the actual hostname. Avoid globally disabling certificate verification, which could admit impersonated servers.

Incorrect Answers

A:

Installing the legitimate intermediate in a validator can sometimes allow a chain to be completed, making this a nearby remediation. However, the case states the upstream server fails to present its required intermediate; the durable fix is to repair the served chain and confirm trusted issuance and hostname on the exact session, not rely on one appliance-specific workaround.

C:

A static URL action can influence web-policy access, but the recorded failure occurs during upstream TLS certificate validation because an issuer is omitted. A URL Allow does not insert the missing intermediate into the server chain or establish a trusted certificate path. Correct the server certificate presentation first.

D:

Certificate validity dates alone do not prove a trusted path to an issuer. A mode change also sacrifices any required decrypted content inspection while leaving the underlying missing intermediate unresolved. Repair and validate the full chain.

Question 163

A FortiGate already forwards traffic and security events to an authorized FortiAnalyzer, and device registration is healthy. Nevertheless, a seven-day storage policy expires incident evidence before the required 90-day investigative window. What should the operator change?

  1. Inspect FortiGate local-disk retention and increase on-box space to preserve ninety days while leaving FortiAnalyzer’s seven-day expiry unchanged.
  2. Set supported FortiAnalyzer retention for 90 days and validate ingestion, searchability, storage capacity and authorized log categories.
  3. Review alert summaries in FortiAnalyzer and keep those summaries ninety days while dropping older raw accepted-session records after seven days.
  4. Increase FortiGate session TTL so connections can remain visible in the session table for much of the 90-day audit period.

Explanation

Correct Answer

B:

Central forwarding is already functional, so changing to another collector alone will not satisfy the evidence-retention requirement. Verify FortiAnalyzer storage and archiving policy against 90 days of projected traffic/security event volume, configure the supported retention and export safeguards, and test a query for older approved evidence. Check that the required traffic and security categories are generated by FortiGate; never claim historical records exist if they have already expired.

Incorrect Answers

A:

An additional local copy can assist troubleshooting, but the requirement is an authorized centralized searchable ninety-day investigative window and FortiAnalyzer is actively expiring events after seven days. Update the supported analyzer retention and validate allocated storage, indexing and received log categories.

C:

An incident summary is useful, but it cannot reliably reconstruct the original per-flow sequence, identifiers and policy actions if raw event records expire. The case explicitly requires incident evidence to remain searchable for ninety days. Retain the necessary complete log classes at the collector, not only derived alert summaries.

D:

A live session table reflects current forwarding state and is not a durable, searchable historical security-event archive. Altering connection lifetime also changes security behavior and cannot satisfy incident evidence retention.

Question 164

Two internal groups need different public source addresses through the same WAN. The existing central SNAT rule catches both groups first. What should be changed?

  1. Insert two source-specific Central SNAT entries below the existing broad match and assign the required different IP pools.
  2. Review the two new IPv4 firewall permits and configure their policy NAT pools for the intended departments without changing central-snat-map entries.
  3. Order source-specific Central SNAT mappings to the two public pools and confirm actual rule hits and translated addresses.
  4. Create two external port-forward VIP objects, one for each internal user group, and retain the existing Central SNAT mapping.

Explanation

Correct Answer

C:

When both groups match a broad earlier central SNAT entry, its translation can override the desired group-specific public source. Inspect source/ingress and destination/egress criteria, policy order and IP-pool mapping. Place the appropriate narrow entries where effective and use test sessions from each group to confirm the expected public address and return reachability.

Incorrect Answers

A:

FortiOS central SNAT rules are evaluated in order. The existing broad rule still matches both internal groups first, so more-specific rules placed beneath it are shadowed. Move each source-specific mapping above the catchall and confirm actual translated addresses from fresh sessions.

B:

Per-policy NAT settings can drive egress translation when the firewall is operating in policy NAT mode. The stem explicitly specifies an existing broad Central SNAT rule, which takes precedence according to the ordered central SNAT table. As long as that rule is enabled and matches both groups, independent policy NAT selections do not ensure separate translated addresses. Fix the central source mappings and rule order.

D:

VIPs implement destination translation for published services and do not replace source-based egress mappings for separately translated internal groups. Both groups would continue to match the broad Central SNAT entry. Use matching source-address/group rules in order with the two proper IP pools.

Question 165

Two critical SD-WAN services use health checks pointing to the same monitoring host. When that host becomes unavailable, both links appear down even though other approved application endpoints remain reachable. Which monitoring design avoids mistaking a shared probe failure for dual ISP failure?

  1. Increase both SD-WAN probe intervals to reduce sensitivity to brief loss of the single shared probe destination.
  2. Use the carrier Up status of both WAN interfaces as the primary SD-WAN member health test for critical application paths.
  3. Use representative independent SLA probe targets so one unreachable shared host cannot make both healthy WAN paths fail.
  4. Increase loss and latency limits for both services while retaining the single shared SLA probe host.

Explanation

Correct Answer

C:

Both WAN members can be physically healthy while a single shared detection server becomes unreachable. An identical probe target creates common-mode health-check failure, so inspect member-specific probe packets and configured thresholds before declaring both links down. Test alternate representative endpoints or supported multi-server detection and verify failure transitions under controlled target loss.

Incorrect Answers

A:

A longer interval can reduce transient alerts but retains a common monitoring-host failure that will make both WANs appear unhealthy when the target is persistently unavailable. Use representative and redundant probe targets to distinguish target outage from WAN loss.

B:

Carrier Up only proves the immediate physical link and can remain true during upstream outages or unacceptable quality. A meaningful SLA must measure representative reachability and performance instead of substituting physical Ethernet state.

D:

Threshold tuning cannot repair a health-check endpoint that is completely unreachable through both paths. Raising limits would reduce protection against real application degradation while preserving the correlated probe-host single point of failure.

Question 166

An intermittently used branch tunnel repeatedly drops its IKE state between valid business sessions. Logs show dead-peer detection retries during idle periods. What should be tuned?

  1. Switch off all peer authentication checks during idle periods so the FortiGate does not tear down the inactive IPsec SA.
  2. Set the shortest supported DPD retry interval and minimum retry count to declare idle peers unavailable more quickly.
  3. Inspect the branch phase-two automatic negotiation setting and enable periodic child-SA initiation while retaining the current phase-one DPD behavior.
  4. Correlate DPD retries with actual tunnel loss, then adjust the supported DPD mode and timing only where evidence warrants.

Explanation

Correct Answer

D:

Dead-peer detection sends supported IKE liveness checks and can remove a tunnel when responses fail. Compare the actual DPD mode, retry interval/count and observed WAN packet loss against the application idle pattern before adjusting timers. Correct the verified path or DPD sensitivity while retaining authenticated peer checks, and retest an idle-to-active transition and a true peer outage. Merely extending timer values is not evidence that unreachable peers will recover safely.

Incorrect Answers

A:

IKE peer authentication and dead-peer liveness are distinct; removing authentication undermines tunnel security and does not legitimately tune how idle transport loss is detected. Diagnose actual DPD retries and supported timing/mode options.

B:

More aggressive DPD can make a lossy or intermittently used path fail even more often, contrary to the symptom. First compare DPD request/response logs, actual packet loss and intended tunnel idle behavior before choosing retry values.

C:

Proactive phase-two negotiation can prevent a child SA from waiting for the first protected packet, and is therefore a relevant VPN availability control. The recorded symptom is repeated idle phase-one DPD retries and peer deletion, not simply delayed child-SA initiation. Investigate DPD mode, retry intervals, peer liveness and upstream NAT idle handling before attributing the outage to phase-two auto-negotiate.

Question 167

A user reports that one web destination is denied despite the URL category being set to allow. The policy also has static URL filtering and another security profile. Which evidence is decisive?

  1. Check whether a local FortiGuard rating override already assigns the hostname to an allowed category, and refresh its rating cache.
  2. Trace the effective policy and web-filter event to the static URL rule, FortiGuard category or other profile.
  3. Downgrade to certificate inspection and leave the static URL Block and remaining security profiles unchanged.
  4. Move the selected HTTPS ACCEPT firewall policy above adjacent rules and replay the same hostname through its existing security profiles.

Explanation

Correct Answer

B:

An allowed FortiGuard category does not guarantee that every static URL entry or additional security profile will permit the request. Examine the actual logged URL/host, which rule ID and web-filter profile handled it, and the action reported. Correct only a demonstrated conflicting rule, then verify the approved site and the originally prohibited destinations still behave correctly.

Incorrect Answers

A:

A category override can be relevant when a rating lookup is wrong, but this session may also match a static URL Block or another attached security profile. An allowed category is not the full traffic disposition. Correlate the actual matched URL-filter entry and separate profile event before changing rating configuration.

C:

Less decryption can change visibility but does not automatically make an explicitly blocked hostname allowed, and it can remove necessary content coverage. The observed denial must be attributed to the matched URL rule, category or other profile first.

D:

Reordering forwarding permits affects which rule is selected only if policy lookup was the problem. The request is already associated with a policy whose category permits the site; a static URL Block or other security-profile verdict can still deny it after ACCEPT. The decisive evidence is the logged profile action.

Question 168

One FGCP HA member has a failing monitored WAN interface, while heartbeats remain stable. The cluster switches primary unexpectedly. What must be compared?

  1. Raise the device priority on the member with the failing monitored WAN port and enable HA override for preference.
  2. Check monitored WAN interfaces and FGCP election history before changing HA priority; a monitored port failure can trigger failover.
  3. Enable session pickup on both FGCP units and compare synchronized sessions during the next WAN-port failure.
  4. Disable WAN-interface monitoring on the preferred member to stop elections caused by the current link fault.

Explanation

Correct Answer

B:

Monitored-interface status can make a member ineligible despite healthy heartbeat; verify matching physical links and their role in HA failover eligibility. Compare each member's port-monitor configuration and the failed WAN port with HA event timestamps. The cluster may legitimately move primary while the heartbeat remains intact, because the monitored production path is the health criterion rather than mere node connectivity.

Incorrect Answers

A:

Priority and override can influence election after health criteria are considered, but a failed monitored interface remains a valid failover trigger. Making a degraded member more preferred may harm production connectivity. Compare monitored-link status and FGCP election history before adjusting preference.

C:

Session pickup supports continuity of eligible flows after failover, but does not explain or override the primary election triggered by a monitored-port state change. The heartbeat path is healthy; investigate the monitored interface and election criteria rather than state-synchronization options alone.

D:

Removing the faulty WAN from HA monitoring might suppress this trigger but leaves the cluster on a member whose production egress is broken. The requirement is to understand the unexpected election and preserve availability. Diagnose the monitored link and repair its physical or upstream fault instead.

Question 169

LDAP authentication fails after the directory team moved users into a new organizational unit. The FortiGate still uses an old search base and a bind account. What should be checked?

  1. Update LDAP search base and group scope for the moved OU, then test directory membership and matched authorization.
  2. Inspect local FortiGate user-group membership and add moved directory users to that local group while leaving the obsolete LDAP search base configured.
  3. Review firewall service permits for LDAP TCP 389/636 and expand the permitted transport ports while keeping the original directory search DN.
  4. Replace the LDAP server’s trusted CA certificate on FortiGate while keeping the old base DN and group search settings.

Explanation

Correct Answer

A:

FortiGate LDAP integration may use a configured distinguished-name search base and user/group filters that no longer include accounts after an OU migration. Inspect server address and bind, the new base DN, group membership attributes and any nested group behavior supported by the implementation. Test a moved account and an out-of-scope nonmember before changing authorization rules.

Incorrect Answers

B:

A local FortiGate group may authorize a different authentication workflow, but the failure is specifically an LDAP search rooted at the former organizational unit. Local membership does not make the remote directory search find moved accounts. Correct the base DN and group scope, then verify bind and lookup.

C:

LDAP transport can be blocked in some deployments, but the scenario identifies the user OU migration and an unchanged obsolete search base. Opening an unrelated port cannot make an already connected LDAP bind search the correct organizational location. Validate the new base DN and group filter.

D:

A trust-chain update matters for LDAPS certificate failures, but the case identifies a moved user OU and obsolete search base. Without evidence of a TLS error, rotating certificates does not expand which user entries the LDAP query searches.

Question 170

A category rule blocks a company's approved social-media support portal. Security wants ordinary personal social sites restricted. What application-control change is defensible?

  1. Change the social-networking category action to Allow for the shared policy and compensate by logging ordinary personal browsing.
  2. Create a static web-filter URL Allow entry for the portal while retaining the application-control signature that produces its Block verdict.
  3. Create an FQDN destination address for the support portal and place it on the current category-blocking rule.
  4. Override only the blocked support-portal application signature on the correct profile, keeping other social apps prohibited.

Explanation

Correct Answer

D:

A broad social-media category can include both an approved support platform and unsanctioned personal apps. Use app-control logs to identify the matching signature and profile action, validate the authorized application, then apply an explicit narrow exception within the supported matching order. Test both the approved application and known blocked traffic after the change.

Incorrect Answers

A:

Category-wide Allow permits the other social apps that must remain restricted, and monitoring logs do not replace a block. A verified signature-level exception or narrowly scoped rule is needed for the approved portal.

B:

A URL Allow can influence web filtering but need not override an independent application-control Block signature. The operator must find the actual application-control match and apply a scoped override while preserving broader category restrictions.

C:

FQDN matching can restrict which destination is in a rule, but merely adding the portal to a rule whose application-control category remains Block will not exempt the intended app. The blocking signature/action must be scoped appropriately.

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