FCP_FSA_AD-5.0 Exam Dumps - FCP - FortiSandbox 5.0 Administrator

The Study Guide states that in an HA cluster, “As well as normal scanning duties, the primary node also manages the cluster, distributes jobs, and gathers the verdicts.” It also says that “The worker nodes provide load balancing. The primary node distributes scan jobs to the worker nodes.”

From those official statements, the primary node is not just a coordinator. It also performs normal scanning duties itself, while distributing scan jobs across worker nodes for load balancing. That rules out A, because the secondary node is for failover, not normal job distribution. It rules out C, because the primary is not restricted to itself only. It also rules out D, because the primary can still perform scanning duties and is not limited to sending all jobs only to workers. Therefore, when the primary receives MTA jobs, the correct behavior is that it distributes the MTA jobs to itself or to worker nodes .

The correct answer is B. 50 seconds . The Study Guide explicitly states: “FortiGate holds the file while waiting for a verdict from FortiSandbox… The default file inspection timeout, and maximum, is 50 seconds.” This is the clearest direct statement for the default timeout used with inline scanning mode on FortiGate.

The Lab Guide confirms the same design limit from the operational side. During the inline scanning exercise, it notes: “Because of the inline scanning time-out limit (maximum of 50 seconds), it ' s not recommended to submit files for VM inspection.” That reinforces that inline scanning is designed for quick decision phases such as active content, community cloud, antivirus, and static analysis, not long VM dynamic analysis jobs. Therefore, options A, C, and D are incorrect because they are far above the documented inline inspection limit. The default FortiGate inline scanning timeout is 50 seconds .

From the High Availability and Management lesson, the Study Guide states:

" You must configure the HA group name, password, and the cluster virtual IP. The worker nodes provide load balancing. The primary node distributes scan jobs to the worker nodes. "

" You must configure the HA group name, password, and the virtual IP only on the primary node... Devices will interact with the cluster using this virtual IP. "

From the exhibit topology:

Cluster Virtual IP address = 10.25.1.50

Primary Node port1 = 10.25.1.30

Secondary Node port1 = 10.25.1.40

Worker Node port1 = 10.75.1.10

The worker node must be configured to point to the Cluster Virtual IP (10.25.1.50) , not the individual primary node IP. This is because worker nodes join the cluster by connecting to the cluster virtual IP address.

Therefore the correct command is: hc-worker -a -sI0.25.1.50 -p <</b> password >