VMware 5V0-35.21 Practice Test - Questions Answers, Page 14

A support bundle is a collection of log and configuration files that can help troubleshoot a vROps issue. To create a support bundle, the system administrator can use the vROps UI and select the option to create a light or full support bundle. A light support bundle includes 24 hours of logs, while a full support bundle includes all available logs and configuration files. For an intermittent issue that occurred in the last 12 hours, a light support bundle should be sufficient to collect the relevant information.The system administrator can also select the cluster nodes that need to be evaluated for support, and download the support bundle in ZIP format for analysis or sending to VMware Technical Support1. The other options are not recommended or efficient ways to collect the relevant information. Collecting the vCenter and vROps primary node logs using SSH and the vm-support utility would not include the logs from the other vROps nodes, and would require manual steps to gather and compress the files. Using the vROps UI to create a full support bundle for ESXi, vCenter, and primary vROps nodes would include unnecessary and excessive data that could slow down the process and consume more disk space.Using SSH to copy the log files from each of the vROps nodes from /var/log/warn & /var/log/messages locations would also require manual steps to gather and compress the files, and would not include the configuration files that could be useful for troubleshooting.References:1:Create a vRealize Operations Support Bundle

To configure vRealize Operations to operate in Continuous Availability mode, you need to use theproduct User Interface -> Administration -> Cluster Management -> Configure Availabilityoption. This option allows you to enable or disable Continuous Availability for the vRealize Operations cluster, as well as to view and edit the fault domains and node pairs.You can also monitor the status and synchronization of the nodes in each fault domain12. The other options are not correct because:

The administration User Interface --> System Status --> Configure Availability option does not exist.The administration User Interface only has the following tabs: System Status, Cluster Management, Software Update, and Support3.

The administration User Interface -> Architecture -> Configure Availability option does not exist.The administration User Interface does not have an Architecture tab3.

The product User Interface -> Administration -> Support -> Configure Availability option does not exist.The Support tab under the Administration menu only has the following options: Logs, Support Bundles, and Support Alerts4.References:1:Enable Continuous Availability in vRealize Operations2:About vRealize Operations Continuous Availability3: [vRealize Operations Manager Administration Interface]4: [Support]

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, 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

When creating an alert definition that has multiple symptoms, the triggered symptom that sets the criticality is the most critical symptom. The criticality of an alert definition is the level of severity or urgency that the alert indicates, such as Critical, Immediate, Warning, or Informational.The criticality of an alert definition is determined by the highest criticality of the symptoms that are included in the alert definition1. When an alert is generated, the criticality of the alert is set by the most critical symptom that triggered the alert. For example, if an alert definition has two symptoms, one with a criticality of Critical and one with a criticality of Warning, and both symptoms are triggered, the alert will have a criticality of Critical.However, if only the symptom with a criticality of Warning is triggered, the alert will have a criticality of Warning2.References:1:Policy Alert Definitions2:Alert Definition Best Practices

The workload placement feature between vRealize Automation Cloud and vRealize Operations Cloud allows vRealize Operations Cloud to provide recommendations for the initial placement of virtual machines based on the demand and allocation models.To enable this feature, the following pre-requisites must be met12:

Both vRealize Automation Cloud and vRealize Operations Cloud must manage the same Cloud Account. This means that the vCenter Server instance that is used as a cloud account in vRealize Automation Cloud must be the same as the one that is monitored by vRealize Operations Cloud. This ensures that the vSphere objects are consistent and identifiable across both platforms.

In vRealize Automation Cloud, the target Cloud Zone Placement Policy must be set to ADVANCED. This option activates the integration with vRealize Operations Cloud and allows it to provide placement recommendations based on the vRealize Operations policy settings. The other options, such as SPREAD or BINPACK, use the vRealize Automation Cloud's own placement logic and do not leverage vRealize Operations Cloud.

All clusters within the target Cloud Zone must have fully automated VMware DRS enabled. This is a requirement for vRealize Operations Cloud to provide placement recommendations, as it relies on the DRS algorithm to balance the workload across the clusters. If the clusters do not have DRS enabled or set to manual or partially automated, vRealize Operations Cloud cannot provide placement recommendations.

The other options, such as installing the vRealize Operations Management Pack for vRealize Automation Cloud, enabling VMware HA on the clusters, or setting the placement policy to SPREAD, are not required to enable the workload placement feature between vRealize Automation Cloud and vRealize Operations Cloud.References:1:Advanced Workload Placement for Allocation Model2:Learn more about workload placement

Workload Management is a feature of VMware vRealize Operations that enables self-driving operations management for hybrid and multi-cloud environments.It uses artificial intelligence and machine learning to monitor, analyze, and automate the performance, capacity, cost, and configuration of applications, infrastructure, and services12.

Workload Management allows administrators to set a goal for workload optimization, which defines how vRealize Operations balances the resource utilization across clusters and data centers.The goal can be one of the following options34:

