When Fusionlnsight HD is expanded, the new root node password of the host OS does not need to be consistent with the root user password of all nodes in the cluster.

The statement is correct. During the cluster expansion process for Huawei FusionInsight HD, the management software (FusionInsight Manager) prompts the administrator to provide the root credentials (username and password) for each new host being added. The system uses these specific credentials to establish an SSH connection to the new node, install the management agent, and perform necessary configurations. This design allows each host in the cluster to maintain a unique root password, which aligns with security best practices by avoiding the use of a single, shared password across multiple systems.

The alternative, "False," is incorrect. If the statement were false, it would imply that FusionInsight HD mandates a uniform root password for all nodes within the cluster. This is not a requirement of the platform. Such a design would be operationally cumbersome and would represent a significant security vulnerability. The FusionInsight HD architecture is built to manage hosts with individual credentials.

1. Huawei FusionInsight HD 6.5.1 Administrator Guide: In the chapter on "Cluster Management," the section "Expanding a Cluster" details the procedure for "Adding a Host." Step 4 of the procedure explicitly states: "On the displayed Add Host page, enter the host name, IP address, and root password of the host to be added to the cluster..." This step confirms that the password for the new host is provided during the expansion process and is not required to be pre-synchronized with existing nodes.

2. Huawei FusionInsight HD 6.5.1 Software Installation Guide: The chapter "Preparing for Installation," in the section "Preparing Hosts," describes the initial setup for each server. The instructions guide the user to set a root password for each individual host as part of the operating system installation and configuration. There is no mention of a requirement for this password to be consistent across all potential cluster nodes, reinforcing that each node is treated as an entity with its own credentials.