The correct answer is B .
The study guide explicitly states: "IKE version 2 does not interoperate with IKE version 1, but they share enough of the header format that both versions can unambiguously operate over the same UDP port." That directly proves B .
Why the other options are wrong:
* A is wrong because the study guide shows authentication methods as Asymmetric for IKEv2 and Symmetric for IKEv1
* C is wrong because the study guide does not say they use the same TCP port; instead, it specifically says they can operate over the same UDP port
* D is wrong because the study guide states: "IKEv2 does not use the concept of phase 1 or phase 2" , even though FortiOS CLI/GUI still uses those terms for configuration purposes

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."

The correct answer is D. IKE_AUTH .
The study guide explicitly states:
"IKE_Auth exchange:
* Performs the mutual authentication of two IKE endpoints.
* Configures settings like IP/mask, DNS, and so on.
* Sets up the piggyback of a child SA. Negotiates IP flow and security settings for the IPsec SA." It also says:
"By default, a piggyback child (IPsec) SA is negotiated along with the IKEv2 SA during IKE_AUTH. If additional IPsec SAs are needed ... they are negotiated during subsequent CREATE_CHILD_SA exchanges." Why the other options are wrong:
* A. IKE_SA_INIT is incorrect because this exchange negotiates the security settings to protect the IKE traffic, not the first CHILD_SA.
* B. INFORMATIONAL is incorrect because it is used to convey control messages between IKE endpoints.
* C. CREATE_CHILD_SA is incorrect for the first CHILD_SA, because it is used to create new additional child SAs or rekey existing ones after the initial exchange.