Balance: This option proactively moves workloads so that the resource utilization ensures maximum headroom for all resources. This means that vRealize Operations tries to distribute the workload evenly across the clusters and data centers, and avoid resource contention or overcommitment. This option is suitable for scenarios where workload performance is the first priority, and where there is a need for extra space for growth or spikes in demand.

Moderate: This option minimizes the workload contention by moving workloads away from clusters and data centers that are experiencing high resource utilization. This means that vRealize Operations tries to reduce the risk of performance degradation or SLA violations by ensuring that there is enough capacity to meet the workload demand. This option is suitable for scenarios where workload availability and reliability are the main goals, and where there is a moderate tolerance for resource imbalance or inefficiency.

Consolidate: This option proactively minimizes the number of clusters and data centers used by workloads by moving workloads to the clusters and data centers that have the lowest resource utilization. This means that vRealize Operations tries to optimize the resource efficiency and reduce the operational cost by freeing up unused or underutilized resources. This option is suitable for scenarios where workload consolidation and cost optimization are the primary objectives, and where there is a high tolerance for resource contention or overcommitment.

Workload Management relies on VMware Distributed Resource Scheduler (DRS) and VMware Storage DRS to perform the workload optimization actions. DRS is a feature that automatically balances the compute resources and power consumption across the hosts in a cluster. Storage DRS is a feature that automatically balances the storage resources and I/O load across the datastores in a datastore cluster .

To enable Workload Management to move a storage resource, such as a virtual disk or a virtual machine, Storage DRS must be enabled for the cluster that contains the storage resource. Storage DRS can be enabled or disabled at the cluster level, and can be configured with different automation levels, such as manual, fully automated, or partially automated .

If Storage DRS is not enabled for the cluster, Workload Management cannot move the storage resource, as it does not have the permission or the mechanism to do so. This is the underlying reason for the problem. The other options are not relevant for moving a storage resource. DRS is only responsible for moving the compute resources, such as CPU and memory, not the storage resources. Storage DRS can be configured for both intra-datacenter and cross-datacenter migrations, not only for cross-datacenter migrations. The automation level of DRS does not affect the ability of Workload Management to move the storage resource, as long as Storage DRS is enabled.

References:

1:vRealize Operations - VMware2:vRealize Operations Manager User Guide3:Workload Optimization Details - VMware Docs4:Workload Optimization in vRealize Operations Manager: [Distributed Resource Scheduler - VMware Docs] : [Storage DRS - VMware Docs] : [Enable or Disable Storage DRS for a Datastore Cluster - VMware Docs] : [Set the Automation Level for Storage DRS - VMware Docs] : [vRealize Operations Manager Installation and Configuration Guide] : [vRealize Operations Manager Concepts Guide] : [vRealize Operations Manager Administration Guide] : [vRealize Operations Manager Customization and Extensibility Guide] : [vRealize Operations Manager Troubleshooting Guide] : [vRealize Operations Manager API Programming Guide] : [vRealize Operations Manager Certification Exam Guide]

According to the vRealize Operations Cloud Getting Started guide1, the two steps that are needed to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance are:

Deploy and configure a cloud proxy. A cloud proxy is a virtual appliance that acts as a bridge between the on-premises vCenter instance and the vRealize Operations Cloud instance. It collects data from the vCenter instance and sends it securely to the vRealize Operations Cloud instance. It also enables actions and remote console access from the vRealize Operations Cloud instance to the on-premises vCenter instance.The guide provides the steps to download, deploy, and configure the cloud proxy using the vRealize Operations Cloud user interface1.

Add a vCenter cloud account. A vCenter cloud account is a configuration that defines the connection details and credentials of the on-premises vCenter instance. It also specifies the cloud proxy that is associated with the vCenter instance.The guide provides the steps to add a vCenter cloud account using the vRealize Operations Cloud user interface1.

The other options are not correct because:

Deploying and configuring a Data node is not a required step to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance. A Data node is a component of the vRealize Operations Cloud cluster that stores and processes data.It is managed by the vRealize Operations Cloud service provider and does not need to be deployed or configured by the customer2.

Deploying and configuring a Primary node is not a required step to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance. A Primary node is a component of the vRealize Operations Cloud cluster that provides the user interface and administration functions.It is managed by the vRealize Operations Cloud service provider and does not need to be deployed or configured by the customer2.

Adding a vRealize Operations Cloud account is not a required step to onboard an on-premises vCenter instance into an existing vRealize Operations Cloud instance. A vRealize Operations Cloud account is a configuration that defines the connection details and credentials of the vRealize Operations Cloud instance. It is used to integrate vRealize Operations Cloud with other VMware Cloud services, such as VMware Cloud on AWS or VMware Cloud Director.It is not related to the on-premises vCenter instance3.References:1: vRealize Operations Cloud Getting Started guide, pages 9-132: vRealize Operations Cloud Concepts guide, pages 5-63: vRealize Operations Cloud User Guide, pages 17-18.

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''.