You attempt to add a new ONTAP 9.7 node to a NetApp cluster running ONTAP 9.8 and it fails. Which nondisruptive approaches can be used to add the new node?

You attempt to add a new ONTAP 9.7 node to a NetApp cluster running ONTAP 9.8 and it fails. Which nondisruptive approaches can be used to add the new node?

• A. Upgrade the new node from ONTAP 9.7 to ONTAP 9.8.
• B. Add the node using the -allow-mixed-version- parameter.
• C. Both upgrading to 9.8 and using -allow-mixed-version- parameter.
• D. Reinstall the node with ONTAP 9.8

Answer: (C)

Adding a new node to a running ONTAP cluster without disruption hinges on version compatibility. If the cluster is at ONTAP 9.8 and the new node is at 9.7, you can still integrate it nondisruptively by either upgrading the node to 9.8 or by allowing mixed-version operation during the add with the -allow-mixed-version- parameter. Upgrading the node first brings all cluster nodes to the same version, which is a clean, fully supported state for ongoing operations. Using the -allow-mixed-version- parameter lets the node join the 9.8 cluster even though it runs 9.7, creating a temporary mixed-version cluster; afterward, you upgrade the node to 9.8 to restore a homogeneous state. Both approaches enable nondisruptive expansion; the choice depends on deployment policy or preference. Be aware that mixed-version operation may limit certain features, so verify any version-specific restrictions in the compatibility guide.

Adding a new node to a running ONTAP cluster without disruption hinges on version compatibility. If the cluster is at ONTAP 9.8 and the new node is at 9.7, you can still integrate it nondisruptively by either upgrading the node to 9.8 or by allowing mixed-version operation during the add with the -allow-mixed-version- parameter. Upgrading the node first brings all cluster nodes to the same version, which is a clean, fully supported state for ongoing operations. Using the -allow-mixed-version- parameter lets the node join the 9.8 cluster even though it runs 9.7, creating a temporary mixed-version cluster; afterward, you upgrade the node to 9.8 to restore a homogeneous state. Both approaches enable nondisruptive expansion; the choice depends on deployment policy or preference. Be aware that mixed-version operation may limit certain features, so verify any version-specific restrictions in the compatibility guide.