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.

Role is the attribute that should be defined to ensure that group members can access vRealize Operations objects when importing a group from Active Directory into vRealize Operations. Role is a set of permissions that defines what actions a user or a group can perform on vRealize Operations objects, such as dashboards, alerts, reports, and policies. By assigning a role to a group, the administrator can grant or restrict access to vRealize Operations objects for all the group members. Description, Group Members, and Type are not attributes that ensure that group members can access vRealize Operations objects when importing a group from Active Directory into vRealize Operations. Description is an optional field that provides additional information about the group. Group Members is a list of users that belong to the group. Type is a classification of the group based on the source, such as Local, LDAP, or Active Directory. References: Import User Groups From Source, section “Import User Groups From Source”. vRealize Operations Manager User Guide, section “Create and Configure Dashboards”.

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