Free Practice Questions for VMware 5V0-35.21 Exam

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 VMware vRealize Operations Reference Materials, the component that will be available when a user logs in to the vRealize Operations Product UI is the Dashboards page. The Dashboards page is the main interface of the Product UI, where the user can view and interact with various dashboards that display the data and analysis of the monitored objects and environments. The Dashboards page also allows the user to create and customize their own dashboards, as well as access other features such as alerts, reports, views, and policies. The other options are incorrect because they are not available in the Product UI, but in the Admin UI. The Software Update page, the Certificate management, and the System Status page are all components of the Admin UI, which is a separate interface that provides the administrative and configuration functions for the vRealize Operations cluster. The Admin UI can be accessed by logging in to the master node or the replica node of the cluster, using the admin user account or a user account with the Administrator role. The user who has access only to the Product UI cannot access the Admin UI or its components. References: vRealize Operations Manager Overview; Log in to vRealize Operations Manager; vRealize Operations Manager Administration

 The support bundle that the customer should send that fits the bandwidth constraints is the light-support bundle from all nodes. A support bundle is a collection of logs, configuration files, and diagnostic information that can be used by VMware support to troubleshoot and resolve issues with vRealize Operations1. A support bundle can be generated from the Admin UI of vRealize Operations, and it can include information from the primary nodes, the replica nodes, and the remote collectors2. A support bundle can be either full or light, depending on the amount and type of information that is included. A full-support bundle contains all the logs, configuration files, and diagnostic information that are available, and it is recommended for most cases. A light-support bundle contains only the essential logs, configuration files, and diagnostic information that are needed for basic troubleshooting, and it is recommended for cases where the bandwidth is limited or the issue is not complex3. A light-support bundle is smaller in size than a full-support bundle, and it can be generated faster and transferred easier. A light-support bundle from all nodes includes the information from the primary nodes, the replica nodes, and the remote collectors, and it can help VMware support to identify the cause of the erratic behavior and the role of the remote collectors. A full-support bundle from the primary nodes only (option A) or a light-support bundle from the primary nodes only (option B) are not the best choices, as they do not include the information from the replica nodes and the remote collectors, which may be relevant for the issue. A full-support bundle from all nodes (option C) is not the best choice, as it is larger in size than a light-support bundle, and it may exceed the bandwidth constraints or take longer to generate and transfer. References:

1: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 35.

2: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 36.

3: vRealize Operations Manager Installation and Configuration Guide, VMware, 2021, p. 37.

4: VMware vRealize Operations Specialist Exam 2023 (5V0-35.21) Exam Guide, VMware, 2021, p. 11.

 According to the VMware vRealize Operations Reference Materials, the cloud provider that needs to be added as a custom cloud provider when running a What-If Analysis is Oracle Cloud. The What-If Analysis feature allows the administrator to compare the cost and performance of running workloads in different public cloud providers, such as AWS, IBM Cloud, Microsoft Azure, Google Cloud, and Alibaba Cloud. These public cloud providers are supported out-of-the-box in vRealize Operations, and the administrator can select them from the predefined list when creating a migration scenario. However, if the administrator wants to compare the cost and performance of running workloads in Oracle Cloud, they need to add it as a custom cloud provider, and upload a rate card that contains the pricing information for Oracle Cloud services. The other options are incorrect because they are supported out-of-the-box in vRealize Operations, and they do not need to be added as a custom cloud provider when running a What-If Analysis. References: What-If-Analysis - Migration Planning: Public Cloud; VMware vRealize Operations What-If Analysis; VMware vRealize Operations for Public Cloud

According to the VMware vRealize Operations Reference Materials, Workload Optimization is a feature that allows you to automatically balance and optimize workloads across your virtualized infrastructure. Workload Optimization has four settings that determine how aggressively it moves workloads between clusters: Moderate, Balance, Consolidate, and Buffer. Each setting has a different impact on the number of vMotion operations, the cluster headroom, and the workload contention.

The Consolidate setting is the most aggressive setting that aims to minimize the workload contention across clusters by reducing the number of clusters used and maximizing the utilization of each cluster. The Consolidate setting performs the most vMotion operations, leaves the least cluster headroom, and has the lowest workload contention. The Consolidate setting is suitable for environments that have overprovisioned clusters and want to free up some clusters for other purposes or reduce the infrastructure costs. Therefore, option C is correct.

The other options are not correct because they do not meet the goal of minimizing the workload contention across clusters by reducing vMotion operations. Option A is not correct because the Moderate setting is the least aggressive setting that aims to maintain the current state of the clusters and avoid unnecessary vMotion operations. The Moderate setting performs the least vMotion operations, leaves the most cluster headroom, and has the highest workload contention. The Moderate setting is suitable for environments that have stable clusters and do not want to disrupt the existing workload placement. Option B is not correct because the Balance setting is a moderate setting that aims to balance the workload distribution across clusters and improve the performance of the clusters. The Balance setting performs a moderate number of vMotion operations, leaves a moderate cluster headroom, and has a moderate workload contention. The Balance setting is suitable for environments that have some imbalanced clusters and want to optimize the workload placement. Option D is not correct because the Buffer setting is a conservative setting that aims to create more cluster headroom and reduce the risk of resource shortage. The Buffer setting performs a low number of vMotion operations, leaves a high cluster headroom, and has a low workload contention. The Buffer setting is suitable for environments that have unpredictable or bursty workloads and want to ensure enough capacity for future demand. References:

