5V0-35.21 Exam Dumps : VMware vRealize Operations Specialist

Data nodes are the type of node in a vRealize Operations (vROps) design that allow an administrator to scale out vROps to monitor very large environments. Data nodes are additional nodes that have all the vROps services installed, such as UI, Controller, Analytics, Collector, and Persistence. Data nodes perform data collection and analysis, and increase the capacity and performance of the vROps cluster. Data nodes can be added or removed as needed to adjust to the changing workload and environment size. Remote collectors are not a type of node in a vROps design, but a separate component that can be deployed to collect data from remote sources and send it to the vROps cluster. Remote collectors do not store data or perform analysis, and do not increase the capacity or performance of the vROps cluster. Replica Primary nodes and Primary nodes are not the type of node that allow an administrator to scale out vROps to monitor very large environments, but the type of node that provide high availability and continuous availability for the vROps cluster. Replica Primary nodes and Primary nodes contain critical services that cannot be replicated across all cluster nodes, such as Global xDB, NTP server, and GemFire locator. Replica Primary nodes and Primary nodes do not perform data collection and analysis, and do not increase the capacity or performance of the vROps cluster. References: About vRealize Operations Cluster Nodes, section “About vRealize Operations Cluster Nodes”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.

Remote Collector nodes are a type of vRealize Operations nodes that only gather objects for the inventory, without storing data or performing analysis. Remote Collector nodes can navigate firewalls, interface with remote data sources, reduce the bandwidth across data centers, or reduce the load on the vRealize Operations analytics cluster1. Remote Collector nodes are not part of the analytics cluster, but they are members of the vRealize Operations cluster2.

Data nodes, Primary Replica nodes, and Primary nodes are all part of the analytics cluster and they store data and perform analysis. Data nodes have adapters installed and perform collection and analysis. Primary Replica nodes are replicas of the Primary nodes and provide high availability or continuous availability. Primary nodes are the initial and required nodes in vRealize Operations and manage all other nodes2. References:

• Additional Operations from the Manage Telegraf Agents Page
• About vRealize Operations Cluster Nodes

 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.