VMware Updated 5V0-35.21 Exam Questions and Answers by melina

 To add a custom metric configuration file to a scoreboard widget in a dashboard, the correct process is to create a metric file in XML format, set the scoreboard widget Self Provider to Off, and create a widget interaction with a provider widget. A custom metric configuration file is a file that defines the metrics that the scoreboard widget displays for different object types. The file must be in XML format and follow a specific schema. The file must be uploaded to the vRealize Operations server and selected in the Metric Configuration option of the scoreboard widget. 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 Off, the widget shows metrics of the objects selected on another widget. The widget interaction is a mechanism that allows widgets to communicate with each other and pass data. A provider widget is a widget that provides data to another widget. A receiving widget is a widget that receives data from another widget. To create a widget interaction, the administrator must edit the dashboard and select the provider widget and the receiving widget, and then configure the interaction type and the data to pass. By creating a widget interaction with a provider widget, the administrator can enable the scoreboard widget to display the custom metrics for the objects selected on the provider widget. References: How the Scoreboard Widget and Configuration Options Work; Question on How to Scoreboard Dashboard - Metric Configuration XML - Max & Avg Metric Values; Dashboard widget can set default metric key

A super metric is a mathematical formula that contains one or more metrics or properties for one or more objects. It can be used to create custom metrics that are specific to your environment and can help you gain deeper insights into the performance and health ofyour infrastructure1. Super metrics can be applied to any object type that contains the objects or metrics involved in the formula2.

Option A is a valid super metric, as it calculates the average CPU usage of VMs within a Datacenter, which is an object type that contains VMs as child objects. The formula for this super metric could be something like avg(${this, metric=cpu|usage_average, depth=1}), which means the average of the CPU usage average metric for all the child objects of the current object3.

Option D is also a valid super metric, as it counts the number of Non-Windows VMs in a vSphere cluster, which is an object type that contains VMs as child objects. The formula for this super metric could be something like count(${this, metric=guestfilesystem|osType, depth=1, where=not contains windows}), which means the count of the guest OS type metric for all the child objects of the current object, where the value does not contain the word windows3.

Option B is not a valid super metric, as it involves the difference of CPU utilization for each VM between two defined time stamps, which is not a metric or property that can be used in a super metric formula. Super metrics can only use metrics or properties that are collected by vRealize Operations, not arbitrary time stamps2.

Option C is not a valid super metric, as it involves string operators that are valid to be used with mathematical calculations in a function, which is not a metric or property that can be used in a super metric formula. Super metrics can only use numerical values, not string values, in mathematical calculations2.

Option E is not a valid super metric, as it involves the average SCSI count with disk size of VMs within an ESXi host, which is not a metric or property that can be used in a super metric formula. Super metrics can only use metrics or properties that are available for the object type that the super metric is assigned to, and the SCSI count and disk size are not available for the ESXi host object type2.

References:

• My Top 15 vRealize Operations Super Metrics - VMware Blogs
• Configuring Super Metrics - VMware Docs
• vRealize Operations 8.10 - Create Super Metric - Virtualization Blog

A vROps cluster in a Continuous Availability configuration consists of two fault domains, which are separate physical locations that can tolerate failures of an entire rack or site. The fault domains contain the primary node, the primary replica node, and the data nodes that store and replicate the data and configuration of the cluster. The witness node is deployed in a third location to monitor the network connectivity between the two fault domains and prevent split-brain scenarios, which occur when both fault domains assume the role of the master node due to network isolation1.

When a network outage occurs between the two fault domains, the witness node detects the situation and makes one of the fault domains offline to avoid data inconsistency. The fault domain that can still contact the witness node remains online and continues to function as the master node. The fault domain that cannot contact the witness node goes offline and stops serving requests. The VMs on the offline fault domain are restarted on the online fault domain by the vSphere HA feature1.

When the network outage is resolved and the connectivity between the two fault domains is restored, the vROps cluster will bring the offline fault domain back automatically. The offline fault domain will resync the data and configuration from the online fault domain and resume its normal operations. The administrator does not need to bring the offline fault domain online manually or restart and resync the vROps cluster1.

Therefore, the two events that will occur as a result of the outage are A. The vROps cluster will bring the fault domain back automatically once the network has been restored and D. One fault domain will go offline.

References: 1: About vRealize Operations Continuous Availability

Cloud Accounts are the connections that allow vRealize Operations Manager to collect data from various cloud platforms and services. vRealize Operations Manager supports several types of Cloud Accounts, such as VMware Cloud, Amazon Web Services, Microsoft Azure, Google Cloud, and Kubernetes1. To monitor all supported environments, the administrator can use any combination of these Cloud Accounts, depending on the cloud services that the company is consuming. However, among the options given, only Amazon Web Services (AWS) and VMware Cloud on AWS are valid Cloud Accounts that can be used in vRealize Operations Manager. AWS is the leading public cloud provider that offers a wide range of compute, storage, networking, database, analytics, and other services2. VMware Cloud on AWS is a hybrid cloud service that delivers a consistent VMware environment on the AWS infrastructure, allowing customers to migrate, extend, and modernize their applications3. Both AWS and VMware Cloud on AWS can be integrated with vRealize Operations Manager by configuring the respective Cloud Accounts and providing the necessary credentials and regions45.

Google Cloud, Alibaba Cloud, and IBM Cloud are also popular public cloud providers that offer various cloud services, but they are not supported as Cloud Accounts in vRealize Operations Manager. Therefore, they cannot be used to monitor the environments in vRealize Operations Manager. To monitor these cloud platforms, the administrator might need to use other tools or methods, such as third-party management packs, custom integrations, or external APIs . References:

• Cloud Accounts
• Amazon Web Services
• VMware Cloud on AWS
• Configure an Amazon Web Services Cloud Account in vRealize Operations
• Configure a VMware Cloud on AWS Cloud Account in vRealize Operations
• [Google Cloud Platform Management Pack for vRealize Operations]
• [Alibaba Cloud Monitoring]
• [IBM Cloud Monitoring]