5V0-35.21 Exam Dumps : VMware vRealize Operations Specialist

 The frequency at which new services are discovered when using Service Discovery in vRealize Operations is every 5 minutes. 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 andservices2. Credential-based Service Discovery uses the credentials provided by the administrator to log in to the guest operating system and run commands or scripts to discover the applications and services3. Credential-less Service Discovery collects the information about the services running inside the guest every five minutes4. Credential-based Service Discovery collects the information about the services running inside the guest every 24 hours5. Therefore, the frequency at which new services are discovered when using Service Discovery in vRealize Operations depends on the method used, but the most frequent one is every 5 minutes for credential-less Service Discovery. 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: Credential-Less Service Discovery with vRealize Operations, VMware, 2020, 4.
• 5: Service Discovery with VMware vRealize Operations, Brock Peterson, 2021, 5.

Custom groups are collections of objects that you define based on criteria that you specify. You can use custom groups to assign different vRealize Operations policies to a particular set of objects that share common characteristics or belong to a specific business unit1. Custom groups allow you to override the default policy settings for the objects in the group and apply a different policy that suits your requirements2. For example, you can create a custom group of ESXi clusters that run database servers and assign a different capacity policy to them than the rest of the clusters in your environment2. References: = 1 Managing Custom Object Groups in vRealize Operations - VMware Docs, 2 Policies - VMware Docs

To add an additional data node to the existing vRealize Operations cluster, you need to deploy a new data node from the Administration Ul. A data node is a node that collects, stores, processes, and analyzes data from your environment. You can expand an existing installation to add a data node by following these steps1:

• In a Web browser, navigate to the name or IP address of the node that will become the data node. The setup wizard appears, and you do not need to log in to vRealize Operations.
• Click Expand an Existing Installation.
• Click Next.
• Enter a name for the node (for example, Data-1).
• From the Node Type drop-down, select Data.
• Enter the FQDN or IP address of the primary node and click Validate.
• Select Accept this certificate and click Next.
• Verify the vRealize Operations administrator username of admin.
• Enter the vRealize Operations administrator password.
• Click Next, and click Finish.

The other options are not correct because they do not deploy a new data node from the Administration Ul. Option A is incorrect because cloning an existing data node is not supported and may cause data inconsistency. Option C is incorrect because deploying a new virtual appliance from an OVF file is not enough to add a data node to the cluster. You still need to configure the node type and join the cluster from the Administration Ul. Option D is incorrect because enabling High Availability in the Administration Ul does not add a data node to the cluster. It only creates a replica of the primary node for failover purposes. References: Expand an Existing Installation to Add a Data Node