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 28

Question 270

A partner's HTTPS server presents a self-signed certificate that is not in the trusted issuing-store. The FortiGate inspection path rejects it. How should the exception be evaluated?

  1. Check the selected SSL inspection profile and permit invalid certificates for the partner’s entire group of HTTPS domains.
  2. Replace the server's public DNS entry with a private IP.
  3. Validate the self-signed partner identity and explicitly approve trust for that certificate, or keep the TLS connection denied.
  4. Import the partner server certificate into the FortiGate trusted certificate store and apply the same trust rule to every HTTPS origin.

Explanation

Correct Answer

C:

Self-signed server certificates lack a public CA chain by default; that does not automatically mean a legitimate internal service is unsafe, nor is it sufficient evidence to trust it blindly. Verify the expected hostname and out-of-band certificate fingerprint, apply a supported explicitly trusted CA/certificate only under approved policy, and retest the connection while retaining normal verification for unrelated destinations.

Incorrect Answers

A:

Invalid-certificate exceptions can restore connectivity, but this broad domain group extends trust beyond the one specifically self-signed server. The actual identity and certificate ownership need independent approval, or the connection should remain denied. A blanket upstream-validation bypass exposes unrelated sites to substitution.

B:

Routing and DNS changes do not validate the certificate's issuer, hostname or expiry. Certificate trust must be addressed independently of the path used to reach the server. A DNS address rewrite does not establish the remote server certificate identity or trusted issuer required by TLS validation.

D:

A deliberately pinned and verified self-signed certificate can be trusted for a bounded partner service, but generalizing that trust to all HTTPS destinations is excessive. Validate its subject, SAN, owner and intended endpoint, then scope the exception rather than accepting unrelated certificates.

Question 271

FGCP reports that the secondary configuration is not synchronized with the primary. An engineer wants to delete all secondary policies manually. What should be checked?

  1. Compare member FGCP checksums and synchronized versus member-local settings; restore controlled primary-to-secondary consistency.
  2. Inspect the HA synchronization checksum and immediately restore the primary configuration onto both members before identifying local-only differences.
  3. Review firewall policy sync differences and exclude all firewall policies from subordinate synchronization to clear the checksum alert.
  4. Reinitialize the secondary from factory defaults immediately and rejoin it with the current primary configuration.

Explanation

Correct Answer

A:

Cluster checksum mismatch indicates non-synchronized or local-specific objects; compare FGCP sync status and permissible per-member configuration before forcing replication. Compare the HA configuration checksums, sync status and failed object context for each member, including member-specific exceptions. Repair the supported synchronization problem at the proper authority rather than manually deleting all subordinate security policies.

Incorrect Answers

B:

Checksums can identify drift, but FGCP intentionally excludes some per-member settings such as reserved management interfaces, priority and licenses. A forced full restore can overwrite those local controls and disrupt redundancy. Identify the actual mismatched synchronized object and use a controlled repair with rollback.

C:

Firewall security policies are ordinarily shared and synchronized to preserve consistent behavior after failover. Suppressing sync can produce different enforcement when the standby becomes primary. Determine the object that diverges, correct allowed configuration and verify synchronization status rather than excluding whole policy categories.

D:

Rejoining a subordinate can be necessary for persistent corruption, but the case only establishes a checksum mismatch. Factory reset before identifying the specific unsynchronized table may destroy useful diagnostic evidence and interrupt redundancy. Compare FGCP status, checksums and known local-only settings first.

Question 272

An employee must complete a thirty-minute regulated order-entry session, but the FortiGate user authentication expires after ten idle minutes and repeatedly interrupts the transaction. Security still requires a bounded idle timeout. What change should be evaluated with a fresh session test?

  1. Inspect the FortiGate administrator GUI idle setting and extend it to 45 minutes for the user’s regulated browser workflow.
  2. Set a supported firewall-user idle timeout sufficient for the 30-minute authorized workflow and validate idle expiry.
  3. Review the existing ten-minute firewall-user timeout and keep it unchanged while sending periodic background HTTPS requests.
  4. Grant permanent access to the source IP after its first successful login, bypassing later user checks.

Explanation

Correct Answer

B:

The ten-minute idle timeout conflicts with a thirty-minute regulated order entry; determine whether the FortiGate authentication timeout, application keepalive or reauth method actually interrupts the session. Set a bounded approved interval and test idle and active behavior without disabling access expiry.

