5V0-35.21 Exam Study Guide: The Ultimate 2026 Practice Test

According to the VMware vRealize Operations Reference Materials, the users who are imported from an LDAP authentication source can access vSphere and other objects including third-party objects in vRealize Operations, as long as they have the appropriate permissions and roles assigned to them. The LDAP users can use their LDAP credentials to log in to vRealize Operations, and they can view and manage the objects that are within their scope of access. The other options are incorrect because they are either false or irrelevant. The credentials for the LDAP users are not stored in the central Postgres database of vRealize Operations, but in the LDAP server. The LDAP users are allowed to perform any actions in vRealize Operations that are permitted by their roles and permissions. The LDAP user password policy is not set by vRealize Operations, but by the LDAP server.  References :  Managing Users and Access Control in vRealize Operations ;  Authentication Sources ;  Give Administrator Access to AD or LDAP Users

In VMware vRealize Operations, policies determine how objects are analyzed and managed. They include settings for metrics collection, alert definitions, symptoms, recommendations, and more. If an administrator disables some virtual machine metrics in the Production policy, only objects assigned to that specific policy will be affected. The changes won’t impact other policies or globally affect all objects. This is because policies are hierarchical and inherit settings from their parent policies, unless overridden by the child policies. In the exhibit, the Production policy and the TestDev policy are both child policies of the Company default policy, which is a child policy of the vSphere solution’s default policy, which is a child policy of the Base settings. Therefore, any changes made to the Production policy will only apply to the objects assigned to that policy, and not to the objects assigned to the TestDev policy or any other policy.  References :

vRealize Operations Policies , page 1-2

Manage Policies , page 3-4

Disable Metrics Collection , page 5

The type of cost driver that the administrator should configure to allocate the cost of database software across a vSphere cluster that has been licensed is  Applications . Applications are software components that run on top of the virtual machines and provide business value. Examples of applications are database software, web servers, middleware, etc. You can assign application costs to VMs based on the type of application they run, such as Oracle, SQL Server, Apache, etc. You can also create custom application types and assign costs to them.  By configuring application costs, you can track the expenses of running different types of applications on your private cloud and optimize your resource utilization and budget 1 2 .  References :  1 :  Application Cost Driver   2 :  Costing with VMware vRealize Operations Part 1