VMware 5V0-35.21 Dumps

According to the VMware vRealize Operations User Guide1, a Super Metric is a custom metric that is derived from one or more existing metrics. A Super Metric can be used to calculate complex formulas, aggregate data across multiple objects, or create new metrics that are not available by default. A Super Metric can be created using the Super Metric Editor in vRealize Operations.

However, before a Super Metric’s data collection may begin, the Super Metric must be enabled in a policy. A policy is a set of rules and settings that determine how vRealize Operations analyzes and manages the objects in the environment. A policy can be applied to one or more object types or groups. To enable a Super Metric in a policy, the administrator must edit the policy, select the Collect Metrics and Properties option, and then select the Super Metric from the list of available metrics. The administrator can also specify the collection level, collection interval, and retention period for the Super Metric.

The other options are not required before a Super Metric’s data collection may begin. Enabling in Alerts, Object Types, or Objects are not necessary steps for collecting Super Metric data. These options are used for different purposes, such as creating alert definitions, defining object relationships, or assigning policies to individual objects. References:

• 1: VMware vRealize Operations User Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-user-guide.pdf, page 35-36, 39-40, 43-44

To achieve the lowest cost in Workload Optimization, the administrator should select the Consolidate option, which will place VMs into as few clusters as possible, but allows for less responsive capacity. This is good for populations with steady demand and may reduce licensing and hardware costs, such as power and cooling1. The Consolidate option is one of the three operational intents that can be selected for Workload Optimization, along with Balance and Moderate2. The Balance option will spread VMs evenly over the available resources, but may move VMs more often. The Moderate option will minimize VM contention, but will not attempt to move VMs to achieve better balance or consolidation1. References: 1: Optimize Performance with VMware vRealize Operations 2: Self-Driving Operations by VMware vRealize Operations Datasheet

Expected Utilization is the workload option that should be included in the scenario to simulate 25% utilization of the resources. Expected Utilization is a percentage value that indicates how much of the allocated resources (CPU, memory, and storage) are expected to be used by the workload. By setting the Expected Utilization to 25%, the administrator can model the impact of adding or removing a workload that consumes 25% of the resources in the datacenter. Memory, Annual Projected Growth, and CPU are not workload options, but workload attributes. Memory and CPU are the amount of resources allocated to the workload, and Annual Projected Growth is the percentage by which the workload is expected to grow each year. These attributes do not directly specify the utilization of the resources by the workload. References: What-If Analysis - Workload Planning: Traditional, section “How What-If Analysis - Workload Planning: Traditional Works”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.