Free Practice Questions for VMware 5V0-35.21 Exam

To discover custom application services running on virtual machines, the administrator needs to install the vRealize Operations Service Discovery Management Pack1. This management pack enables service and application discovery using the Service Discovery adapter, which leverages the Telegraf agent to collect data from the end point VMs2. The administrator can configure the Service Discovery adapter to discover predefined and custom applications and services, and view their relationships and metrics in vRealize Operations3. The administrator can also create custom application definitions based on object names, tags, or properties, and import them as XML files. Configuring a white list is not a valid option, as it is used to filter out unwanted services from discovery. References: 1: vRealize Operations Service Discovery Management Pack - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.6/com.vmware.vcom.core.doc/GUID-B9095E9B-7F10-4B2F-95A9-3D54CF5038FF.html)  2: Service and Application Discovery - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.10/com.vmware.vcom.core.doc/GUID-CC683117-D936-432C-B30B-CCCA08E863FB.html)  3: Configure Service and Application Discovery - VMware Docs(https://developer.vmware.com/apis/579/vra-advanced-designer/) : Create Application Definition - VMware Docs : Configure White List - VMware Docs

 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

These two prerequisites are required for integrating vRealize Operations Cloud and vRealize Log Insight Cloud to manage on-premises vSphere environments. vRealize Operations Cloud and vRealize Log Insight Cloud must be enabled in the same organizations, as this is a requirement for the integration to work properly. Organizations are logical entities that group users, projects, and resources in VMware Cloud Services. Users can belong to multiple organizations, but they can only access one organization at a time. To integrate vRealize Operations Cloud and vRealize Log Insight Cloud, users must select the same organization in both services. Deploying a cloud proxy, and then configuring vCenter and ESXi hosts syslog to forward logs to the cloud proxy is another prerequisite for the integration. A cloud proxy is a virtual appliance that collects data from on-premises sources and sends it securely to vRealize Operations Cloud and vRealize Log Insight Cloud. A cloud proxy is required to monitor on-premises vSphere environments, as it acts as a bridge between the on-premises and cloud services. Deploying the vRealize Operations Cloud Content pack, and configuring the adapter to connect to the on-premises vCenter is not a valid option, as this is not a prerequisite for the integration, but a step that can be performed after the integration is established. The vRealize Operations Cloud Content pack is a collection of dashboards, alerts, and reports that provide insights into the vRealize Operations Cloud environment. The adapter is a component that collects data from a specific source, such as vCenter, and sends it to vRealize Operations Cloud. vRealize Operations Cloud and vRealize Log Insight Cloud must be enabled in separate organizations is not a feasible option, as this is the opposite of what is required for the integration. Enabling the services in separate organizations would prevent the users from accessing both services at the same time, and would break the integration. Deploying an on-premises vRealize Log Insight instance, and configuring the integration directly with vRealize Operations Cloud is not a possible option, as this is not supported by the services. vRealize Log Insight Cloud is a cloud-based log analytics service that cannot be integrated with an on-premises vRealize Log Insight instance. vRealize Operations Cloud can only be integrated with vRealize Log Insight Cloud, not with an on-premises vRealize Log Insight instance. References: Integrating vRealize Log Insight and vRealize Operations, section “Integrating vRealize Log Insight and vRealize Operations”. Cloud Proxy Overview, section “Cloud Proxy Overview”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.

To get application-related data (metrics) from the VM that vRealize Operations doesn’t collect, the administrator can use the custom script feature of the End Point Operations Management agent. The custom script feature allows the administrator to run custom scripts in the end point VM and collect custom data which can then be consumed as a metric. The administrator needs to install the End Point Operations Management agent on the VM, place the appropriate script to the VM, and then configure the agent to call the script from the Manage Agent location for the VM in vRealize Operations. The script metrics are created under an object called Custom Script which is a single object per end point VM. The administrator can view the output for the specific metric in the All Metrics tab1. The Telegraf agent is not used for custom script monitoring, but for application monitoring using predefined plugins2. The script should not be placed in the vRealize Operation Manager, but in the end point VM. References: 1: Custom Script 2: Application Monitoring

The type of cost driver that the administrator should configure to allocate the cost of database software across a vSphere cluster that has been licensed is Applications. Applications are software components that run on top of the virtual machines and provide business value. Examples of applications are database software, web servers, middleware, etc. You can assign application costs to VMs based on the type of application they run, such as Oracle, SQL Server, Apache, etc. You can also create custom application types and assign costs to them. By configuring application costs, you can track the expenses of running different types of applications on your private cloud and optimize your resource utilization and budget12. References: 1: Application Cost Driver 2: Costing with VMware vRealize Operations Part 1

To enable High Availability (HA) on a vRealize Operations cluster, the following two options are requirements:

The cluster must have at least one Primary node: The primary node is the first node that is deployed in the cluster and it is responsible for managing the cluster configuration, user interface, and administration functions. The primary node also stores data and performs analytics like any other data node. Without a primary node, the cluster cannot function properly1.

The cluster must have at least one Data node: A data node is a node that collects data from various sources, stores data in its local file system, and performs analytics and alerting functions. A data node also participates in the cluster load balancing and data replication. To activate HA, you must have at least one data node deployed, in addition to the primary node. This allows the creation of a replica node that can take over the primary node functions in case of a failure2. References: 1: About vRealize Operations High Availability 2: High Availability (HA)

 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.

vRealize Operations continuous availability (CA) separates the vRealize Operations cluster into two fault domains, stretching across vSphere clusters, and protects the analytics cluster against the loss of an entire fault domain. A fault domain consists of one or more analytics nodes grouped according to their physical location in the data center. To activate CA, you must have at least one data node deployed, in addition to the primary node and the witness node. The primary node and the data node must reside in different fault domains, and the witness node must reside in a third location. Therefore, the minimum number of fault domains required to achieve vRealize Operations continuous availability with a primary node, data node, and witness node is two. References: About vRealize Operations Continuous Availability; Continuous Availability Considerations

According to the VMware vRealize Operations User Guide1, an alert is a notification that indicates a potential or existing problem in the monitored environment. An alert consists of the following components:

Threshold: A value that defines the normal range of a metric or property. When the value exceeds or falls below the threshold, a symptom is generated.

Symptom: A condition that indicates a deviation from the normal behavior of an object. A symptom can be based on a metric, a property, a message, or a fault. A symptom can be associated with one or more alert definitions.

Alert definition: A rule that defines the criteria and the severity for generating an alert. An alert definition specifies the symptoms, the impacted object types, the alert type, and the alert sub-type.

Recommendation: A suggested action that can help to resolve or prevent the problem that triggered the alert. A recommendation can include a link to a related topic in the documentation or an external URL.An alert definition can have one or more recommendations.

Therefore, the correct answer is C. Recommendation, as this is the alert component that provides instructions that would resolve the triggered alert. References:

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