VMware 5V0-35.21 Exam Actual Questions

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