The correct answer is A .
The debug flow shows:
* traffic is going to TCP port 211
* FortiGate logs run helper-ftp(dir=original)
The study guide explains exactly what that message means:
"In this example, the run helper-ftp message indicates that the FTP session helper is being used." Under normal proxy-based inspection, protocol handling is controlled by Protocol Options . The FortiOS administration guide states:
"Protocol port mapping only works with proxy-based inspection." and "The ports can be modified to inspect any port with flowing traffic." So if the policy is configured for proxy-based inspection but the debug still shows the FTP session helper on port 211, the most likely explanation is that the FTP protocol mapping in Protocol Options is broad enough to match unexpectedly, such as being mapped to Any . That would cause FortiGate to identify the traffic as FTP and invoke the helper.
Why the other options are wrong:
* B is wrong because SSL deep inspection is unrelated to this debug. The traffic shown is plain TCP/211
, and the key message is about the FTP helper , not SSL decryption.
* C is wrong because if FTP had not been mapped to port 211, FortiGate would be less likely to treat this traffic as FTP. The observed run helper-ftp indicates FTP handling is being triggered.
* D is wrong because low-memory conserve behavior would typically cause inspection bypass or blocking behavior, not specifically the run helper-ftp message. The study guide's helper example ties this message to session-helper use, not memory shortage.
So the verified answer is: A .

The correct answers are A and D .
The Network Security Support Engineer 7.6 Study Guide explains that automation stitches consist of a trigger and one or more actions , and that they can detect events such as high CPU and conserve mode across the Security Fabric The FortiOS administration guide then gives the exact practical example for A :
"Automation stitches can be created to run a CLI script and send an email message when memory or CPU usage exceeds specified thresholds." It also shows examples where the email body contains the script output using:
%%results%%
That directly confirms A .
For D , the FortiOS administration guide states:
"The URI and HTTP body can use parameters from logs or previous action results." It also explains the execution model:
"The stitch Action execution can be set to either Sequential or Parallel. In sequential execution actions will execute one after another with a delay (if specified). ... In parallel execution all actions will execute immediately when the stitch is triggered." A concrete example shows a second action using the output of the first action:
"This string for the body text includes the results from the preceding CLI script action." with Body=%%results%%...
That confirms D .
Why the other options are wrong:
* B is wrong because automation stitches can be triggered by IPS events, but the documentation does not describe them as modifying packet headers or payloads. Instead, they perform actions such as email, CLI script, webhook, quarantine, and similar automated responses
* C is wrong because delay is associated with sequential execution, not parallel execution. The guide explicitly says: "A delay can be added before an action if Sequential action execution is used." So the verified answers are: A, D .

The correct answer is C .
The exhibit shows the neighbor state as Connect in the State/PfxRcd column. The study guide explains the BGP states exactly as follows:
* "Connect: Waiting for a successful three-way TCP connection"
* "OpenSent: Waiting for an OPEN message from the peer"
* "Established: Peers have successfully exchanged OPEN and keepalive messages" Because the router is still in Connect state, the TCP three-way handshake has not completed yet . In practical terms, the local router has sent the TCP SYN but has not successfully received the SYN/ACK needed to complete the handshake . That is why C is correct.
Why the other options are wrong:
* A is wrong because the message counters alone do not prove that the neighbor is unreachable. The study guide says the State/PfxRcd field shows the BGP state when the session is not established, and here that state is specifically Connect
* B is wrong because waiting for an OPEN message happens in OpenSent , not Connect
* D is not the best answer for this output. The study guide ties the displayed state directly to the protocol phase: Connect means the device is still waiting for a successful TCP handshake So the verified answer is: C .

The session output includes the flags:
* state=redir local may_dirty ...
* npu_state=00000000
* offload=0/0
The 7.6 study guide explains these flags directly:
* local = "Session is to/from local stack"
* redir = "Session is being processed by an application layer proxy"
* may_dirty = "Session is allowed by a firewall policy"
This makes C correct, because the local flag means the session either originates from FortiGate or terminates on FortiGate . The FortiOS administration guide states the same meaning: "Session is originated from or destined for local stack." This also makes A correct. The redir flag means the session is handled by an application-layer proxy .
FortiOS documents explain that proxy-based inspection buffers traffic on the FortiGate and inspects it there, and that proxy-based processing is CPU and memory-intensive Since the session also shows no NPU offload (npu_state=00000000, offload=0/0), this traffic is being handled in software/CPU, not by the NPU.
Why the other options are wrong:
* B is wrong because the redir flag proves the session is not passing without inspection; it is being processed by an application-layer proxy
* D is wrong because there is no authentication flag in this session. In Fortinet examples of captive portal/authentication-related sessions, the session state includes auth or authed flags. The study guide shows: "Any session for traffic coming from an authenticated user contains the authed flag." This exhibit does not show auth or authed, so there is no basis to conclude the client was redirected to a captive portal for authentication.