VMware 5V0-35.21 Dumps Questions Answers

According to the VMware vRealize Operations Reference Materials, the Custom Script option in vRealize Operations is able to calculate measurements on a Guest OS. The Custom Script option allows the administrator to run a script on the Guest OS of a virtual machine and collect the output as a metric. The script can be written in any language that is supported by the Guest OS, such as PowerShell, Bash, or Python. The script can perform any calculation or operation that is required by the administrator, such as checking the CPU load, memory usage, disk space, or application status. The script output can be numeric or text, and it can be displayed in a dashboard, alert, or report. The other options, such as HTTP Check, UDP Check, or TCP Check, are not able to calculate measurements on a Guest OS. They are used to monitor the availability and response time of a web service, a UDP port, or a TCP port, respectively. They do not run any script on the Guest OS, nor do they collect any metric from the Guest OS. References: Custom Script; How to build a per-guest filesystem report in vRealize Operations using the ‘Breakdown By’ feature; How to Get In-Guest Metrics in vRealize Operations for Horizon 6

The administrator needs the Active Directory domain administrator account and password to configure service discovery to identify which virtual machines are running Active Directory services. Service discovery is a feature of vRealize Operations that allows the administrator to discover and monitor the applications and services running on the virtual machines in the environment1. Service discovery can be performed using two methods: credential-less and credential-based. Credential-less service discovery uses VMware Tools to query the guest operating system for the list of running processes, and then matches them with a predefined set of signatures to identify the applications and services2. Credential-based service discovery uses the credentials provided by the administrator to log in to theguest operating system and run commands or scripts to discover the applications and services3. Credential-less service discovery can be used for most common applications and services, such as web servers, database servers, or file servers, but it has some limitations, such as not being able to discover clustered or distributed applications, or applications that run on non-standard ports4. Credential-based service discovery can be used for more complex and customized applications and services, such as Active Directory, Exchange, or SharePoint, but it requires the administrator to provide the appropriate credentials for each guest operating system. For Windows operating systems, the credentials must be either a local administrator account or a domain administrator account. For Active Directory services, the domain administrator account is preferred, as it has the necessary permissions to access the Active Directory information and configuration. Therefore, the administrator needs the Active Directory domain administrator account and password to configure service discovery to identify which virtual machines are running Active Directory services. No credentials are needed since credential-less service discovery can be used (option A) is not a correct answer, as credential-less service discovery cannot discover Active Directory services, which require credential-based service discovery. Local Windows administrator account and password (option B) is not a correct answer, as the local administrator account may not have the sufficient permissions to access the Active Directory information and configuration, which require the domain administrator account. Active Directory domain user account and password (option D) is not a correct answer, as the domain user account may not have the necessary permissions to access the Active Directory information and configuration, which require the domain administrator account. References:

• 1: vRealize Operations Manager User Guide, VMware, 2021, p. 237.
• 2: vRealize Operations Manager User Guide, VMware, 2021, p. 238.
• 3: vRealize Operations Manager User Guide, VMware, 2021, p. 239.
• 4: vRealize Operations Manager User Guide, VMware, 2021, p. 240.
• [5]: vRealize Operations Manager User Guide, VMware, 2021, p. 241.
• [6]: vRealize Operations Manager User Guide, VMware, 2021, p. 242.
• [7]: vRealize Operations Manager User Guide, VMware, 2021, p. 244.

 The Troubleshooting Workbench is a feature in vRealize Operations that helps you perform advanced troubleshooting tasks on an alert or an object. You can look for potential evidences of a problem within a specific scope and time range. The potential evidences are based on three types of data: Alerts, Events, and Property Changes. Alerts show the active and inactive alerts that are related to the object or its peers. Events show the events that are based on a change in the metrics, such as spikes, drops, or anomalies. Property Changes show the changes in the configuration or properties of the object or its peers, such as CPU, memory, or disk allocation. These types of data help you identify the root cause of the issue and take corrective actions. Symptoms and Anomalous Metrics are not considered as potential evidence in the Troubleshooting Workbench, although they may be used to trigger alerts or events. Logs are not displayed in the Troubleshooting Workbench, but they can be accessed from the Logs tab of the object. References: Discovering Potential Evidences Using the Troubleshooting Workbench, Solving Real Problems with vRealize Operations TroubleshootingWorkbench, Troubleshooting Workbench Home Page, vROps 8.0 Troubleshooting Workbench and Blue Medora