VMware 5V0-35.21 VMware vRealize Operations Specialist Exam Practice Test

Answer : B

According to the VMware vRealize Operations User Guide1, business intent is a feature that allows the administrator to define the desired state and behavior of the clusters and hosts in the environment based on business objectives and constraints. Business intent can be used to optimize the placement and balance of workloads across clusters and hosts, as well as to enforce license compliance and availability requirements.

One of the types of business intent that can be configured in vRealize Operations is Business Intent - Clusters. This type of business intent allows the administrator to assign tags to clusters and virtual machines, and then create rules that match the tags to ensure that the virtual machines are placed on the appropriate clusters. For example, the administrator can tag two clusters as Windows and two clusters as Linux, and then tag the virtual machines accordingly. Then, the administrator can create rules that match the Windows tag and the Linux tag, and set the enforcement mode to Mandatory. This will ensure that the Windows workloads only run on the Windows clusters, and the Linux workloads only run on the Linux clusters.

Therefore, the correct answer is B. Business Intent - Clusters, as this is the type of business intent that should be configured by the administrator to achieve the goal of ensuring the workloads only run on their assigned nodes.References:

1: VMware vRealize Operations User Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-user-guide.pdf, page 49-51, 54-55

Answer : B

The alert action that the administrator should take to stop the alert from triggering again, unless the problem occurs in the future, is to cancel the alert. Canceling the alert removes the alert from the active alerts list and stops the alert from affecting the state of the object. However, canceling the alert does not resolve the underlying conditions that triggered the alert. Therefore, the administrator should only cancel the alert after investigating and resolving the problem. If the problem occurs again in the future, the alert will be triggered again. To cancel an alert, the administrator can select the alert in the alerts list, click Actions, and click Cancel Alert. Alternatively, the administrator can open the alert details, click Actions, and click Cancel Alert.References:Monitoring Alerts in vRealize Operations Manager;User Scenario: Respond to an Alert in the Health Alert List

Answer : C

The scoreboard widget configuration option that possibly caused this problem is Self Provider set to On. The Self Provider option determines whether the widget shows metrics of the objects selected during editing of the widget or selected on another widget. When the Self Provider option is set to On, the widget shows metrics of the objects selected during editing of the widget. When the Self Provider option is set to Off, the widget shows metrics of the objects selected on another widget. Therefore, if the administrator wants to enable a custom metric configuration file to a scoreboard widget in a dashboard, and the custom metrics are defined for a specific object type, the administrator should set the Self Provider option to Off and select the appropriate object type on another widget. Otherwise, the scoreboard widget will not show the new metrics at all, because the custom metric configuration file will not match the object type selected during editing of the widget.References:How the Scoreboard Widget and Configuration Options Work;Solved: How to configure Generic Scoreboard widget to interact with...

Answer : B

According to the vRealize Operations Cluster Management guide1, the Association Member Status indicates the state of the association between the remote collector nodes and the master node in a multisite deployment. The valid statuses are:

Active: The remote collector node is connected to the master node and is sending data.

Inactive: The remote collector node is not connected to the master node and is not sending data.

Unreachable: The master node cannot reach the remote collector node due to network issues or node failure.

The Asymmetric status is not a valid status for the Association Member Status. It is a valid status for the Cluster Status, which indicates the state of the cluster nodes in a single site deployment.The Asymmetric status means that the cluster nodes are not in sync and have different configurations or versions1.References:1: vRealize Operations Cluster Management guide, pages 3-4.

Answer : A

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''.

Answer : B, C, D

The Troubleshooting Workbench is a feature in vRealize Operations that helps you perform advanced troubleshooting tasks on an alert or an object. You can look for potential evidences of a problem within a specific scope and time range. The potential evidences are based on three types of data: Alerts, Events, and Property Changes. Alerts show the active and inactive alerts that are related to the object or its peers. Events show the events that are based on a change in the metrics, such as spikes, drops, or anomalies. Property Changes show the changes in the configuration or properties of the object or its peers, such as CPU, memory, or disk allocation. These types of data help you identify the root cause of the issue and take corrective actions. Symptoms and Anomalous Metrics are not considered as potential evidence in the Troubleshooting Workbench, although they may be used to trigger alerts or events. Logs are not displayed in the Troubleshooting Workbench, but they can be accessed from the Logs tab of the object.References:Discovering Potential Evidences Using the Troubleshooting Workbench,Solving Real Problems with vRealize Operations Troubleshooting Workbench,Troubleshooting Workbench Home Page,vROps 8.0 Troubleshooting Workbench and Blue Medora

Answer : D

According to the VMware vRealize Operations Install and Configure Guide1, when upgrading the vRealize Operations cluster via the Administration UI, the cluster status should change from offline to online after the upgrade process is completed. However, if the cluster status remains offline or fails during the upgrade, the administrator can use the Finish Installation option to resume the upgrade process. The Finish Installation option attempts to bring the cluster online and complete the upgrade. The administrator can monitor the progress of the upgrade from the Administration UI or the Cluster Management page.

The other options are not suitable for managing this problem and continuing the installation process. The Rollback Installation option is used to revert the cluster to the previous version of vRealize Operations, not to resume the upgrade process. The Rollback Installation option is only available if the cluster is online and the upgrade has failed. The administrator should not manually take the cluster offline, as this would interrupt the upgrade process and cause data loss or corruption.References:

1: VMware vRealize Operations Install and Configure Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-installation-and-configuration-guide.pdf, page 54-55, 58-59