The ‘set nat enable’ command in a FortiGate firewall policy enables Source NAT (SNAT) for outgoing traffic, typically rewriting the source IP to the FortiGate’s interface IP or an IP pool. It does not disable NAT (B), force a specific pool (C), or limit to incoming traffic (D). Exact extract: "The ‘set nat enable’ command in a firewall policy enables Source NAT, rewriting the source IP address of outgoing traffic to the egress interface IP or a configured NAT pool."

TCP is a unicast, connection-oriented protocol that ensures reliable data delivery between two endpoints using sequence numbers and acknowledgments. Multicast, which sends data to multiple recipients, is supported by UDP, not TCP, due to TCP’s requirement for a direct connection. Fortinet devices handle multicast traffic via UDP-based protocols like IGMP or PIM. Exact extract: "TCP is a unicast protocol that establishes a reliable connection between two devices... Multicast traffic, such as streaming or group communications, relies on UDP, as TCP does not support multicast delivery."

HTTP defines standard request methods, including GET (retrieve a resource) and HEAD (retrieve headers only). LIST and RETR are not standard HTTP methods; RETR is used in FTP, and LIST is not a recognized method in either protocol. The original document incorrectly lists only A, omitting C. Exact extract: "HTTP supports several request methods, including GET, HEAD, POST, PUT, DELETE, etc... GET retrieves a resource, while HEAD retrieves only the headers without the body content."

Traffic Logs in FortiGate record all traffic events, including denied packets, with details like source, destination, and policy ID. Security Logs (B) cover UTM events, Event Logs (C) system events, and System Logs (D) hardware or system status, not specifically denied traffic. Exact extract: "Traffic Logs record all packet activity, including allowed and denied traffic, with details such as source/destination IPs, ports, and the firewall policy applied."

Hub-and-spoke IPsec VPN reduces the number of tunnels needed (one per spoke to hub instead of n(n-1)/2 in full mesh), simplifying configuration and routing tables with summarized routes at the hub. It does not inherently provide stronger encryption or require for redundancy (though can be made redundant). Exact extract: I want to have a way to quickly (preferably automated) setup VPN's to my 2 hubs from each spoke. However we do not want/need VPNs between spokes. Hub Configuration: Configure the FortiGate unit as the hub. Set up IPsec VPN tunnels for each spoke. Use preshared keys for authentication. The purpose of this document is to describe the requirements and general information for building a Hub & Spoke architecture using FortiGate-VM on Oracle Cloud ... The remote sites do not need to have connectivity to each other nor does the customer want them to have connectivity to each other. Given these ... This article gives a brief configuration example from one spoke to other spoke using IPsec, through the Hub firewall.