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 39

Question 380

A compliance report must show whether an individual HTTPS request's content passed through deep inspection. Current traffic logs list the forwarding policy but no SSL profile. Which proof is necessary?

  1. Correlate applied SSL profile and actual certificate/content events with the HTTPS session before claiming decryption occurred.
  2. Inspect the HTTPS ACCEPT traffic log for the policy ID and use its accepted byte counter as evidence that the encrypted content was malware-scanned.
  3. Review the global SSL/SSH inspection feature status and export a screenshot of the configured deep-inspection profile for the audit.
  4. Use a DNS request log to infer that all later TLS URL paths were decrypted and inspected.

Explanation

Correct Answer

A:

An audit must distinguish TLS traffic that was merely seen from traffic actually decrypted or inspected for content. Correlate the session's policy ID with the applied SSL/SSH inspection profile, the chosen inspection mode, certificate events and relevant security-profile logs. Verify an authorized controlled HTTPS test shows the expected content inspection, not only a successful TLS handshake. A certificate-inspection profile alone cannot prove antivirus saw the encrypted response body.

Incorrect Answers

B:

Traffic bytes and policy acceptance establish forwarding, not a particular SSL/SSH inspection depth or content-verdict action. The same policy could use certificate-only inspection or a different profile. Correlate the actual SSL profile and decryption/content security logs with this exact request before claiming payload scanning.

C:

Global availability of a deep-inspection profile does not prove that a particular HTTPS session matched it or that encrypted payload was decoded. The compliance claim requires connection-specific policy/profile association, applicable certificate evidence and security-event disposition rather than an unused configuration screenshot.

D:

DNS may reveal a name, not the HTTPS payload or full URL path. Check which TLS profile processed the session and whether the applicable privacy exemption applied. A DNS event reveals hostname resolution but cannot demonstrate decryption of a later HTTPS request path.

Question 381

The FortiGate administrator session remains open on an unattended shared operations workstation for hours after use. Which setting should limit exposure?

  1. Set the shared administrator GUI idle timeout to unlimited duration so long incident tasks never require another FortiToken sign-in.
  2. Disable all administrator account lockouts because long-lived sessions might otherwise block the operator.
  3. Apply a bounded FortiGate admin idle timeout and named authenticated, trusted-source management for shared operations computers.
  4. Set a short firewall forwarded-traffic HTTPS idle timeout and assume it will log out the FortiGate administrator GUI session on the same host.

Explanation

Correct Answer

C:

An unattended management session on a shared operations workstation exposes privileged configuration access to the next user. Configure the supported administrator idle timeout according to business requirements, preserve named accounts, MFA/trusted hosts where applicable, and test that idle sessions terminate and require a fresh login. Extending user VPN or firewall traffic session lifetimes would not secure the administrator console.

Incorrect Answers

A:

Unlimited management sessions increase unattended access risk. The intended control is a bounded inactivity timeout with named identities and trusted sources.

B:

Account lockout and session idle timeout address different risks. Removing lockout does not safely close an unused authenticated management session. Account lockout mitigates credential attacks and is distinct from session expiry; disabling it weakens a separate protection.

D:

A forwarded-user HTTPS session timeout is not the same control as the FortiGate administrator web/CLI login idle timeout. Altering the data-plane timer may interrupt application flows while leaving management exposure unchanged. Use the appropriate administrator setting and trusted management access constraints.

Question 382

An infected workstation must be blocked from contacting internal application networks immediately, while other hosts in its subnet continue working. Where should the temporary policy be placed?

  1. Add the infected source-host deny below an existing internal subnet permit and assume the more specific address object overrides first-match rule order.
  2. Disable every LAN-to-server allow policy until the workstation is cleaned, then restore them.
  3. Apply a URL web-filter Block for the infected source IP on the server policy, leaving nonweb application sessions and existing accepted flows unchanged.
  4. Place a narrowly scoped host deny above effective permits and clear selected existing sessions for immediate containment.

Explanation

Correct Answer

D:

For an urgent but scoped host block, place an explicit deny rule that matches the verified offending source or destination, required interfaces and relevant services ahead of otherwise permitting rules. Document the trigger, intended expiry and change owner. Confirm the session is actually blocked and that neighboring legitimate traffic still matches its normal policies. Clearing sessions or disabling the entire application profile can produce a broader outage without providing a controlled exception.

Incorrect Answers

A:

An earlier general permit can shadow a later host deny. Place the scoped deny above applicable rules and re-evaluate new sessions.

B:

A blanket deny disrupts unrelated users and creates an avoidable outage. Apply a narrow temporary source and destination condition with a recorded owner and removal criterion. Removing every server permit would interrupt unrelated healthy hosts; isolate the compromised workstation and document the action.