Incorrect Answers

A:

Management GUI idle timers control FortiGate administrators rather than a firewall-user authentication session. The session requiring a 30-minute work period is an end-user identity policy. Adjust the supported user idle timer with a bounded expiry and validate an authorized fresh transaction instead of changing admin settings.

C:

Background application traffic might not count as activity under the relevant user-authentication idle semantics and should not be treated as a guaranteed substitute for a supported session timer. The requirement is a bounded 30-minute workflow. Configure a suitable authorized idle duration and verify expiration in a controlled test.

D:

An address is not enduring proof of the person using a device. Shared or reassigned clients could inherit an earlier user session and bypass the intended expiration policy.

Question 273

Two internal business applications both use TCP 443, but only one needs an SLA with very low latency. Which SD-WAN matching approach is needed?

  1. Configure a low-latency SD-WAN health check for both links but leave the two HTTPS applications under the same general catch-all service rule.
  2. Set the default static route toward the lowest-latency WAN and assume only the latency-sensitive HTTPS application will use it.
  3. Create one SD-WAN source-port-based rule for TCP/443 and expect it to distinguish latency-sensitive HTTPS from an unrelated HTTPS workload using the same client ports.
  4. Match the latency-sensitive HTTPS application in a higher-precedence SD-WAN rule with its SLA, leaving general HTTPS separate.

Explanation

Correct Answer

D:

Application A and B on similar ports can have different latency requirements; use separate matching SD-WAN service rules and SLA targets to direct eligible traffic appropriately. A TCP/443-only rule cannot identify which business application needs the low-latency member. Use supported application-signature or destination-aware SD-WAN matching, verify the rule's precedence, and test both workloads' selected links and SLA results.

Incorrect Answers

A:

SLA measurements alone do not identify which of two TCP/443 applications needs premium steering. An application/destination-specific service rule must match the sensitive one separately.

B:

A destination default route affects all otherwise eligible sessions, including ordinary HTTPS. The case requires a scoped SD-WAN match rather than a global route change.

C:

Transport port matching cannot reliably tell two TLS applications apart when both use the same HTTPS service. Define a higher-precedence service rule with actual application signature or destination specificity and associate the measured performance SLA only with that workload.

Question 274

A web-filter policy logs traffic to a prohibited category, but users can still open those pages. The configured category action is Monitor. What explains this?

  1. Inspect web-filter logs for the prohibited category and enable logging on each Monitor category action so violations generate an event.
  2. Review FortiAnalyzer log forwarding and increase security-event logging detail for the category on the current web-filter profile.
  3. Change the matched prohibited web category from Monitor to Block and verify a fresh denial and security log.
  4. Change the category action from Monitor to Warning and rely on the interstitial browser warning to prevent all users from visiting prohibited pages.

Explanation

Correct Answer

C:

A Monitor action may generate a useful log without denying the matching web request. Compare the observed category/rating and matched firewall-policy profile to the configured action. If the approved rule must enforce a prohibition, select the supported Block action at the correct scope and test both disallowed and approved destinations.

Incorrect Answers

A:

Additional logging is valuable for an observation-only rollout, but Monitor passes matching traffic instead of enforcing a prohibition. The scenario explicitly needs the pages blocked; the effective category must use a blocking action with fresh-session verification, not merely more Monitor events.

B:

A richer collector record can prove which category a user accessed, but it cannot change the policy action taken by FortiGate. With the actual category set to Monitor, requests may continue even if every match is logged. Configure and test Block when prevention is required.

D:

A Warning action may permit user continuation, depending on configuration; it is not equivalent to unconditionally denying the prohibited category. Select Block and verify the event.

Question 275

A backup IPsec overlay is selected whenever one health probe stops answering, although application servers at the primary remote site remain reachable. What should be examined?

  1. Lower the backup IPsec route administrative distance as soon as the shared health probe misses one reply, without checking whether the application target is reachable.
  2. Inspect the backup IPsec child-SA lifetime and extend its rekey interval so standby tunnel negotiations occur less frequently during probe outages.
  3. Disable the primary tunnel’s SLA probe and rely on the WAN physical interface remaining Up as proof the remote protected application still works.
  4. Validate probe reachability over the intended primary IPsec tunnel against actual application health before forcing backup selection.

Explanation

Correct Answer

D:

