Fortinet NSE4_FGT_AD-7.6 Practice Test 13
Question 120
An executable escapes antivirus detection because the FortiGate AV signatures have not updated, although the appropriate policy is enabled. Which investigation is most relevant?
- Raise the antivirus scan size threshold so larger executables are no longer exempt from file scanning.
- Inspect FortiGuard entitlement, update reachability, current AV database version and applicable scanning mode, then validate detection on a safe test.
- Inspect the existing executable file-type controls and add the missed extension to the antivirus profile before retesting the reported malware sample.
- Switch the affected antivirus profile from proxy-based to flow-based inspection without checking its definition-update status.
Explanation
Correct Answer
B:An enabled antivirus profile needs a functional signature and scanning pipeline. Confirm license status, DNS/reachability to permitted update services, database version and the actual policy’s file protocol/SSL visibility. Resolve update failure and test known benign/detection cases without exposing real malware to production users.
Incorrect Answers
A:File-size limits are important for scan coverage when signatures are current, but this case explicitly reports stale AV signatures and update failures. Raising thresholds cannot supply missing FortiGuard definitions. Examine entitlement, delivery reachability, current database and a safe detection test before changing file handling.
C:File-type filtering can make a policy more restrictive for executables, but it does not restore missing or stale FortiGuard AV signatures. A filename extension is neither a substitute for malware content detection nor proof the correct engine/database is installed. Verify entitlement, update transport, definition version and a safe supported antivirus test artifact.
D:Inspection modes affect buffering and supported actions but do not replace the threat-signature database. If FortiGuard updates are stale in the case, either mode can miss newly defined threats. Establish licensing, update reachability, and installed version, then test detection under the correct mode.
Question 121
The physical WAN port shows link down after a cable replacement, and all internet sessions fail. What should be examined before changing firewall policies or routes?
- Raise the static default route preference while leaving the WAN port physically Down and unable to negotiate link.
- Disable and recreate the internet firewall allow policy first.
- Interface physical state, cabling, switch port, speed/duplex negotiation and transceiver status where applicable.
- Replace the public source-NAT IP pool before inspecting switch-port, SFP and speed/duplex counters on the failed WAN circuit.
Explanation
Correct Answer
C:A down interface is a physical or link-layer fault until evidence shows otherwise. Verify port enablement, cable, SFP compatibility, upstream link state and autonegotiation, then confirm layer-three addressing and routes after carrier recovers. Avoid masking it with an unrelated security-policy change. A working layer-one carrier should be established before validating routing, NAT and security rules.
Incorrect Answers
A:A route metric cannot repair the absence of Layer 1 carrier after a cable change. Establish physical interface link, appropriate transceiver and speed/duplex agreement before expecting the gateway route to forward packets.
B:A firewall policy can authorize packets only after an operational interface and route allow them to traverse. Deleting or broadening access rules does not restore electrical/optical link negotiation and adds unnecessary outage risk.
D:Source NAT determines egress packet addresses, but the physical WAN link is reported Down before normal packets can exit. Compare cabling, switch configuration, transceiver and port errors before modifying a valid translation configuration.
Question 122
A branch firewall learns employee identities through an FSSO collector, but new Windows logons appear in policy only several minutes later. Which evidence best isolates the delay?
- Reduce the client-side HTTP authentication timeout and assume the FSSO collector will forward Windows logon events sooner.
- Extend the FortiGate identity-map cache so delayed collector updates are hidden by older user-to-IP assignments.
- Verify only LDAP password authentication to the domain and infer that DC Agent or polling event delivery has no delay.
- Domain controller event generation, collector polling/agent delivery timing, connector reachability and FortiGate mapping update timestamps.
Explanation
Correct Answer
D:Compare timestamps at the Windows logon source, collector, and FortiGate. Identify whether domain events arrive late, polling intervals are too long, agents cannot reach the collector, or updates are delayed on the connector. Test a controlled login/logout and measure end-to-end recognition before changing timers.
Incorrect Answers
A:HTTP login timers are different from the timing of passive Windows logon events. A delay between DC event creation and FortiGate FSSO mapping requires checking agent/collector polling, transport and current timestamps, not changing a web-portal timeout.
B:A larger identity cache may keep an outdated mapping alive longer and risk attributing a reused address to the wrong user. It does not speed new DC logon event ingestion. Establish the delay at the DC, collector and FortiGate connector first.
C:An LDAP bind can succeed while passive FSSO logon events arrive late. Compare domain-controller security event timestamps with collector records, polling/agent delivery time, and FortiGate user-IP mapping updates to isolate the actual stage.
Question 123
FortiGate reports an IPS signature match on a session carried over an allowed branch IPsec tunnel. What should an investigator establish before declaring the branch compromised?
- Review VPN IKE authentication success and mark IPS alerts from this registered branch peer as approved traffic unless the tunnel loses authentication.
- Correlate signature ID and action with the decrypted inner source/destination, policy, application and event evidence to assess the exploit.
- Block all branch IPsec sessions matching the protected subnet based on this single IPS signature event.
- Inspect IPS severity and confidence labels for the triggered signature and use those labels alone to classify the protected server as compromised.
Explanation
Correct Answer
B:Use the actual detection signature, verdict, time, source/destination addresses, applied firewall policy and contextual traffic to assess intent and impact. Distinguish a blocked attempt, a false positive, and evidence of a successful compromise. Preserve logs and investigate affected hosts proportionately. A prevented exploit attempt does not automatically demonstrate that the destination was compromised.
Incorrect Answers
A:A valid IKE peer authenticates the gateway, not the integrity of every host behind it. A compromised branch endpoint can generate malicious sessions over a trusted tunnel. Examine the inner addresses, IPS signature, action, policy and host evidence instead of equating VPN trust with benign payloads.
C:Immediate containment can be appropriate for a validated serious threat, but an IPS signature match alone may be a blocked attempt or a false positive. The question asks what to establish before declaring compromise. Preserve the signature/event context and determine the affected flow and outcome before tenant-wide disruption.
D:Severity and signature metadata assist prioritization but cannot prove that an exploit succeeded. The IPS might have blocked the packet before the server processed it. Reconstruct the matched encrypted-tunnel inner tuple, effective sensor action, host response and any corroborating endpoint evidence before declaring compromise.
Question 124
A FortiGate VM protects a production application distributed across two AWS availability zones. The solution must maintain inspection if an availability zone fails. What architecture should be validated?
- Deploy two firewall instances within the same availability zone but use no alternate route or target for an outage of that entire zone.
- Increase the FortiGate VM instance size in one zone.
- Redundant supported inspection instances across failure zones with coordinated route/failover handling, policy consistency and health tests.
- Place replicas in two zones but leave both application subnet routes permanently pointing to the primary-zone firewall, without health-based route recovery.
Explanation
Correct Answer
C:Design for multiple failure zones with the Fortinet-supported cloud deployment pattern, consistent security configuration and an explicit health-based routing or failover mechanism. Simulate AZ loss and verify both directions still traverse an authorized inspection point, with no unintended bypass or asymmetric path. Verify that neither traffic direction skips inspection during automated recovery or route reassociation.
Incorrect Answers
A:Two instances sharing one AZ do not protect against loss of that zone; independent failure-domain placement and tested traffic steering are required.
B:An individual VM of any size remains unavailable if its whole availability zone is lost. Resilience requires supported redundant instances with route and state handling.
D:Redundant instances alone do not ensure application traffic reaches the surviving appliance. Route automation or an approved insertion service and compatible policies must select the healthy zone after failure.
Question 125
An application policy was created in VDOM root, but client traffic enters VDOM tenant-a and exits via an inter-VDOM link. The policy in root never matches. What should be checked?
- Reorder firewall policies only inside VDOM root, without confirming which VDOM owns the client ingress and inter-VDOM link.
- Add an allow-any policy on the physical WAN interface of root.
- Change the default route distance in root but leave the tenant-a ingress, inter-VDOM link and policy lookup context unchanged.
- The traffic VDOM context, inter-VDOM link interfaces, route path and correct VDOM-specific firewall policies.
Explanation
Correct Answer
D:FortiOS VDOMs have distinct interface assignments, route tables and firewall policy contexts. Map the actual path across inter-VDOM links and ensure permitted flows have correct policies and routes at each relevant boundary. Test the intended tenant traffic without applying a broad allow to unrelated VDOMs.
Incorrect Answers
A:Firewall rules are evaluated in the virtual domain that handles the relevant traffic. Moving a rule within root cannot make traffic arriving under tenant-a match that rule unless the inter-VDOM path and appropriate policies send it through the correct context.
B:A broad WAN rule in a different VDOM does not replace directional policies and link interfaces along the actual tenant-a to root path. It also expands exposure unnecessarily. Identify the VDOM route and policy scope of each hop.
C:A route metric inside root affects only that context and cannot by itself fix a missing tenant-a ingress/inter-VDOM policy match. Confirm forwarding through the virtual link and applicable policy objects where the session actually traverses.
Question 126
A route to 10.90.0.0/16 is configured under a different FortiGate VDOM from the one receiving the affected traffic. Increasing the route priority does not help. What should be corrected?
- The route or inter-VDOM forwarding path in the VDOM actually performing the lookup, using the correct virtual routing context.
- Lower the administrative distance on the static route in the unrelated VDOM, expecting it to become visible automatically to the active VDOM.
- Create an all-services firewall permit in the affected VDOM.
- Rename the inactive VDOM to match the active VDOM.
Explanation
Correct Answer
A:FortiGate forwarding must find an eligible route in the routing context of the packet, including any supported VRF/VDOM boundaries. A correct route in another isolated table does not automatically apply. Inspect the effective VDOM and interface, then configure authorized inter-VDOM reachability and appropriate policy as needed.
Incorrect Answers
B:Route preference affects eligible routes inside a routing table, not visibility across distinct FortiOS VDOM routing contexts. The actual ingress VDOM requires the correct route or designed inter-VDOM transfer before metric tuning can influence forwarding.
C:A firewall policy may permit traffic but cannot create a route toward 10.90.0.0/16 that is absent from the VDOM performing lookup. Add the correct path in that context and ensure permitted inter-VDOM interfaces and return forwarding.
D:VDOM display names do not merge routing tables or automatically redistribute static entries. Confirm which VDOM and VRF receive the session, whether inter-VDOM links are configured, and which table contains the eligible destination route.
Question 127
FortiGate full SSL inspection is enabled. An upstream HTTPS server has an expired or incomplete certificate chain, and the client receives an inspection error. What should the administrator verify?
- Change the upstream server-certificate failure action to Allow for all HTTPS destinations in the shared SSL-inspection profile.
- Check the managed endpoint’s trust store and redeploy the FortiGate deep-inspection signing CA before testing the affected upstream HTTPS server.
- Check the server certificate validity and complete trust chain, FortiGate trusted CA store and configured certificate validation behavior.
- Switch the matching rule to certificate-only inspection to avoid upstream full-decryption certificate checks permanently.
Explanation
Correct Answer
C:Full inspection interacts with both client trust of the FortiGate signing CA and FortiGate trust of the upstream server. Check validity dates, hostnames, intermediate certificates and configured CA trust, then correct server-chain or trust-store faults. Test that invalid certificates are handled according to policy rather than silently accepted.
Incorrect Answers
A:A certificate-error override can let connections proceed, but applying it globally accepts invalid remote certificates across unrelated services. The scenario calls for diagnosing an expired or incomplete chain and the FortiGate trusted-CA store before deciding whether any scoped exception is warranted.
B:An endpoint that distrusts the FortiGate inspection signer can see certificate errors during normal deep inspection, so local trust is worth testing. The scenario separately reports an expired or incomplete origin certificate chain. Redeploying the inspection CA will not make the upstream certificate valid or complete; inspect the original server chain and the FortiGate validation behavior.
D:Certificate inspection may change which TLS details the FortiGate evaluates, but it also removes visibility needed for payload security scanning and does not repair a defective origin certificate. Diagnose the upstream expiry or missing intermediate first, then choose scoped compatibility measures only with justified residual risk.
Question 128
An administrator enables source NAT on a route-based IPsec policy by copying a standard internet-egress rule. The partner expects packets to retain their original 10.10.0.0/16 source. What should be evaluated?
- Always translate the source to the public WAN IP for every VPN regardless of peer requirements.
- Preserve the original private source where intended by the tunnel design, or coordinate explicit VPN NAT and matching selectors if overlapping subnets require it.
- Leave source NAT enabled but broaden both child-SA selectors to 0.0.0.0/0.
- Add a central SNAT rule translating the branch source to a different private prefix but leave the partner expecting original 10.10.0.0/16 traffic selectors and no agreed translated address design.
Explanation
Correct Answer
B:In a normal site-to-site private network design, the partner expects the original private address and routes back through the tunnel. Disable unintended source NAT and verify IPsec selectors and remote security policy. If address overlap requires intentional VPN NAT, plan the translated subnets jointly and test both directions.
Incorrect Answers
A:Unplanned public-source translation may prevent the partner from matching protected traffic selectors or returning to the expected private prefix. Internet SNAT behavior should not be copied blindly to tunnel policies.
C:Broad selectors do not guarantee the peer will accept packets with the unexpected translated source or that the expanded policy is authorized. The partner expects the original 10.10.0.0/16 identity, so preserve that address across the VPN unless a documented overlap requires coordinated NAT and matching policy/selector changes.
D:Additional source translation only works if the peer explicitly expects the translated protected prefixes and the child-SA selectors, routes and firewall policies agree. The given partner expects original 10.10.0.0/16 identities, so inventing an uncoordinated second SNAT rule prolongs the mismatch.
Question 129
A departed employee can still access a FortiSASE-protected private application because their browser session remains usable after the identity provider disables the account. Which improvement is needed?
- Let the existing browser/session cookie remain valid until its maximum lifetime even after HR disables the identity provider account.
- Remove private-application user-group conditions, relying on the formerly successful identity-provider login as perpetual authorization.
- Reduce only the FortiGate WAN route distance, without clearing the authorized session or re-evaluating its disabled user identity.
- Use supported session expiration or forced disconnect and identity/group access revocation so an existing FortiSASE application session cannot outlive the approved employee access window.
Explanation
Correct Answer
D:Disabling a user at the identity provider may not terminate already-established VPN, SWG or browser application sessions immediately. Audit the FortiSASE access and authentication lifecycle, apply supported connected-user session termination or bounded reauthentication and remove the former employee from permitted groups. Test denial from the currently connected endpoint and a fresh session; do not assume every FortiSASE version supports instantaneous token invalidation.
Incorrect Answers
A:An identity-provider disable action may not invalidate an already-authorized SASE or application session immediately. A deliberate offboarding process must account for active connections and established tokens, not wait indefinitely for an unrelated expiration.
B:An allow rule without identity and session invalidation would worsen former-employee access. Tie session control to the actual identity lifecycle and verify deprovisioning through a denied test connection.
C:A route-preference change does not revoke a user identity, terminate an access token or invalidate the authorized application session. Inspect tenant session duration, connected-user state and supported access revocation/deactivation controls, then test the effective denial.
Question 130
FortiGate uses Central SNAT. A new outbound security policy permits traffic but the public source address is not the requested IP pool. Where should NAT be corrected?
- Enable the NAT checkbox on the outbound security policy while retaining central NAT mode and leaving the matching Central SNAT map unchanged.
- In the Central SNAT map matching the traffic, including rule order and selected IP pool, rather than assuming per-policy NAT governs it.
- Reorder the outbound ACCEPT firewall rule while leaving the matching central-SNAT pool and source/destination/interface selectors unchanged.
- Add a new central-SNAT entry using the desired IP pool BELOW an earlier catch-all central-SNAT rule that still matches every affected outbound session.
Explanation
Correct Answer
B:Central source NAT evaluates its own rule entries to select address translation. Compare original source, destination, egress interface, ordering and pool assignment against the live session translation. Correct the narrow intended rule and verify return connectivity and public address ownership without changing unrelated firewall actions.
Incorrect Answers
A:With Central SNAT enabled, source translation is configured in the separate ordered central SNAT map; the security policy permit does not replace the actual egress NAT rule.
C:Firewall permission order can affect which traffic policy accepts a session, but when central SNAT is enabled, the translated source comes from the matching central-SNAT map. Confirm its criteria and pool, then test a new session rather than assume rule order picks the public IP.
D:A later source-NAT map may never be reached if an earlier broader map matches the traffic. Inspect central-SNAT ordering, source/destination/service selectors and chosen pool, then place an appropriately scoped mapping so the desired public source actually applies.