Fortinet NSE4_FGT_AD-7.6 Practice Test 23
Question 220
A proxy-based web-filter feature works on one FortiGate rule but does not appear in a flow-based profile selected on another rule. Which configuration should be compared?
- Inspect the flow-based profile in the CLI for a setting matching the legacy proxy web-filter option, then apply that setting to the flow rule.
- Align the effective firewall rule’s flow/proxy inspection mode with its supported web-filter features and test matched URLs.
- Compare the feature lists, then migrate every internet firewall policy to proxy inspection to standardize all web-filter profiles.
- Enable a more permissive FortiOS firewall policy service for HTTPS but leave its selected web-filter feature on a flow-based profile that does not support it.
Explanation
Correct Answer
B:Flow and proxy inspection have different buffering and feature support; confirm that the requested web/AV operation is available in the chosen mode and trace its action. The missing proxy-only action may not be available in a flow inspection profile, even if both are called web filters. Verify the policy inspection mode and the profile's supported feature set before moving the rule, and compare the real security and latency tradeoffs. In FortiOS 7.6.0, proxy-based inspection is unsupported on physical FortiGate models with 2 GB RAM or less; confirm model capacity before selecting that mode (VM behavior differs).
Incorrect Answers
A:The CLI exposes configuration detail, but it cannot make a proxy-only feature supported by the flow inspection engine. The effective firewall policy mode and the selected profile feature set must agree. Confirm supported alternatives and actual URL behavior before replicating a setting from another mode.
C:A proxy policy can offer features absent in flow, but a universal migration can change latency, supported protocol behavior and appliance capacity, including small-memory physical models. This is one affected rule. Choose the inspection mode and security profile based on the needed supported action, model and controlled performance tests.
D:Widening transport permission cannot make a proxy-only inspection feature appear in an incompatible flow-based web-filter profile. Check the effective policy inspection mode and the supported FortiOS profile features before changing service selection.
Question 221
An HA cluster needs a FortiOS maintenance upgrade while preserving service. Engineers propose upgrading the active appliance arbitrarily first. Which procedure is appropriate?
- Follow Fortinet’s supported HA cluster firmware upgrade sequence, checking compatibility, rollback and session failover continuity.
- Upgrade the subordinate to a newer standalone FortiOS build, then reboot the primary without following Fortinet’s documented cluster upgrade sequence.
- Upgrade only the standby permanently to a new incompatible version.
- Change device-priority and override settings during the firmware upgrade until both members report their intended HA roles after reboot.
Explanation
Correct Answer
A:Use a compatible Fortinet-supported HA firmware upgrade path, preserve a configuration backup, and schedule a controlled maintenance window. In the default uninterrupted cluster-upgrade sequence, subordinate units upgrade before a new primary is selected and the former primary upgrades. Verify heartbeat, configuration synchronization, health and application continuity after the staged process. Do not arbitrarily upgrade only the active member or force repeated role changes without a tested rollback plan.
Incorrect Answers
B:An unsupported mixed-version arrangement can break cluster synchronization and traffic continuity. Use the Fortinet-supported in-cluster upgrade path and validated rollback, not ad hoc sequencing between members.
C:Unsupported mixed versions can disrupt cluster membership and synchronized flows. Follow Fortinet's documented supported upgrade path and version compatibility. HA state synchronization requires a supported software compatibility path; a permanently mixed-version pair is not a reliable continuity design.
D:Election settings govern member preference, not compatibility of firmware images or ordered upgrade/failover. Uncontrolled changes may obscure actual cluster health; follow the supported upgrade sequence and verify session continuity.
Question 222
An employee successfully authenticates to a user-based firewall policy, then changes directory groups while their TCP session remains open. When should the new entitlement take effect?
- Reevaluate every established TCP packet against the latest directory group on each pass and assume the firewall automatically tears down mismatched sessions.
- Recheck updated user/group identity and the existing session’s authorization; expire old state when revocation is required.
- Add the employee to both old and new groups temporarily to keep the existing session connected regardless of intended revocation.
- Create a second permit policy for the new user group while leaving the authenticated session and previous group authorization state untouched.
Explanation
Correct Answer
B:A successful new FSSO login can coexist with sessions created under an older mapping; test whether policy re-evaluation or session clearing is necessary for the changed user. A previously established TCP session can retain state and authorization even after a directory-group change, depending on policy re-evaluation and session lifetime. Compare fresh and existing sessions and use controlled session revocation when the entitlement must end immediately.
Incorrect Answers
A:Existing stateful sessions need not be immediately reclassified after a directory change. Confirm identity-cache refresh and the session lifecycle; when revocation must be immediate, invalidate existing state through a supported process.
C:That may preserve access after a legitimate privilege removal. Use the supported identity/session revocation procedure and reauthenticate as needed. Granting both groups weakens deliberate revocation and obscures whether the stale session should continue; compare authenticated current membership.
D:A new rule may govern future sessions but does not necessarily revoke an established flow authorized under the prior group. The required entitlement transition needs group mapping and session-state handling.
Question 223
A video meeting is choppy but FortiGate application-control logs show the app is permitted. SD-WAN statistics report significant jitter. What should be diagnosed?
- Inspect the conferencing application sensor and switch its existing Allow action to Monitor to collect additional app-control events during the call.
- Disable every application-control signature because a permitted application cannot be degraded by network conditions.
- Review UDP session expiry statistics and lengthen the meeting application’s idle session timeout on the matched firewall policy.
- Correlate the permitted conferencing application with SD-WAN jitter, health-SLA selection and congestion during the impaired call.
Explanation
Correct Answer
D:For video calls distinguish application-control deny events from packet loss, jitter and constrained SD-WAN member choice; each produces different logs and remedies. The app-control action is Allow, so inspect voice path quality, the selected SD-WAN member, measured jitter and congestion during the choppy call. Changing an application signature cannot correct a WAN link that fails real-time performance requirements.
Incorrect Answers
A:Monitor may supply extra application visibility, but this traffic already matches the intended signature and is permitted. The impairment is correlated with high SD-WAN jitter, not an application-control denial. Diagnose the selected member, performance SLA and congestion, preserving the authorized application decision.
B:No deny event does not prove latency is low. Disabling security profiles is not a first response to an observed path-quality problem. Disabling application controls removes a separate security layer while leaving the WAN quality impairment unexplained.
C:UDP timeout tuning can matter when idle state is expiring, but it cannot reduce packet-delay variation on a congested WAN link. The case supplies measured jitter while application control permits traffic. Correlate real call timing with selected SD-WAN path metrics and health-based steering.
Question 224
A FortiGate physical interface reports growing CRC errors during peak traffic, but firewall permits are correct. What should be examined first?
- Move the matched interface firewall Accept policy to the top of the rule table, expecting a rule precedence change to reduce Ethernet CRC errors.
- Force a higher port speed or full-duplex setting.
- Switch the link MTU setting to the largest supported value and preserve the same physical interface and transceiver without checking counters.
- Investigate CRC counters, cables, SFP and speed/duplex negotiation at both physical link ends before modifying firewall rules.
Explanation
Correct Answer
D:Increasing interface CRC or physical errors under load points to media, negotiation, optics or switch configuration; inspect counters and link characteristics before firewall policies. Growing CRC errors point to physical frame integrity: check cable, transceiver, duplex/speed negotiation and peer-interface error counters. Verify errors clear after the targeted link fix rather than widening a firewall policy that already permits the traffic.
Incorrect Answers
A:CRC errors originate at the link or framing layer and are not corrected by policy precedence when forwarding already permits traffic. Inspect the port, cabling, transceiver and negotiated speed/duplex.
B:A mismatched or unsupported forced speed/duplex setting can create more frame errors. CRC counters point to a Layer 1/2 fault; inspect transceiver health, cabling, link partner settings and interface statistics before any coordinated negotiation change.
C:MTU mismatch can affect certain packets, but it does not directly establish the cause of rising Ethernet CRC errors. Verify layer-one framing and both ends of the physical link before changing unrelated path parameters.
Question 225
FortiGate connects successfully to the FSSO collector, but a security policy shows no selectable groups for the intended AD organizational unit. What should be checked?
- Inspect the FortiGate remote-user-group object and create a group with the intended AD name even though that group is absent from the FSSO collector feed.
- Review the Security Fabric external connector health and reconnect it after editing only the firewall policy source address object.
- Check FSSO collector AD group filters and read rights, then FortiGate connector group visibility and membership scope.
- Turn on an all-groups collector import and use the resulting general domain-user group for the restricted policy.
Explanation
Correct Answer
C:A reachable FSSO collector proves transport connectivity but not that the intended AD groups were selected or imported. Compare the collector’s monitored domain, group filter, account permissions and FortiGate connector group mapping. Refresh supported group retrieval after fixing the scope and verify one expected group member and one excluded user before assigning access.
Incorrect Answers
A:A named group object can be useful only when its underlying directory identity or SID is actually available from the collector. It does not import a missing group merely by matching its display name. Check collector selection filters, directory read rights and FortiGate group visibility before applying the restricted rule.
B:Reconnecting can refresh data but a source-address object is unrelated to the collector permission or filter that publishes AD group memberships. The FortiGate connection already succeeds and the group is absent. Inspect collector imports, read access and selected groups instead of changing unrelated traffic selectors.
D:Broad import may expose missing memberships for troubleshooting, but assigning a general group to a scoped policy could authorize unintended users. Identify the intended group's exact directory scope and collector filter, then choose only that mapped group for policy enforcement.
Question 226
Two SD-WAN members distribute new outbound sessions across different ISPs with different NAT pools. After failover, some replies arrive on the opposite member and are dropped for lack of compatible state. What information should the engineer correlate before changing load-balancing behavior?
- Enable SD-WAN session-based load distribution across both ISPs, allowing each new packet to choose the currently better link regardless of its NAT binding.
- Force all returning packets to whichever WAN has the lowest current jitter, regardless of the original session path.
- Correlate original/translated session five-tuples and selected SD-WAN member with the return captures on both ISP paths.
- Confirm that both SD-WAN performance SLA targets respond on each member and use that as proof all established NAT sessions return over their original member.
Explanation
Correct Answer
C:Different ISP NAT pools can create address and port translations that upstream paths must route back to the right FortiGate state. Compare the original WAN member and translated source for a new session, the return packet destination/ports and actual session lookup after failover. FortiOS may accept asymmetric reverse packets that match state, so prove a translation or session mismatch instead of assuming every different ingress interface causes a drop.
Incorrect Answers
A:Session-based load selection can use multiple ISPs, but moving packets of an existing NATed flow among different translated sources can destroy return-state consistency. Analyze original/translated tuples and member symmetry before changing the forwarding strategy.
B:Return-path routing has to preserve NAT and session consistency where required. Independently changing uplinks from application SLA values can send traffic to a path lacking the expected state. Compare the original packet five-tuple, selected outbound member, translated source and the reverse packet path on both WAN interfaces.
D:Link health checks indicate probe reachability, not whether each established connection preserves a compatible source address and reverse path. The rejected return packets must be correlated with their stored session and NAT translations.
Question 227
A suspicious executable passes basic antivirus signatures, but the policy calls for detonation-based analysis of unknown files. FortiSandbox integration is available. What should be evaluated?
- Use the supported FortiSandbox submission path in the matching antivirus profile and verify executable verdicts and entitlement.
- Check FortiGuard antivirus database freshness and schedule a new AV signature update before rerunning the unknown executable.
- Inspect FortiSandbox detections on the FortiAnalyzer collector and use the same filename in an unrelated email-scanning event as the outbound-file verdict.
- Configure antivirus to mark unknown executables as clean until FortiSandbox issues an asynchronous verdict, without a quarantine or post-verdict response design.
Explanation
Correct Answer
A:An unknown suspicious executable may require dynamic sandbox analysis beyond a static antivirus signature decision; a scan miss is not a clean verdict. Use the supported FortiSandbox integration for eligible file types, including controlled submission, verdict correlation and privacy limits for sensitive files. Specify how pending, malicious and timeout results affect file delivery, and verify the enforced profile action using a safe simulation.
Incorrect Answers
B:Signature freshness is worth checking but a local AV scan with no known match does not prove detonation of an unknown file. The stated policy specifically requires FortiSandbox dynamic analysis. Confirm supported submission from the effective profile, entitlement, asynchronous verdict and handling of pending or malicious files.
C:Sandbox detection logs can establish a known submission, but a matching filename on another policy or transport does not prove that this specific executable from the outbound session was analyzed. Link the exact file hash and session to a supported submission path, verdict and enforcement treatment.
D:Asynchronous analysis may be appropriate for supported modes, but unconditional clean disposition bypasses the required detonation decision. Verify supported hold/post-transfer behavior, alerts and response handling rather than silently trusting an unscanned file.
Question 228
A branch FortiGate encrypts packets toward the headquarters IPsec peer, but the WAN capture shows no return packets. Local firewall policy and phase-two selectors appear correct; the peer address may have changed at the provider. What should be verified before rebuilding the tunnel configuration?
- Rebuild the branch child-SA encryption proposal and increase key lifetime even though the captured packets never receive an upstream response from the expected public peer.
- Verify the headquarters peer’s resolved public address, upstream routing and return WAN captures before changing local IPsec settings.
- Create a new LAN-to-IPsec forwarding permit on the branch while keeping the same possibly outdated headquarters public peer address and upstream route.
- Inspect the remote peer IKE identity and relax remote-ID matching on the branch so a newly addressed headquarters gateway can respond.
Explanation
Correct Answer
B:An IPsec capture showing outgoing encrypted packets without any response calls for outer peer reachability and underlay routing checks before changing SA proposals. Inspect the peer public address, upstream firewall/NAT rules, UDP 500/4500 or ESP path as negotiated, and return traffic at the far endpoint. Only after transport is verified should the administrator troubleshoot IKE or child-SA mismatch; compare packet and tunnel counters after each change.
Incorrect Answers
A:Child-SA parameters govern protected traffic after peer reachability and compatible negotiation. With no return response, the first uncertainty is peer address/provider path; changing encryption cannot repair missing external replies.
C:Firewall policy can authorize protected data, but the outbound IKE/ESP packets already leave the branch and no WAN reply returns. Check live peer resolution, upstream ACLs and return routing before adding redundant local permits.
D:Identity validation is important when a peer changes its address or certificate, so checking remote IDs belongs in a full IPsec investigation. The evidence here is no returning WAN packet from the expected public destination, even before an authenticated exchange can be confirmed. Weakening remote-ID matching may admit an unintended peer and cannot establish whether packets reach the actual headquarters public address. Prove DNS and return routing first.
Question 229
A retailer protects rapidly changing container workloads in a public cloud. Its self-managed FortiGate-VM capacity is fixed and new application scale-outs regularly exceed planned throughput. The architect proposes a managed cloud-native firewall option. What should the comparison prioritize?
- Review the currently oversized FortiGate-VM instance and select a larger fixed VM type for the next planned container rollout.
- Inspect the cloud provider’s container autoscaling events and assume a FortiGate CNF subscription automatically protects every new workload.
- Route uninspected workloads around every firewall during demand spikes and claim that the security architecture remains unchanged.
- Compare CNF managed scaling, service scope and traffic insertion with VM autoscale licensing, operations and inspection coverage.
Explanation
Correct Answer
D:A managed FortiGate CNF deployment can reduce customer-operated VM lifecycle and capacity work, while a FortiGate-VM approach may require explicit instances, bootstrap, licenses and autoscaling architecture. The customer still owns its protected routes and security policies. Compare the availability and supported integration of each option in the target region and test packet traversal after a capacity change before assuming unlimited transparent scaling.
Incorrect Answers
A:Upsizing can increase capacity but retains image patching, licensing and static operating responsibilities that the proposed managed CNF model aims to change. The decision requires comparing managed-service scaling and boundaries with VM autoscale, traffic insertion and inspection coverage, not just a single larger virtual machine.
B:Container autoscaling does not by itself insert new traffic flows through the managed security service. FortiGate CNF has service scope, supported features, regional and metering constraints that must be evaluated. Validate protected network paths and actual policy coverage instead of inferring inspection from workload scaling.
C:Uninspected bypass defeats the stated requirement to protect the retailer during peak demand. Scaling problems should be handled by an approved managed-service or VM expansion design that retains inspection and route symmetry, not by turning off the security path.
Question 230
A user on the same host can open HTTPS to an application server but not its SSH management port. Both attempts reach the same FortiGate policy area. Which check best isolates the difference?
- Inspect the existing HTTPS firewall service object and add SSH TCP/22 to it for the entire original source group.
- Enable HTTPS deep inspection and assume the certificate profile also authorizes the server's SSH service.
- Review the HTTPS rule’s NAT setting and apply the same translated source IP to the new SSH session.
- Compare the failed SSH TCP/22 service and source tuple to the effective policy; permit only authorized management hosts.
Explanation
Correct Answer
D:FortiGate firewall policy matching includes the service protocol and destination port, not only the two IP addresses. A permitted HTTPS session can coexist with a denied new SSH session on TCP 22. Trace the actual rule ID and object/service definitions; if remote administration is approved, create a narrowly scoped SSH permit without broadening unrelated services.
Incorrect Answers
A:Changing the shared service could permit SSH from every host previously authorized only for HTTPS. The symptom needs a separate authorization check: compare the actual management source, destination and TCP/22 with the matching policy, and grant SSH only to approved administrative hosts.
B:TLS content inspection for HTTPS is not a firewall service allow for TCP 22. FortiOS evaluates service definitions and then any applicable inspection; the two services must be examined separately.
C:NAT may affect return routing, but the scenario distinguishes HTTPS from SSH to the same host and the existing rule explicitly matches the HTTPS service. Copying the source translation cannot make TCP/22 an authorized service. Check the rule’s service selector and a narrow management policy first.