The administrator needs to add an additional data node to the existing vRealize Operations cluster. Which step needs to be taken?

Question

Options

• AShutdown and clone one of the existing data nodes.
• BDeploy a new data node from the Administration UI.
• CDeploy a new virtual appliance from an OVF file.
• DEnable High Availability in the Administration UI.

• A
  13% (4)
• B
  3% (1)
• C
  77% (24)
• D
  6% (2)

Explanation

Adding a new data node to a vRealize Operations cluster requires deploying a fresh virtual appliance from an OVF/OVA file, then joining it to the cluster through the Administration UI - this is the standard, documented expansion process VMware prescribes.

Why the distractors are wrong:

• A - Cloning an existing node would copy its identity, certificates, and cluster membership data, causing conflicts rather than adding clean capacity.
• B - The Administration UI is used to configure and expand the cluster after deployment, not to deploy the underlying virtual appliance itself; the VM must exist before the UI can see it.
• D - High Availability is a separate feature that adds a replica node for failover, not a data node for analytics capacity - it doesn't expand the cluster's data processing capability.

Memory tip: Think of it as a two-step handshake - first deploy (OVF), then join (Admin UI). The OVF file creates the VM; the UI brings it into the cluster. You can't skip step one.

No community discussion yet for this question.