VMware 5V0-35.21 - VMware vRealize Operations Specialist

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

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

Cost calculation in vRealize Operations is the process of computing the cost of resources and services for your monitored environment. Cost calculation by default occurs daily and whenever there is a change in the inventory or cost drivers values. You can also trigger the cost calculation manually from the Administration > Cost Calculation page1. The default cost calculation interval is every 24 hours, which means that vRealize Operations will update the cost data once a day at the specified time. You can change the cost calculation interval from the Administration > Management > Global Settings > Cost Calculation page2. References: 1: Cost Calculation Status Overview 2: Change the Cost Calculation Interval

To view the status of all objects in vRealize Operations, you can create a dashboard by adding widgets or views. You can create and modify dashboards and configure them to meet your environment needs. Widgets are graphical elements that display data and analysis from vRealize Operations. Views are predefined or custom presentations of object data that you can use in dashboards, reports, or alerts. Alerts, recommendations, and reports are not objects that can be used to create dashboards, but they can be displayed or accessed from dashboards. References:

Create and Configure Dashboards

Dashboards

vROPS Dashboards Overview

 According to the VMware vRealize Operations User Guide1, vRealize Operations allows the user to perform various actions on vSphere virtual machines from the product UI. These actions can help to manage, optimize, and troubleshoot the virtual machines and their resources. Some of the actions that can be performed on vSphere virtual machines from vRealize Operations product UI are:

Create virtual machine snapshot: This action creates a snapshot of the virtual machine, which is a point-in-time copy of the virtual machine state and data. A snapshot can be used to revert the virtual machine to a previous state, or to clone or migrate the virtual machine. The user can specify the name, description, and memory options for the snapshot.

Delete virtual machine snapshot: This action deletes a snapshot of the virtual machine, which frees up the disk space used by the snapshot. The user can select the snapshot to delete from a list of available snapshots for the virtual machine.

Move virtual machine: This action moves the virtual machine to a different host or cluster within the same vCenter Server. The user can select the destination host or cluster from alist of compatible and available options. The move action can help to balance the workload or improve the performance of the virtual machine.

Therefore, the correct answers are A. Create virtual machine snapshot, B. Delete virtual machine snapshot, and C. Move virtual machine, as these are three of the actions that can be performed on vSphere virtual machines from vRealize Operations product UI. References:

1: VMware vRealize Operations User Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-user-guide.pdf, page 31-32, 34-35, 37-38

According to the VMware vRealize Operations Reference Materials, the cloud services console is a unified interface that allows you to access and manage your VMware Cloud services. The Identity & Access Management capability is available in the cloud services console regardless of the subscribed cloud services, as it enables you to manage users, groups, roles, and permissions for your organization. The other capabilities, such as Organization Access Management, Settings, and Cost Insights, are specific to certain cloud services and may not be available for all subscriptions. References:

Cloud Services Console Overview

Identity & Access Management Overview

Workload Optimization 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 Optimization 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.

Therefore, the configuration that proactively moves workloads so that the resource utilization ensures maximum headroom for all resources is Balance.

References:

1: vRealize Operations - VMware 2: vRealize Operations Manager User Guide 3: Workload Optimization Details - VMware Docs 4: Workload Optimization in vRealize Operations Manager : [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]

What-If Analysis is a feature of vRealize Operations that allows you to plan for an increase or decrease in workload or capacity requirements in your virtual infrastructure. You can use What-If Analysis to evaluate the demand and supply for capacity on your resources, and to assess the potential risk to your current capacity. You can create scenarios for adding and removing workloads, hosts, clusters, or datastores, and see the impact on the time remaining and capacity remaining scores12.

Time remaining and capacity remaining are two metrics that measure the available capacity in your environment. Time remaining is the estimated time until a resource runs out of capacity based on the current utilization and growth trends. Capacity remaining is the percentage of unused capacity that is available for future growth. Both metrics are calculated for CPU, memory, disk space, and network bandwidth resources34.

By using What-If Analysis, you can accomplish the goal of determining how many more ESXi servers are needed to increase the time remaining and capacity remaining scores. You can create a scenario for adding ESXi servers to a cluster or a datacenter, and specify the number, type, and configuration of the servers. You can then see the projected time remaining and capacity remaining scores for the cluster or the datacenter after adding the servers. You can also compare the results with the current scores and the recommended scores. You can adjust the number of servers until you reach the desired scores5 .

References:

1: What-If Analysis: Modeling Workload, Capacity, or Migration Planning 2: Create a What-If Scenario 3: [Capacity Overview - VMware Docs] 4: [Time Remaining and Capacity Remaining Metrics] 5: [Add Hosts to a Cluster or Datacenter Scenario] : [View the Results of a What-If Scenario] : vRealize Operations Manager User Guide : 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 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.

 Exporting the dashboard from the development instance, and importing the dashboard into the other instance is the correct action to accomplish the goal. This method allows the administrator to share the dashboard configuration file (in JSON format) with other vROps instances, and edit the dashboard in the other instances as needed. Generating a custom URL, setting the expiration to “never expire”, and importing this URL into the other instance is not a valid option, as this method only allows the administrator to share a non-authenticated view of the dashboard, not the dashboard configuration file. Using the Embed option to import the HTML code into the other instances is not a feasible option, as this method only allows the administrator to embed the dashboard into a web page, not to import the dashboard configuration file. Connecting the vROps instances together, and synchronizing the dashboards is not a possible option, as vROps does not support thisfeature. References: Export and Import Dashboards, section “Export and Import Dashboards”. Options for Sharing Dashboards, section “Options for Sharing Dashboards”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.