From the FortiGate Integration lesson, the Study Guide explicitly states:
"The quarantine daemon is involved in submitting files to FortiSandbox." From the Lab Guide (Exercise 3 - Using FortiGate Diagnostics), the following is explicitly documented:
"Enter the following commands to enable debugging for the quarantine daemon: diagnose debug application quarantine -1 diagnose debug enable"
"Use the following CLI debug command to diagnose the connection and file transfer issue between HQ-FGT-1 and HQ-FSA-1: diagnose debug application quarantine -1" This command enables real-time debug output for the quarantine daemon on FortiGate, which is specifically responsible for submitting files to FortiSandbox and receiving verdicts. Option B clears the analytics cache rather than providing diagnostic information, and the other options relate to different functions entirely.

From the Deployment and System Settings lesson, the Study Guide explicitly states:
"Initial port1 IP configuration must be performed from the console, using the commands shown on this slide. If your management computer is on a separate subnet from FortiSandbox, you must specify a gateway address using the commands shown on this slide." The two required commands are:
set port1-ip <IP address> - to assign the IP address to port1 for GUI access set default-gw <IP Address> - to configure the default gateway so the management computer can reach FortiSandbox from a different subnet Option B (set api-port port1) is for API access configuration, and Option C (set admin-port port1) is not a valid FortiSandbox CLI command for this purpose.

From the Scanning and Rating Components lesson, the Study Guide explicitly states:
"VM images are downloaded from FortiGuard, using port1. So, you must ensure FortiSandbox has a default route and internet connectivity for port1." The exhibit confirms this - the test-network output shows:
System DNS resolve: Failed for both bing.com and fsavm.fortinet.net
fsavm.fortinet.net is the FortiGuard VM image download server
This DNS failure on the system side (port1) confirms there is no internet connectivity on port1, preventing VM image downloads. Note that port3 internet shows "Warning: VM to access internet: Disabled" - but port3 is only for VM sandboxing traffic, not for downloading VM images.

From the FortiWeb Integration lesson, the Study Guide explicitly states:
"You can configure FortiSandbox file submission in a file security policy. Any files not detected by the FortiGuard antivirus engine will be uploaded to FortiSandbox."
"You can configure FortiWeb to send attachments to FortiSandbox for additional scans to detect advanced persistent threats or zero-day attacks." From the Lab Guide (Exercise 1 - FortiWeb Integration):
"Click Web Protection > Input Validation > File Security. In the File Security Policy section, click Create New. Configure Send Files to FortiSandbox: Enabled." This confirms that File Security (Option A) is the correct location on FortiWeb to configure FortiSandbox file submission settings.

From the Deployment and System Settings lesson, the Study Guide states:
"The test-network command checks FortiGuard services as its last set of validation tests. These include the FortiGuard distribution network (FDN) accessibility, FDN contract expiration, web filtering service, and the community cloud service. All these FortiGuard services should be reachable and valid for FortiSandbox to be effective."
"The diagnose-debug fdn command provides details around FortiSandbox and the FortiGuard Distribution Network (FDN) communication and updates." FortiGuard Distribution Network (FDN) communication requires TCP/443 for HTTPS-based update and licensing communication. The current firewall rules allow TCP/4443 (API/management), UDP/8888 (FortiGuard queries), and UDP/53 (DNS), but TCP/443 is missing - which is the standard port required for FortiGuard FDN connectivity and license validation.