Fortinet NSE4_FGT_AD-7.6 Practice Test 22
Question 210
A corporate SaaS application should reach a trusted regional gateway using SD-WAN. General browsing must continue to use cheaper internet links. Which rule design should be tested?
- Make the regional gateway the first interface preference in the catch-all SD-WAN rule while preserving its match to all internet traffic.
- Change the global default-route gateway to the trusted regional path for every employee, including unrelated browsing.
- Add a dedicated HTTPS Accept firewall policy for the SaaS FQDN without creating an SD-WAN service selection for the eligible regional member.
- Place the scoped SaaS SD-WAN rule above browsing, restricting regional members and verifying actual new-session egress.
Explanation
Correct Answer
D:The regional gateway should be an eligible SD-WAN member with a matching specific rule and representative SaaS health check, while honoring source and application policy. Build a specific SaaS application or destination match above the general browsing SD-WAN rule, with the approved regional gateway and eligible SLA targets. Test both SaaS and non-SaaS sessions to confirm they select their intended links.
Incorrect Answers
A:A catch-all rule could steer general browsing to the regional gateway as well, violating the requirement to keep unrelated traffic on lower-cost links. A higher-priority narrow SaaS rule must distinguish the application or destination.
B:That sends all default traffic to the region rather than steering only the approved application. Combine destination-aware SD-WAN rules with valid route and health checks. A global default-route change affects unrelated destinations and can violate the stated separation of SaaS and ordinary browsing.
C:The security policy may permit the connection but does not by itself force the specified regional egress when the broader SD-WAN steering rule chooses other links. Confirm an application/destination match in the service rule.
Question 211
A branch must recover configuration after its FortiGate fails. The available replacement has a different hardware model, different physical port numbering, and an earlier FortiOS build. The stored backup contains WAN routes and security policies. Which preparation minimizes restore failure and management lockout?
- Edit the original backup's port names by hand to match the replacement chassis before loading it unchanged.
- Use a supported cross-model and firmware configuration migration, validate port mappings, backup and console rollback before restore.
- Upgrade only the replacement to the source firmware version and then upload the original unconverted backup.
- Inspect the replacement console recovery procedure and factory-reset the appliance before importing the original unconverted backup from the failed different-model device.
Explanation
Correct Answer
B:Fortinet identifies wrong hardware model or firmware as common reasons for a configuration-file restore error. Identify a supported target version or conversion method before applying the backup; map physical interfaces, HA and WAN paths, safeguard licensed or private credentials, and maintain console access plus a rollback so service can be recovered safely.
Incorrect Answers
A:Port remapping can be part of a deliberate conversion, but the backup also belongs to a different model and newer firmware. Fortinet documents that direct restore may be rejected on either incompatibility. A supported migration and version reconciliation are required before a controlled backup/restore test.
C:Matching software builds removes one risk but does not make different hardware models and port numbering automatically compatible for a direct restore. Model-specific settings may still fail. Validate a supported conversion, interface mapping, admin access and rollback after firmware alignment.
D:Console and a clean initial state are valuable recovery safeguards, but a reset does not convert interface names or unsupported configuration syntax from a different hardware model and earlier firmware. FortiOS may reject an incompatible restore or leave required routes and management ports mismapped. Perform a supported model/version migration, test the converted backup and retain rollback access.
Question 212
A security requirement says blocked connections should receive an explicit refusal. The existing deny rule drops matching TCP packets silently. Which interpretation should guide the change?
- Check Log Violation Traffic on the matched DENY rule and enable detailed event logging before repeating the blocked TCP connection.
- Inspect the DENY policy sequence and move the rule higher while leaving its current silent-drop response behavior unchanged.
- Enable the supported send-deny-packet response on the narrowly matched DENY policy, verify TCP reset versus ICMP behavior and test the actual refusal.
- Enable deny-traffic logging on the explicit policy without configuring the FortiOS supported deny-packet signaling behavior requested for rejected TCP sessions.
Explanation
Correct Answer
C:FortiOS firewall policies use Accept and Deny; Deny normally drops matching traffic. When the requirement is an explicit response, inspect the supported `send-deny-packet` setting for that DENY policy and the relevant `deny-tcp-with-icmp` system behavior. Depending on those settings, denied TCP may elicit a TCP reset or ICMP prohibited rather than silent timeout. Confirm the response with a fresh controlled connection and a packet trace; policy logging alone does not send a client refusal.
Incorrect Answers
A:Traffic logs can show that the firewall denied the packet, but they do not cause a TCP RST or ICMP response to be sent to the client. The requirement is explicit network-layer refusal; test the supported send-deny-packet behavior on the intended deny and inspect what the peer actually receives.
B:Ordering can determine which rule rejects an incoming flow, but once the described deny is already matching, moving it cannot change silent-drop behavior into an explicit refusal. Select and verify the supported deny-packet signaling configuration and any TCP/ICMP platform behavior.
D:Logging records that the firewall denied the session, but does not itself guarantee that the client sees a TCP RST or appropriate ICMP refusal. Verify the explicit deny policy and supported send-deny-packet option, plus any deny-tcp-with-icmp behavior, using a controlled test.
Question 213
Two FortiGate VPN peers negotiate across a provider NAT device. UDP 500 is visible, but ESP-based payloads fail and session mappings expire. What should the operator inspect?
- Permit native ESP protocol 50 at the provider firewall but retain a rule that blocks UDP/4500 for any NAT-detected IKE peer.
- Inspect the child-SA ESP encryption settings and harmonize the IPsec transform proposals before changing provider UDP/4500 forwarding.
- Review the IKE SA lifetime and enable more frequent peer keepalives while preserving the upstream router rule that filters UDP/4500.
- Verify IKE UDP/500 and NAT-T UDP/4500 connectivity in both directions and keep provider NAT mappings active.
Explanation
Correct Answer
D:IKE commonly uses UDP 500, with NAT traversal encapsulating IPsec ESP traffic on UDP 4500; confirm intermediary state and the supported peer NAT-T settings. With an upstream NAT device, verify IKE negotiation on UDP/500 and NAT traversal on UDP/4500, including NAT state and tunnel endpoint identity. A phase-one request arriving does not prove child-SA traffic survives NAT or permitted return mappings.
Incorrect Answers
A:ESP transport may be appropriate when there is no NAT, but the scenario explicitly includes a NAT device and expiring mappings. NAT traversal normally encapsulates ESP in UDP/4500, so native ESP alone misses that path.
B:ESP proposals matter after IKE establishes a transport path. This case reports that intermediary NAT and firewall behavior disrupts ESP/NAT-T payload reachability, not an authenticated child-SA proposal rejection. Verify UDP/500 initiation, bidirectional UDP/4500 encapsulation and stateful mapping timeouts before changing cryptography.
C:Keepalives can help maintain a working NAT mapping, but they cannot carry encapsulated ESP through a provider firewall that drops the required transport port. Establish a permitted bidirectional NAT-T path and correlate its connection entries before tuning IKE lifetimes.
Question 214
An application migrates to a nonstandard TCP port, but the same exploit pattern is observed. The IPS sensor matches protocols rather than only default service ports. What should be tested?
- Inspect application-control events on TCP/8443 and confirm the application signature name shown for the new port.
- Test IPS decoding and signature action on observed TCP/8443 traffic with a safe authorized exploit-pattern simulation.
- Disable all application-control and IPS signatures because custom port assignments make signature inspection unreliable.
- Create a TCP/8443 firewall service object and attach it to the inbound permit that already has the standard-port IPS sensor.
Explanation
Correct Answer
B:FortiOS IPS may use protocol decoders and signature logic that are not restricted to a service’s common TCP port, but actual coverage depends on the enabled sensor, signature and visibility. Observe traffic on the changed port, correlate the matched firewall policy and signature logs and perform a safe representative test before concluding the application is protected or unprotected.
Incorrect Answers
A:Application identification is useful background, but it is not proof that the configured IPS attack decoder and blocking signature examine the exploit payload on a nonstandard service. Test the actual IPS sensor action and detection for an authorized representative pattern after the port migration, not just the application label.
C:Nonstandard ports require testing but do not justify abandoning inspection. Verify supported protocol decoding, service settings and the effective policy. Disabling sensors sacrifices exploit detection; validate the signature trigger and policy profile against the new port instead.
D:Service matching can ensure the migrated traffic reaches the intended policy, but a correct port object does not itself prove the IPS decoder supports the modified protocol or the matching signature remains active. The question calls for measured exploit-pattern inspection evidence on the new traffic path.
Question 215
A FortiGate model without an SSD is configured for persistent local disk logs and reports storage errors. Where should long-term events be kept?
- Set the local logging target to Disk and raise the maximum log file size to retain the compliance period on this SSD-less hardware.
- Increase the administrator inactivity timeout so traffic logs stay visible in the browser after signout.
- Forward logs to a durable authorized FortiAnalyzer or equivalent central collector, validating retention instead of relying on volatile memory.
- Store logs in the FortiGate memory log and export monthly copies manually after the configured memory log threshold is reached.
Explanation
Correct Answer
C:Local memory logging is transient and small flash/disk can constrain retention; use a supported FortiAnalyzer/FortiGate Cloud target with defined event storage and verification. If this appliance lacks supported local disk logging, select a managed FortiAnalyzer, FortiGate Cloud or approved remote syslog retention target. Verify actual receipt, searchability and capacity; local memory logs are not a reliable long-term forensic archive.
Incorrect Answers
A:Increasing a disk log quota cannot create an absent persistent disk. This model needs a supported remote storage/collector strategy for retention; memory buffering alone does not deliver the required durable history.
B:Administrative session settings do not provision persistent log storage. Select a suitable FortiAnalyzer/FortiCloud destination with verified delivery and retention. GUI inactivity controls administrator sessions rather than log retention; use a supported remote log sink with verified storage.
D:Memory logs are finite and volatile, so a threshold-triggered manual export can lose events before collection or during power loss. A reliable central destination with verified ingestion and retention is required.
Question 216
A LAN client accesses its organization's public VIP address, but the internal server does not respond. An external client succeeds. The design requires same-LAN loopback access. What should be checked?
- Add the public VIP to the WAN-to-server rule and reuse that rule for internal-origin clients accessing the same external address.
- Change the public DNS record to the server's private IP for all internet users to make loopback routing easier.
- Enable source NAT on the existing LAN-to-internet policy for every destination, assuming the public VIP will then match the same route.
- Use the appropriate LAN-to-VIP hairpin rule with correct DNAT and necessary return-path SNAT for same-LAN clients.
Explanation
Correct Answer
D:An external WAN-to-VIP rule need not match a new connection originating on the LAN. To support internal access to the public VIP, inspect whether the LAN ingress matches a suitable policy that targets the VIP, whether destination translation occurs, and whether source NAT is required to keep replies on the FortiGate rather than directly returning from the server. Capture both directions and test a new connection without broadly exposing the server.
Incorrect Answers
A:An external-source policy does not necessarily match a LAN-originated hairpin packet or establish the needed internal translation/return path. The effective local-side VIP policy and session NAT must be correct for loopback.
B:A global private-address DNS change could break legitimate remote access. Internal split DNS may be an option, but the actual requirement should be evaluated without disrupting the public service. Changing external DNS to a private address would break internet clients and not repair how internal clients reach the published VIP.
C:Broad outbound SNAT is not sufficient to create a LAN-to-public-VIP DNAT policy and symmetric return behavior. The inside client must match an appropriate VIP/forwarding rule and server replies must traverse the tracked session.
Question 217
Unmanaged guest tablets cannot receive the enterprise deep-inspection CA. The guest network still requires web safety controls and privacy compliance. What is a defensible design?
- Apply deep-inspection CA trust through a captive portal certificate warning acknowledgement and assume this authorizes payload decryption for guests.
- Force deep inspection without client trust and bypass every browser certificate warning through application settings.
- Apply guest certificate-only inspection with supported web/DNS protections and explicit limits where TLS decryption is not authorized.
- Apply only category-based web filtering on a general internet Accept policy and assume encrypted file malware will still be inspected as before.
Explanation
Correct Answer
C:Unmanaged guests may lack an enterprise root CA for deep inspection; avoid forcing untrusted certificate injection and apply supported metadata/domain controls and a clear reduced-visibility policy. Unmanaged guest devices may not trust an enterprise deep-inspection CA, so evaluate appropriate certificate-level web controls, DNS filtering or other supported safeguards with privacy constraints. Verify permitted and blocked categories without forcing endpoint-wide trust distribution on guests.
Incorrect Answers
A:A browser warning acknowledgement is not appropriate enterprise trust provisioning or a privacy authorization basis. Without managed endpoint trust, deep inspection may break sessions; use supported narrower controls and state the residual visibility limit.
B:Broken trust can interrupt legitimate guest use, and bypassing warnings creates security risk. Use compatible certificate-level visibility, DNS or web controls and explicitly justified restrictions instead of forced untrusted TLS interception.
D:Category decisions can reduce risky site access but cannot provide plaintext file scanning if payload decryption is excluded. A guest policy needs a supported inspection mode with documented privacy and threat-detection limitations.
Question 218
Two hosts share the same directly connected /24 behind port4. An engineer proposes adding a static route for their subnet via the upstream ISP. What should be examined?
- Use the connected port4 /24 path and check ARP and physical link; do not route the local subnet via ISP.
- Inspect route-distance values and add a lower-distance static route for the locally connected port4 /24 through the ISP next hop.
- Lower the distance of the ISP default route to supersede the interface's connected subnet reachability.
- Review interzone firewall-policy permits and add a broad LAN-to-LAN ACCEPT rule before checking whether port4 resolves the destination host MAC.
Explanation
Correct Answer
A:A connected interface supplies the directly attached network route; a failed same-subnet conversation calls for VLAN, ARP, host and policy checks before inventing a redundant static route. For the two hosts on the same directly connected /24, FortiGate's connected route already describes that subnet and direct L2 reachability. Diagnose ARP and local path rather than adding an ISP-facing static route that would misdirect traffic.
Incorrect Answers
B:FortiOS already has an interface-connected path to the subnet directly attached to port4. A static next hop at the upstream provider is not a substitute for link and ARP reachability to local hosts; it can also send local destinations to the wrong segment. Confirm connected route and L2 neighbor resolution.
C:A default route does not normally win a more specific connected prefix. Verify the interface's network and local L2 access rather than treating a default as the first diagnostic target.
D:Policies determine permitted forwarding but cannot supply the missing ARP and connected-link information for a directly attached destination. A broad interzone permit also creates unrelated exposure. Validate port4 subnet, link and host ARP first, then review a necessary policy only if it actually applies.
Question 219
A provider firewall allows data traffic for a site-to-site IPsec deployment but blocks the initial IKE UDP/500 packets. The FortiOS 7.6.0 IKEv2 peers are explicitly configured for UDP transport rather than the supported Auto/TCP fallback, and the branch is behind NAT. Which transport and stateful mapping path must be tested before changing the security proposals?
- Open ESP protocol 50 to the VPN peer but leave IKE UDP/500 and NAT traversal UDP/4500 filtered on the upstream stateful router despite the tunnel requiring those negotiations.
- Open outbound UDP/4500 for the NATed IPsec peer but leave initial UDP/500 IKE negotiations blocked at the provider boundary.
- Review the FortiOS 7.6.0 IPsec-over-TCP transport option and enable TCP transport only on the branch peer, leaving the remote and upstream policies unchanged.
- Test both directions of IKE UDP/500 plus UDP/4500 NAT traversal and stateful provider mappings before changing mutually accepted cryptographic proposals or protected selectors.
Explanation
Correct Answer
D:FortiOS IPsec commonly needs UDP 500 for initial IKE and UDP 4500 for NAT-T, with ESP handling as applicable; verify the actual upstream filters and encapsulation. IKE requires its own reachable negotiation path, ordinarily UDP/500 and NAT-T UDP/4500 where NAT is present. Confirm the upstream firewall and NAT mapping permit the actual IKE exchange before changing cryptographic proposals or phase-two selectors.
Incorrect Answers
A:ESP protocol 50 carries unencapsulated IPsec data, not the full UDP IKE negotiation or NAT-T path. Verify both directions of UDP/500 and UDP/4500 and their upstream state translations; changing an ESP-only firewall rule will not restore the blocked negotiation.
B:NAT-T handles encapsulated traffic, but the scenario explicitly says the initial IKE UDP/500 exchange is blocked. Enabling only the later NAT-T port does not prove the peer can negotiate its expected IKE path.
C:FortiOS 7.6.0 supports an IKEv2 TCP encapsulation option and Auto fallback from UDP in compatible deployments, so a jointly approved transport migration can be a legitimate alternative to provider restrictions. However, changing only one branch peer does not establish mutual transport support or upstream TCP-port reachability. The actual case specifies UDP-only peer configuration, making UDP/500 initiation and NAT-T UDP/4500 mapping the first path to diagnose.
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.