5V0-35.21 Exam Dumps : VMware vRealize Operations Specialist

To compare the cost of running workloads hosted with two different custom cloud providers, the administrator needs to create two new pricing cards in vRealize Operations. A pricing card is a template that defines the cost of cloud resources, such as compute, storage, network, and services. By creating two pricing cards, one for each custom cloud provider, the administrator can specify the prices for each resource type and apply discounts or markups as needed. The administrator can then use the pricing cards to run a what-if analysis and compare the cost of migrating or scaling workloads to the custom cloud providers. The other options are not correct for comparing the cost of running workloads hosted with two different custom cloud providers. Adding custom cloud providers as cloud accounts is not possible, as vRealize Operations only supports adding public cloud accounts, such as AWS, Azure, or Google Cloud. Inputting prices manually when running a what-if analysis is not efficient, as it would require entering the prices for each resource type and workload every time. Adding two custom cloud providers is not a valid option, as it is not clear how the administrator would define the cost of the cloud resources without using pricing cards. References: Create a Pricing Card, Compare the Cost of Running Workloads on Different Cloud Providers, What-If Analysis

 A super metric is a custom metric that you can define using existing metrics and mathematical functions. They allow you to create new metrics that are specific to your environment and can help you gain deeper insights into the performance and health of your infrastructure1. Before enabling a super metric in a policy, you need to associate it to an object type. An object type is a category of objects that share common characteristics, such as hosts, virtual machines, clusters, datastores, etc. By associating a super metric to an object type, you can calculate the super metric for all the objects of that type and display it in the dashboards and reports2. For example, if you create a super metric that calculates the average CPU usage of all the virtual machines in a cluster, you need to associate it to the cluster object type. Then, you can enable the super metric in a policy and apply it to the cluster object or group. This way, you can monitor the average CPU usage of the cluster as a super metric3. References: 1: Configuring Super Metrics 2: Metrics and Properties Details 3: Supercharge Your vRealize Operations with Super Metrics

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