C:

Web-filter destination controls do not provide comprehensive source-host containment across internal services. Use a source-specific forwarding deny and state cleanup.

Question 383

A site-to-site design has IPsec tunnels over two ISPs. The auditor wants proof that a primary ISP outage does not interrupt authorized branch access for longer than the agreed recovery objective. The operator can perform a controlled outage. Which evidence should be collected to validate resilience?

  1. Show both tunnel interfaces Up during a maintenance screenshot and use that as the sole proof application traffic can recover after ISP failure.
  2. Measure controlled primary ISP outage, VPN route transition, recovered application path and service disruption against the RTO; on both new and existing flows.
  3. Disable the primary tunnel with no monitoring and assume the backup peer will be selected automatically.
  4. Measure only time until IKE phase-one reconnects on the standby peer, without confirming child-SA, protected-route and user-application continuity.

Explanation

Correct Answer

B:

A redundant VPN design is not verified by seeing two tunnel interfaces marked up. Plan a controlled failure of the primary ISP or tunnel, capture IPsec and routing state before and after, then test permitted application traffic and its return path through the standby. Check failover time and whether existing sessions recover according to the acceptance criteria. The evidence must identify the selected route and firewall rules, not just whether an IKE SA exists.

Incorrect Answers

A:

Tunnel availability before failure does not establish route failover, return path or application recovery time. Exercise the primary outage and measure results.

C:

A forced outage without route/SLA verification can cause packet loss or asymmetric routing. Record expected selection, run a controlled failover and observe end-to-end sessions.

D:

An IKE phase-one reconnect timestamp does not prove that IPsec phase two, protected-prefix routes and permitted application traffic are functioning. Business recovery time must measure the actual branch application outage, including route convergence and both new and established sessions after the primary path fails.

Question 384

A corporation needs stricter web categories for guests than for employees. Both networks currently match one shared allow policy and web-filter profile. What should change?

  1. Use separate matched guest/staff policies with their own approved web-filter profiles and test allowed/blocked categories.
  2. Create a named Guest firewall administrator access profile and use its permissions to restrict all guest browsing categories.
  3. Review FortiGuard category-rating overrides and assign a new global category for each website commonly visited by guests.
  4. Disable all guest FortiGate web-filter profiles and rely solely on the wireless controller’s guest VLAN assignment to enforce browsing categories.

Explanation

Correct Answer

A:

The existing shared policy assigns one profile to both populations, so it cannot provide their different web category rules unless reliable per-identity policy selection is added. Match guest and staff traffic by appropriate source interfaces/groups, attach distinct web-filter profiles, and verify actual policy/profile IDs and category actions for both test users.

Incorrect Answers

B:

Administrative profiles govern what device operators can manage, not the web categories applied to ordinary user traffic. Both guests and staff still hit one forwarding policy and web-filter profile. Separate the actual traffic policies or identity matches and assign distinct approved web-filter profiles for each audience.

C:

Site rating overrides are based on destination classification, not a per-user distinction between guest and employee policy. A global override could affect staff as well and would be impractical to maintain. Use separately matched guest/staff policies and scoped security profiles to enforce different category actions.

D:

VLAN isolation identifies traffic sources and broadcast scope, but does not by itself apply the required guest-versus-staff web filtering rules. Removing the guest web-filter profile would make category enforcement depend on unrelated policies. Preserve narrowly matched guest access and apply a differentiated profile.

Question 385

The preferred HA primary has finished maintenance. Operators plan to fail back while hundreds of sessions are active. What must be validated?

  1. Confirm FGCP health and synchronization, monitored interfaces, applicable election rules and session pickup; rehearse failback with a tested rollback plan.
  2. Review the preferred member’s maintenance completion and issue a manual failback immediately while the current primary continues serving sessions.
  3. Disable HA monitored interfaces to ensure the preferred primary wins the next election even if its production WAN port remains unhealthy.
  4. Inspect device priorities and enable HA override so the former primary preempts its peer immediately after maintenance.

Explanation

Correct Answer

A:

After HA maintenance, failback should be evaluated against more than the desired primary member name. Inspect member health, configuration synchronization, monitored links, active sessions and the expected override behavior before inducing a controlled role change. Test representative existing and new connections, including paths with NAT and security profiles, and record whether state continuity meets the acceptance requirement. Forcing a failback while synchronization is incomplete can create an avoidable second outage.

Incorrect Answers

B:

Maintenance completion alone does not guarantee safe traffic movement. The cluster must have consistent configuration, healthy heartbeat and monitored interfaces, understood election behavior and session state continuity. Validate those controls and rehearse with rollback before an intentional primary role change.