Configuring and Using Workload Optimization

Start Running a Self-Driving Datacenter – vRealize Operations 7.0 Workload Optimization

Using Workload Optimization to Improve Performance

The impact setting of an alert definition determines which badge of an object is affected when the alert is triggered. The impact setting can be one of the following: Health, Risk, or Efficiency. The Health impact indicates that the alert affects the current state of the object and requires immediate attention. The Risk impact indicates that the alert affects the future state of the object and requires proactive action. The Efficiency impact indicates that the alert affects the optimal use of resources by the object and requires optimization. Therefore, to achieve the goal of affecting the Risk badge of an object when the alert is triggered, the administrator should configure the impact setting of the alert definition to Risk. References: Defining Alerts in vRealize Operations; Policy Alert Definitions

The function that is unavailable in the vRealize Operations Admin UI is viewing alerts, symptoms, and policies. The Admin UI is a separate interface from the Product UI that provides access to selected maintenance functions beyond what the Product UI supports. TheAdmin UI is used for platform administration tasks, such as upgrading vRealize Operations, enabling or disabling High Availability (HA), uploading and installing vRealize Operations PAK files, taking vRealize Operations Online/Offline, and managing certificates, passwords, and users1. The Admin UI does not provide access to the operational functions, such as viewing alerts, symptoms, and policies, which are available in the Product UI. The Product UI is used for monitoring and managing the objects, metrics, alerts, dashboards, reports, and policies in vRealize Operations2.

References: 1: About the vRealize Operations Administration Interface 2: About the vRealize Operations Product Interface

To automate an action for an alert, you must enable it in the object’s associated policy. A policy defines the settings and rules that vRealize Operations applies to objects in your environment. You can activate actionable alerts in your policies by selecting the Automate option for the alert definition that is associated with the symptom, recommendation, and action that you want to automate. When an alert is triggered that is associated with the recommendation, it triggers the action without any user intervention. The other options are not correct because they do not enable the automation of the action. An object’s associated recommendation is a suggestion for resolving the problem indicated by the alert, but it does not activate the action. An object in the default policy is not specific enough to enable the automation of the action. An object’s associated symptom definition is a condition that indicates a potential problem, but it does not activate the action. References: Actions Supported for Automation, VMware vRealize Operations Actions

Suspending an alert is the action that allows the administrator to stop the alert from triggering again while investigating the problem. Suspending an alert also automatically assigns the alert to the user who performed the action1. Suspending an alert does not cancel or disable the alert, but rather pauses the alert evaluation until the user resumes or cancels the alert2. Taking ownership of an alert does not stop the alert from triggering again, but only indicates that the user is responsible for resolving the alert3. Disabling an alert prevents the alert from being generated for any object, which is not recommended unless the alert is no longer relevant or useful4. Canceling an alert removes the alert from the system, which is not appropriate if the alert is still valid and requires investigation. References: 1: Suspend an Alert - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.10/com.vmware.vcom.user.doc/GUID-595146FB-93F7-4F34-A9D3-79144EA7A658.html)  2: Alert Actions - VMware Docs(https://docs.vmware.com/en/vRealize-Operations/8.10/com.vmware.vcom.core.doc/GUID-F9AF30F3-089B-43A8-8323-F266E51C05B8.html)  3: Take Ownership of an Alert - VMware Docs(https://kb.vmware.com/s/article/2012021)  4: Disable an Alert Definition - VMware Docs(https://www.brockpeterson.com/post/vmware-vrealize-operations-actions) : Cancel an Alert - VMware Docs

According to the VMware vRealize Operations User Guide1, business intent is a feature that allows the administrator to define the desired state and behavior of the clusters and hosts in the environment based on business objectives and constraints. Business intent can be used to optimize the placement and balance of workloads across clusters and hosts, as well as to enforce license compliance and availability requirements.

One of the types of business intent that can be configured in vRealize Operations is Business Intent - Clusters. This type of business intent allows the administrator to assign tags to clusters and virtual machines, and then create rules that match the tags to ensure that the virtual machines are placed on the appropriate clusters. For example, the administrator can tag two clusters as Windows and two clusters as Linux, and then tag the virtual machines accordingly. Then, the administrator can create rules that match the Windows tag and the Linux tag, and set the enforcement mode to Mandatory. This will ensure that the Windows workloads only run on the Windows clusters, and the Linux workloads only run on the Linux clusters.

Therefore, the correct answer is B. Business Intent - Clusters, as this is the type of business intent that should be configured by the administrator to achieve the goal of ensuring the workloads only run on their assigned nodes. References:

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