FCSS_NST_SE-7.6 Online Practice Questions

Explanation:
Intermittent behavior (working sometimes, failing others) points to resource or connectivity fluctuations rather than static misconfigurations.
B. Check that FortiGate is not entering conserve mode:
Reason: When FortiGate enters Conserve Mode (due to high memory usage), it changes its inspection behavior to save resources. Depending on the av-failopen setting, it may either bypass inspection (allowing blocked sites) or drop traffic (blocking valid sites) temporarily until memory recovers. This flapping between states causes intermittent filtering issues.
D. Check that the communication between FortiGate and FortiGuard is stable:
Reason: The Web Filter engine relies on real-time queries to the FortiGuard Distribution Network (FDN) to categorize URLs that are not in the local cache. If the internet connection or the specific path to FortiGuard is unstable (packet loss, latency), queries will time out. This results in "Rating Errors," which can block or allow traffic unpredictably based on the "Allow websites when a rating error occurs" setting.
Why other options are incorrect:
A: A mismatch in inspection mode (e.g., Profile set to Proxy, Policy set to Flow) is a static configuration error. It would typically result in the profile not being selectable or consistently failing/not applying, rather than working intermittently.
C: If the wrong port is mapped (e.g., HTTP on 8080 is not mapped), the inspection engine will consistently ignore traffic on that port. It would not be intermittent.
Reference: FortiGate Security 7.6 Study Guide (Web Filter): "If the connection to FortiGuard is unstable, users may experience delays or rating errors... Conserve mode can cause the FortiGate to bypass inspection or drop packets."

Explanation:
The administrator is running a packet sniffer with the filter 'udp port 500 or udp port 4500 or esp'. The result is "no output," even though the VPN is attempting to establish (failing). A. The VPN is configured to use IKE over TCP:
Standard IPsec IKE negotiation uses UDP port 500 (IKE) and UDP port 4500 (NAT-T). However, if IKEv2 over TCP (RFC 8229) or Fortinet's proprietary IKE over TCP is configured (often used to bypass firewalls that block UDP), the traffic will use TCP (often port 4500 or 443).
The sniffer filter explicitly looks for udp or esp (IP Protocol 50).
If the traffic is encapsulated in TCP, it matches tcp protocol, not udp or esp (raw ESP).
Therefore, the sniffer sees zero packets matching the filter.
Why other options are incorrect:
B: esp is a valid argument for diagnose sniffer packet. It is equivalent to filtering for IP protocol 50.
C: If the ISP were blocking traffic, the sniffer (running on the local FortiGate) would still see the outbound packets generated by the FortiGate trying to initiate the connection. "No output" implies the local device isn't even generating packets matching that filter.
D: Mismatched IKE versions would still generate IKE negotiation packets (proposals/errors) that would be captured by the sniffer.
Reference: FortiGate Security 7.6 Study Guide (IPsec VPN): "IKEv2 over TCP is available for environments where UDP 500/4500 is blocked. When enabled, IKE and ESP packets are encapsulated in TCP headers."