C:

Monitored ports prevent an impaired unit taking over. Removing detection hides the outage and risks continuity; restore health before failback.

D:

Priority and override affect election behavior, but they do not prove the maintained member has synchronized configuration, healthy monitored links or eligible session pickup. Forcing preemption with hundreds of live sessions can cause avoidable disruption. Validate readiness, then schedule a tested failback with rollback.

Question 386

A published application needs both a TCP control channel and a UDP media stream. The public VIP currently forwards TCP only. How should the service mapping be evaluated?

  1. Map TCP control and UDP media through separate restrictive VIP/service bindings and test both protocols.
  2. Review the inbound security-policy UDP media service and add it to that rule while keeping the published VIP mapped only for TCP.
  3. Broaden the inbound firewall Accept to ALL while leaving its destination VIP mapped only for TCP control traffic and no UDP media forward.
  4. Inspect the media UDP listener and replace the current TCP control VIP with a UDP-only forwarding VIP for the application.

Explanation

Correct Answer

A:

When an application needs more than TCP, a port-forwarded VIP and service object must match the actual protocol and ports that traverse the firewall. Inspect the external mapped address, protocol-specific port ranges, matching policy and internal server listener. Create separate precise mappings where necessary instead of assuming a TCP-only VIP also forwards UDP. Use captures and session logs to prove the correct transport reaches the intended server, without opening every protocol.

Incorrect Answers

B:

The security policy can authorize UDP only after the public destination is mapped to the correct internal media listener. A TCP-only VIP does not provide the missing UDP destination NAT. Add the appropriate UDP VIP/service binding and test the external media flow without over-broadening the whole policy.

C:

ALL can expose excess services but still does not map the needed UDP port. Create a distinct UDP VIP with matched permit.

D:

A UDP mapping can carry the media path, but removing the TCP control forwarding breaks the same application’s required control channel. The design needs both authorized translations and matching firewall services, either as separate appropriately constrained VIPs or a supported equivalent that preserves both protocols. Test both independently.

Question 387

A FortiGate running FortiOS 7.6.0 sees a TLS ClientHello with a CDN-facing public outer SNI, but the browser’s intended destination hostname is not readable in packet capture. The client may have negotiated Encrypted ClientHello (ECH). What evidence-based next step avoids wrongly inferring that the browser requested only the visible CDN hostname?

  1. Check the visible outer ClientHello/SNI and ECH indicators, the effective FortiOS 7.6.0 SSL inspection mode and related SSL/DNS events before identifying the true target or making a hostname-specific policy claim.
  2. Treat the visible public CDN SNI in the outer ClientHello as definitive proof that the browser requested only that CDN host and classify the hidden destination as nonexistent.
  3. Configure a static HTTPS URL-path Block rule for the requested site using the hostname expected by administrators.
  4. Disable encryption for every corporate browser in order to restore plain-text hostname and URL visibility for troubleshooting.

Explanation

Correct Answer

A:

ECH encrypts the inner ClientHello that contains the intended destination name; the outer ClientHello may expose only a public CDN-facing SNI, which is not proof of the requested origin. Correlate the actual ECH/TLS indicators with the active inspection profile and authorized DNS evidence. FortiOS 7.6.0 has proxy-mode ECH controls; do not assume later flow-mode ECH inspection enhancements were already present. Without supported visibility, avoid falsely attributing an exact website or decrypted URL path.

Incorrect Answers

B:

An ECH outer SNI can identify a public CDN-facing endpoint while the encrypted inner ClientHello contains a different intended hostname. A readable public SNI is therefore not conclusive evidence of the final origin. Check ECH indicators and the effective SSL policy before making a site-identity determination.

C:

The captured outer public hostname is not the same as the inner requested destination, and an HTTPS URL path remains encrypted without supported inspection. A static URL-path block based on an assumed hidden destination would lack matching evidence. Examine FortiOS 7.6.0 ECH and DNS/SSL visibility, then apply a documented control only to verifiable signals.

D:

Weakening transport security globally is disproportionate and may violate privacy policy. Use supported inspection or alternate policy signals while documenting visibility limitations. Disabling TLS companywide creates serious confidentiality exposure; use supported inspection capabilities and documented visibility limits.

Question 388

A branch SD-WAN health check targets status.provider.example. Immediately after the FortiGate system DNS resolver is changed, its probe goes down, although raw IP connectivity over the same ISP still works. What should be compared before declaring that WAN physically failed?

  1. Inspect the SD-WAN member’s Ethernet carrier status and disable its failed FQDN health monitor until the next DNS refresh.
  2. Treat DNS resolution failure of the probe server as definitive proof both WAN circuits have failed, and fail all members without testing numeric IP reachability.
  3. Compare system DNS resolution and source-member route for the SLA probe FQDN before declaring WAN failure.
  4. Recreate the SD-WAN gateway routes for both members and restart all health checks after the FortiGate DNS change.

