NSE6_FSR-7-3 practice question 5 of 10

An administrator is issuing the following command on a node trying to join a FortiSOAR duster as a standby: csadm ha join-cluster --status active —role secondary --primary-node 10.0.1.160 The node fails to join the cluster. What is the issue?

Full set: 39 questions
Answer options
A: The role value should be worker.
B: The primary node needs to be resolvable via FQDN.
C: The IP address should be for secondary-node Instead of primary-node.
D: The status value should be passive. Correct answer
Correct Answer:
D. The status value should be passive.
Explanation

In a FortiSOAR High Availability (HA) cluster, there is one active primary node and one or more passive secondary (standby) nodes. The command shown is being run on a node attempting to join as a standby. The parameter --status active incorrectly attempts to define this new standby node as active. A joining secondary node must be in a passive state to function correctly as a standby. Therefore, the command fails because the status value is logically incorrect for the node's intended role. The value should be passive.

Why Incorrect

A. The role worker is used for nodes in a distributed (non-HA) architecture, not for a standby node in an HA pair. The role secondary is correct.
B. The --primary-node parameter accepts an IP address. Using an FQDN is not a mandatory requirement for the command to succeed.
C. The command is run on the secondary node and must point to the primary node's IP address using the --primary-node flag to initiate the join.

References

- FortiSOAR 7.2.0 High Availability Guide, "Chapter 2: Configuring a High Availability Cluster > Joining the secondary node(s) to the primary node", Page 10. This guide describes the HA architecture, stating that secondary nodes are passive.

Scroll to Top