A VPN failover path should be evaluated using targets reachable across the actual protected network; a dead or misrouted probe server can falsely mark a healthy tunnel unusable. Compare probe loss against actual application reachability and alternate health targets before forcing the backup overlay. A single unreachable monitor endpoint can trigger unnecessary failover while the primary site continues serving traffic.

Incorrect Answers

A:

A single probe-server issue may not reflect service failure. Changing route preference solely from a possibly misrouted/failed probe can cause unnecessary backup use; correlate application reachability.

B:

IPsec rekey timing can cause genuine service interruptions when negotiation fails, and this can be worth investigating if SA events coincide with loss. The observed trigger is a particular SLA health probe failing while real primary-site application servers remain reachable. A longer backup SA lifetime does not improve the probe target or measure production application health. Correlate probe source path and app reachability first.

C:

Physical interface state cannot validate a remote application or IPsec overlay health. Use an eligible representative protected-service target via the correct tunnel path.

Question 276

Session-table utilization spikes during a suspected volumetric scan. The administrator proposes raising the maximum session count. Which evidence should come first?

  1. Raise the FortiGate maximum concurrent session limit immediately and treat the increased capacity as evidence the source scan is harmless.
  2. Measure scan-driven sessions, half-open rates, occupancy and resource use before applying DoS or session-limit mitigation.
  3. Disable the firewall's DoS anomaly checks to improve throughput during the event.
  4. Reduce all TCP application idle timeouts globally to a few seconds without isolating the scanning sources or recording established business-session requirements.

Explanation

Correct Answer

B:

An unusually large session table can consume resources during a flood; examine connection distribution, session states and CPU/memory counters before selecting mitigation. Inspect session creation rate, table utilization, source concentration and CPU/memory pressure during the suspected scan. Raising capacity without controlling malicious connection churn can postpone failure while amplifying resource exhaustion.

Incorrect Answers

A:

Adding session capacity without understanding active/half-open rate and resource pressure can worsen an attack’s impact. Measure source behavior and state usage before DoS/session policy action.

C:

Turning off protection can amplify the load. Use scoped diagnostic counters and confirmed thresholds instead of removing the control indiscriminately. DoS anomaly checks can identify abusive creation rates; disabling them during a suspected attack removes useful containment.

D:

Broad timeout reduction may disrupt legitimate traffic and obscures which scan behavior fills state. Use observed per-source session creation and process counters to choose targeted mitigation.

Question 277

In a FortiOS 7.6.0 DC-Agent FSSO deployment, a recent firewall ACL change blocks UDP/8002 from one domain controller to the FSSO Collector Agent. Other DC agents still work and the collector-to-FortiGate TCP/8000 channel remains connected. No new logons from this one DC appear. What targeted test and fix are appropriate?

  1. Reconfigure collector-to-FortiGate TCP/8000 connectivity even though fresh event feeds from the other controllers confirm that leg is functioning.
  2. Allow domain-controller LDAP TCP/389 to the FortiGate and assume the FSSO DC-Agent UDP event channel automatically uses that directory connection.
  3. Restore narrow DC-Agent UDP/8002 permission toward the collector and verify new FSSO identity updates reach FortiGate.
  4. Allow only LDAP/LDAPS binds from the collector to the domain controller.

Explanation

Correct Answer

C:

Fortinet documents that in DC Agent mode each DC agent forwards logons to the Collector Agent, which listens for those updates on UDP port 8002 by default, while the Collector communicates with FortiGate over TCP port 8000. Confirm actual configured ports, capture the blocked UDP leg, restore only the required ACL and test a fresh logon, collector user-IP mapping and FortiGate identity event.

Incorrect Answers

A:

The blocked segment is DC Agent to Collector UDP/8002 for one controller. Changing the already functioning collector-to-FortiGate leg does not restore those missing domain events.

B:

LDAP queries and DC-Agent event transport use different protocols and paths. The collector must receive UDP/8002 notifications and then forward learned mappings over its existing TCP/8000 path.

D:

Agent-based FSSO and direct directory polling use different pathways. LDAP connectivity to the domain controller may serve group lookup but does not repair blocked push event traffic from the DC Agent to the collector. Validate UDP/8002 or the configured agent port instead.

Question 278

