Parallel Path Processing (PPP) in FortiOS refers to the system's ability to evaluate and select among multiple processing paths-often involving dedicated network processors, content processors, or CPU-based workflows-to optimally process packets. The official documentation highlights that the PPP engine dynamically selects which hardware or software path to use for each session based on session characteristics, policy configuration, and traffic type. This dynamic selection results in optimal throughput and resource utilization.
The document specifies that PPP assesses several processing paths in parallel, using decision logic to determine whether a session should be offloaded to specialist hardware (like NP6, CP9, etc.) or stay in the CPU path, ensuring that each packet is handled by the most efficient available method under current load and policy. Hardware and software configurations both influence this outcome, but it is the PPP engine ' s decision-making that defines the optimal path per session.
References:
Fortinet FortiGate Handbook: Parallel Path Processing
Fortinet FortiOS Technical Documentation: Packet Flow and Path Selection

To identify the reason for the lack of prefixes, we must interpret the State/PfxRcd and Up/Down columns in the get router info bgp summary exhibit.
Analyze Neighbor Status:
Neighbor 10.125.0.60: State is OpenSent. This session is not established. It is stuck in the negotiation phase.
Neighbor 100.64.3.1: State is Active. This session is not established. The router is actively trying to initiate a TCP connection.
Neighbor 10.127.0.75:
Up/Down: 02:45:55. This indicates the BGP session has been Up (Established) for almost 3 hours.
State/PfxRcd: 0. This number represents the count of prefixes received. The session is fully established, but the neighbor has sent zero routes.
Determine the Cause:
Since the session with 10.127.0.75 is established, connectivity and handshakes (Options A, B, C) are not the issue for this neighbor.
The fact that it is Up but sending 0 prefixes strongly implies that the neighbor is configured to filter out its routes before sending them to the local FortiGate.
Option D correctly identifies this as a RIB-OUT (Routing Information Base - Outbound) configuration issue on the neighbor (Router 10.127.0.75), which prevents it from advertising its routes.
Reference:
FortiGate Security 7.6 Study Guide (BGP): " In the BGP summary, if the State/PfxRcd shows a number (e.g.,
0), the session is Established. A value of 0 means the peering is up, but no routes have been received, often due to route-map or prefix-list filtering on the remote peer. "

References:
FortiOS Admin Guide: OSPF, Debug Outputs

The correct answer is A . This behavior is dictated by the configuration command set snat-route-change enable shown in Exhibit 1 under config system global.
* Routing Change: By changing the priority of route ID 2 from 10 to 0, it becomes lower than route ID 1 (priority 5). In FortiOS, a lower priority value indicates a more preferred route. Consequently, the active route for the destination changes from port1 to port2 .
* SNAT Implication: The existing session (shown in Exhibit 2) is using Source NAT (SNAT) with the IP address associated with port1 (10.200.1.1). If the traffic were simply switched to port2 , the source IP would be incorrect for that interface and the return traffic would likely fail or be dropped.
* snat-route-change enable: This specific setting instructs the FortiGate on how to handle established SNAT sessions when a routing change occurs that alters the preferred outgoing interface. When enabled, if a route change forces an SNAT session to a new interface, FortiGate flushes (deletes) the session from the session table. This is necessary because a live TCP session cannot survive a change in its source IP address. The client must initiate a new session, which will then be created using the new correct route (port2) and the corresponding new SNAT IP.
If this setting were disabled, the session would likely remain " sticky " to the original interface (port1) until it closed, provided the route still existed. However, the explicit configuration forces the deletion.

The correct answer is C .
The exhibit shows:
* 562 in ESTABLISHED state
* 27 in CLOSE state
* memory_tension_drop=0
* ephemeral=0/131072
According to the study guide, for TCP sessions: "The protocol state in the session table is a two-digit number. For TCP, the first number (from left to right) is related to the server-side state and is 0 when the session is not subject to any inspection (flow or proxy)... The second digit is the client-side state." The same page also shows that value 1 = ESTABLISHED So, if a TCP session is in ESTABLISHED state and there is no inspection , its proto_state is 01 :
* first digit 0 = no inspection
* second digit 1 = ESTABLISHED
That makes C correct. This is also consistent with FortiOS examples showing established TCP sessions with proto=6 proto_state=01 Why the other options are wrong:
* A is wrong because the field that indicates sessions dropped due to low free memory is memory_tension_drop, and in the exhibit it is 0 , not 113. The study guide states: "If there is a lack of free memory, the kernel deletes the oldest sessions. The command shown on this slide displays the number of sessions the kernel deleted because of this mechanism." So 113 is the clash value, not memory-tension drops.
* B is wrong because ephemeral=0/131072 does not mean 131072 ephemeral sessions were recorded.
The study guide explains that FortiGate "sets a hard limit on the maximum number of ephemeral sessions that can exist at the same time in the session table." Therefore:
* 0 = current ephemeral sessions
* 131072 = maximum allowed ephemeral sessions for that model/context
* D is wrong because the study guide says the temporary retention for possible out-of-order packets happens in state value 5 (TIME_WAIT) : "When a session is closed by both the sender and receiver, FortiGate keeps that session in the session table for a few seconds, to allow for any out- of-order packets that might arrive after the FIN/ACK packet. This is the state value 5." But the exhibit shows 27 in CLOSE state , and the same table shows CLOSE = 6 , not TIME_WAIT So the verified answer is C .