How should the system administrator resolve this availability issue within vRealize Operations Manager?

Due to multiple hardware failures, several virtual machines were corrupted and are being restored from a recent backup. One of the corrupted virtual machines was the primary replica node of a large production vRealize Operations Manager cluster.

How should the system administrator resolve this availability issue within vRealize Operations Manager?
A . Remove the corrupted node, and then disable and re-enable vRealize Operations Manager High Availability to reassign the primary replica role to another existing node in the cluster.
B . Deploy a new vRealize Operations Manager node, and then add it to the existing cluster.
C . Clone an existing primary vRealize Operations Manager node, and then add it into the vRealize Operations Manager cluster.
D . Ask the backup administrator to restore the corrupted primary replica node, and then refresh the nodes from the vRealize Operations Manager administrator interface.

View Answer

Answer: A

Explanation:

Removing the corrupted node, and then disabling and re-enabling vRealize Operations Manager High Availability to reassign the primary replica role to another existing node in the cluster is the correct way to resolve the availability issue within vRealize Operations Manager. This method ensures that the cluster can continue to operate with high availability and continuous availability, as the primary replica node is responsible for providing critical services that cannot be replicated across all cluster nodes, such as Global xDB, NTP server, and GemFire locator. By removing the corrupted node, the administrator can prevent any further issues or conflicts with the cluster configuration. By disabling and re-enabling vRealize Operations Manager High Availability, the administrator can trigger the cluster to select a new primary replica node from the existing data nodes, and synchronize the data and services with the primary node. Deploying a new vRealize Operations Manager node, and then adding it to the existing cluster is not a valid option, as it does not address the primary replica role assignment, and may cause additional problems with the cluster configuration. Cloning an existing primary vRealize Operations Manager node, and then adding it into the vRealize Operations Manager cluster is not a feasible option, as it may result in duplicate node IDs, IP addresses, and hostnames, and may cause conflicts with the cluster configuration. Asking the backup administrator to restore the corrupted primary replica node, and then refreshing the nodes from the vRealize

Operations Manager administrator interface is not a reliable option, as it may take a long time to restore the node, and may not guarantee the consistency and integrity of the data and services on the node.

References: Remove a Node from a Cluster, section “Remove a Node from a Cluster”. About vRealize Operations Cluster Nodes, section “About vRealize Operations Cluster Nodes”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.