Application-control logs report a user, but the visible source address is a public translated address rather than the workstation's private IP. What should be correlated?

  1. Use the public post-SNAT source address alone to identify the employee, without reconciling original client IP and security-policy identity.
  2. Delete the FSSO identity mapping to make the public source IP disappear from all application-control logs.
  3. Map the application log to pre-SNAT user/source tuple and its actual FSSO or authentication record before attribution.
  4. Use the application signature name as the employee identity and disregard the FortiGate source-user field because NAT has rewritten the client address.

Explanation

Correct Answer

C:

Source NAT can change the IP seen downstream, while FSSO mappings can reference the original client; correlate pre/post-translation tuple and event timestamps before attributing users. Track the logged public translated address to the original client tuple and its contemporaneous identity-to-IP mapping using NAT/session fields. A public SNAT address is not itself the authenticated workstation; preserve temporal linkage before attributing an application event.

Incorrect Answers

A:

A shared translation address can represent many users. Attribution requires joining the session’s pretranslation tuple with the FSSO or authentication mapping at the event timestamp.

B:

Removing identity can break user-based policy matching without altering the translation. Inspect logged fields and the selected SNAT pool rather than destroying mapping evidence. Deleting an identity map destroys valid attribution rather than reversing translation in an existing application event.

D:

Application classification identifies traffic type, not a person. NAT may hide original addressing, but actual user mapping remains available through correlated session and authentication evidence.

Question 279

An administrator added a route for a remote address pool to tunnel-A, but the pool is behind tunnel-B. Authentication succeeds; sessions fail. What should change?

  1. Inspect the tunnel-A route’s distance and add a less-preferred default route through the healthy tunnel-B interface.
  2. Review phase-two selectors on both tunnels and include the remote address pool in each child SA.
  3. Rotate both tunnels' preshared keys as the first repair because application traffic cannot reach the remote pool.
  4. Point the remote pool’s static route to tunnel-B and validate installed path, selectors, policies and reverse reachability.

Explanation

Correct Answer

D:

Valid IKE authentication on tunnel-A and B does not mean every internal prefix is reachable through either peer. The remote address pool belongs behind tunnel-B, so the route should resolve to that interface and be supported by the correct policy and phase-two protected subnet definitions. Confirm reverse routing from the remote side and tunnel packet counters before retesting the application.

Incorrect Answers

A:

The explicit route to the remote pool is more specific than a new default. It can continue selecting tunnel-A even if the backup default points to tunnel-B. Update the protected-prefix route to the correct tunnel and examine both peers’ selectors and return routing.

B:

Selectors determine eligible encrypted subnets, but overlapping them across two peers cannot force the forwarding table to choose tunnel-B. The faulty static route still sends pool traffic toward tunnel-A. Correct route selection first and retain only the intentional encryption scope for each peer.

C:

IKE authentication already succeeds; a wrong destination route is a forwarding issue. Changing keys can disrupt healthy SAs without correcting the misplaced prefix. A preshared-key failure would affect IKE authentication; the described defect is an installed route toward the wrong peer.

Question 280

A signed business application is blocked by an antivirus signature that the vendor disputes. Security still needs protection against other malware. What should guide the exception?

  1. Inspect the vendor attestation and temporarily disable file antivirus for only the application’s executable-download policy.
  2. Trust the executable publisher signature alone and whitelist every future signed file from that vendor across all antivirus policies.
  3. Correlate the AV event’s hash and signature with the vendor claim before granting a narrowly approved file/signature exception.
  4. Create an antivirus exclusion for all executable filenames matching the application family’s usual installation pattern.

Explanation

Correct Answer

C:

False-positive antivirus response should be scoped by file evidence and detected signature; a narrowly approved exception must not disable protection for unrelated files. Record the exact disputed AV signature and safe file hash, verify reputation or a false-positive submission with Fortinet, then apply a time-bound, narrowly scoped supported exception if justified. Retest the approved signed app and unrelated malicious test files.

Incorrect Answers

A:

The publisher’s statement is a useful lead, but it does not establish that the detected hash is benign or that no other malware uses the same path. Disabling an entire antivirus profile removes unrelated protections. Reconcile the precise hash, AV detection and signed-file provenance before any narrow approved exception.

B:

A valid publisher signature can identify origin but not exclude malicious or compromised signed content. Make evidence-based, file/signature-scoped decisions rather than open-ended vendor allowlisting.

D:

A filename pattern can isolate a release family operationally, but it is not a robust indicator of a particular verified false positive and may admit malicious files with reused names. A narrower exception should depend on the confirmed hash or signature, appropriate verification and change-control expiry.

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