Explanation

Correct Answer

C:

An SD-WAN health check configured with a hostname can fail after DNS changes even if the WAN path remains usable by IP. Inspect the resolved monitor address, DNS server availability, source/member-specific route and probe results. Compare the same target using a suitable fixed IP or alternate supported health check to isolate name resolution. Correct the monitor dependency or resolver rather than immediately declaring the ISP link failed or changing application steering globally.

Incorrect Answers

A:

A link may be physically healthy while a probe fails because the FortiGate resolver no longer resolves the detection-server FQDN or reaches the intended member path. Disabling the monitor hides that diagnostic distinction. Test hostname resolution and member-specific probe routing before treating the WAN as unavailable.

B:

A common DNS failure can mask healthy physical ISP paths. Distinguish resolver outage from probe transport and actual application reachability.

D:

Route recreation may help when a gateway actually changes, but the symptoms began with a system DNS resolver change while numeric IP connectivity stayed healthy. Rebuilding every WAN route may disrupt working paths and does not establish FQDN resolution. Examine the specific probe name, DNS response and sourced member route.

Question 389

A new IPsec cryptographic proposal is deployed at headquarters and only one older spoke loses connectivity. Other spokes remain up. What should be compared?

  1. Deploy the newest hub IKE/ESP suite to every spoke and assume the older failing platform can negotiate it regardless of its supported transforms.
  2. Lower the failing spoke’s protected-subnet static route distance and assume the resulting route preference corrects phase-one crypto proposal mismatch.
  3. Inspect the older spoke’s IKE authentication settings and temporarily disable peer-identity enforcement on that branch while retrying the hub’s newer cryptographic proposal.
  4. Compare the older spoke’s supported IKE, ESP and PFS proposals with the new headquarters policy; negotiate an approved compatible configuration without reverting to deprecated weak cryptography.

Explanation

Correct Answer

D:

A proposal update that breaks one legacy IPsec peer should be investigated using that peer's IKE and phase-two negotiation logs. Compare supported encryption, integrity, DH/PFS choices and lifetimes across both endpoints, distinguishing a proposal mismatch from authentication or route failure. Restore a mutually supported secure setting under the organization's crypto policy; do not weaken every tunnel solely to accommodate one older spoke. Verify the negotiated SA parameters after repair.

Incorrect Answers

A:

One legacy spoke can lack the updated proposal. Match supported secure overlap with its firmware/hardware and inspect actual rejection details.

B:

A static route influences protected traffic after the tunnel has negotiated a usable IKE/ESP security association. It cannot resolve the peer proposal incompatibility observed during negotiation. Compare the supported IKE encryption/integrity, DH and child-SA/PFS transforms before changing unrelated route preference.

C:

Peer identity configuration can cause IKE failures when IDs or certificates differ, and those fields deserve inspection if authentication logs identify them. The outage began after a hub cryptographic proposal update and only the legacy spoke failed, which points first to the older device’s supported IKE/ESP/PFS transforms. Disabling identity checks weakens security and does not make unsupported encryption and group proposals compatible.

Question 390

Packets arrive on port2 but a sniffer sees none on the expected port4 egress. A matching permit is configured. What should be traced?

  1. Enable full SSL inspection on the expected port4 egress interface, assuming decrypted HTTPS causes an existing route to select the correct outgoing interface.
  2. Trace filtered ingress session through policy, route, NAT and expected port4 egress using bounded debug flow.
  3. Change the source NAT pool to a larger range without checking whether the destination route selects port4.
  4. Infer server receipt solely from the arrival packet on port2, then skip the missing port4 egress trace and investigate only the application listener.

Explanation

Correct Answer

B:

An incoming packet with no port4 egress may have been denied by policy, translated to another destination, routed through a different interface or associated with an existing session. Filter the source, destination and protocol; compare packet sniffers on both interfaces with FortiOS debug-flow and the active route. Remove temporary diagnostics after locating the actual decision.

Incorrect Answers

A:

Decryption does not select L3 egress. Trace the fresh flow through matched firewall policy and route/policy steering before changing inspection.

C:

Translation may affect reply identity but not automatically choose the intended egress. Verify route and steering decision using actual packet capture. A larger SNAT pool changes addresses, not whether the destination route selects port4.

D:

A packet capture on the ingress interface only proves the FortiGate received the frame. It does not establish that the policy accepted it, that NAT and routing chose the desired egress, or that the destination server received it. Correlate diagnostic flow with the specified egress capture.

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