Which action will help the administrator to quickly identify the underlying problem?

Users have reported several application VMs are performing very slowly. The system administrator was requested to find out the source of the problem on both VMs and/or ESXi hosts level. vRealize Operations has not been configured with Application Remote Collector.

Which action will help the administrator to quickly identify the underlying problem?
A . Under Inventory, select Manage Agent, then select the VMs, and run Remote Checks on ICMP, HTTP checks.
B . Under Report, use Configuration Report – Virtual Machines to list down possible changes that have occurred.
C . Under Administration, choose Configuration, select Object Relationships, and then identify the VMs and ESXi hosts relationship to generate a correlation of the metric, and finally, isolate the issue.
D . Under Dashboard, choose the out-of-the-box Performance dashboards that displays contention on both VMs and ESXi hosts.

View Answer

Answer: D

Explanation:

According to the vRealize Operations User Guide1, one of the best ways to quickly identify the underlying problem of slow application VMs is to use the out-of-the-box Performance dashboards that display contention on both VMs and ESXi hosts. These dashboards show the key performance indicators (KPIs) of CPU, memory, disk, and network for the selected objects, and highlight any contention or saturation issues that may affect the performance. The administrator can use these dashboards to drill down into the details of the metrics, alerts, events, and properties of the objects, and isolate the root cause of the problem. The other options are not correct because:

Under Inventory, selecting Manage Agent, then selecting the VMs, and running Remote Checks on ICMP, HTTP checks is not a helpful action, as it only verifies the connectivity and availability of the VMs, but does not provide any information about the performance or contention of the VMs or the ESXi hosts2.

Under Report, using Configuration Report – Virtual Machines to list down possible changes that have occurred is not a helpful action, as it only shows the configuration details of the VMs, such as name, UUID, power state, guest OS, CPU, memory, disk, and network, but does not show any performance or contention metrics or alerts of the VMs or the ESXi hosts3.

Under Administration, choosing Configuration, selecting Object Relationships, and then identifying the VMs and ESXi hosts relationship to generate a correlation of the metric, and finally, isolate the issue is not a helpful action, as it only shows the hierarchical and logical relationships between the objects, such as parent, child, sibling, and peer, but does not show any performance or contention metrics or alerts of the objects4.

References: 1: vRealize Operations User Guide, pages 57-59, 62-

632: vRealize Operations User Guide, pages 69-703: vRealize Operations User Guide, pages 81-824: vRealize Operations User Guide, pages 84-85.