5V0-35.21 Exam Dumps : VMware vRealize Operations Specialist

 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.

According to the vRealize Operations User Guide1, Business Intent is a feature that allows the administrator to define the performance, efficiency, and consolidation goals for the clusters and hosts in the SDDC, and to specify the maximum amount of cluster resources to be reserved for burst capacity. Business Intent is applied to objects in vRealize Operations using vCenter Server tags, which are key:value labels that allow operators to add meta-data to vCenter Server objects. By tagging VMs, hosts, and/or clusters with specific tags, the administrator can create business-related placement constraints, such as VMs can only be placed on hosts/clusters with matching tags. For example, the tag OS: Linux can indicate a cluster or VM that is assigned to the category OS with a tag name of Linux. vRealize Operations then uses these tags to optimize the placement and balance of the workloads, and to perform automated remediation actions in the event of an issue. The other options are not correct because:

• Groups are not used to apply Business Intent to objects in vRealize Operations. Groups are collections of objects that share common characteristics, such as type, name, location, or relationship. Groups are used to organize objects for monitoring, analysis, alerting, or policy assignment, but not for workload placement or balance1.
• Policies are not used to apply Business Intent to objects in vRealize Operations. Policies are sets of configuration settings that define how vRealize Operations monitors and manages the objects in the SDDC. Policies are used to enable or disable alerts, metrics, properties, symptoms, recommendations, or actions for different types of objects, but not for workload placement or balance1.
• Roles are not used to apply Business Intent to objects in vRealize Operations. Roles are collections of permissions that define what actions a user can perform on the objects in the SDDC. Roles are used to control the access and visibility of the objects for different users, but not for workload placement or balance1. References: 1: vRealize Operations User Guide, pages 57-59, 62-63, 66-67, 70-71.

According to the VMware vRealize Operations Reference Materials, the Wait Cycle and the Cancel Cycle are the settings that determine how long a symptom condition must be true or false before the symptom is triggered or cancelled. The default cycle for both settings is 5 minutes, which means that each cycle corresponds to one collection interval of 5 minutes. Therefore, if a symptom has a Wait Cycle of 3 and a Cancel Cycle of 2, it will take 15 minutes (3 cycles x 5 minutes) for the symptom to be triggered after the condition becomes true, and 10 minutes (2 cycles x 5 minutes) for the symptom to be cancelled after the condition becomes false. The other options are incorrect because they do not match the calculation based on the given settings and the default cycle. References: Symptom Definition Settings; Alert Definition Best Practices