Valid FCP_FSA_AD-5.0 Dumps shared by EduDump.com for Helping Passing FCP_FSA_AD-5.0 Exam! EduDump.com now offer the newest FCP_FSA_AD-5.0 exam dumps, the EduDump.com FCP_FSA_AD-5.0 exam questions have been updated and answers have been corrected get the newest EduDump.com FCP_FSA_AD-5.0 dumps with Test Engine here:
An organization has an existing FortiGate provisioned as a data center firewall (DCFW) that submits inbound files to FortiSandbox for inline scanning. As a result of a network redesign, traffic between the FortiSandbox and the DCFW now passes through an intermediate firewall. Inline scanning is no longer working. While examining the configuration of the intermediate firewall you notice that it is configured to allow traffic on ports TCP/3389, UDP/53, and TCP/443. What must you change for the integration to work? (Choose one answer)
Correct Answer: A
The FortiSandbox 5.0 Administrator Lab Guide explicitly states during the inline scanning configuration: "FortiGate and FortiSandbox communicate through port 4443. Management or API ports grant access through port 4443." In the same exercise, the guide has you enable API access on port2 specifically so inline scanning can function, which confirms that the integration depends on FortiGate reaching FortiSandbox over TCP/4443. In this scenario, the intermediate firewall currently allows TCP/3389, UDP/53, and TCP/443, but not TCP/4443. That is why inline scanning stopped working after the redesign. TCP/443 is not sufficient here because the documented FortiGate-to-FortiSandbox inline communication port is 4443, not standard HTTPS 443. The other ports in the options do not match the inline-scanning communication requirement described in the uploaded lab materials. Therefore, the required fix is to allow FortiGate access to FortiSandbox on TCP/4443.
