5V0-35.21 Exam Dumps : VMware vRealize Operations Specialist

According to the VMware vRealize Operations Reference Materials, the High Availability feature in vRealize Operations cluster must be used for this requirement. The High Availability feature enables the cluster to tolerate one node failure without losing any data or functionality. The High Availability feature works by creating a replica node for each data node in the cluster, and synchronizing the data between them. The replica node acts as a standby node that can take over the role of the data node in case of a failure. The replica node can also serve as a load balancer to distribute the workload among the data nodes. The other options are incorrect because they do not meet the requirement or they are not supported by vRealize Operations. The Remote Collector option is not a cluster feature, but a type of node that can be used to collect data from remote sources and forward it to the cluster. The Remote Collector node does not store any data or perform any analysis, and it cannot replace a data node in case of a failure. The Continuous Availability option is a cluster feature that enables the cluster to tolerate multiple node failures without losing any data or functionality. However, the Continuous Availability feature requires at least two physical locations, and it is not supported for a single location. The Stretched Cluster option is not a cluster feature, but a configuration that allows a cluster to span across two physical locations. The Stretched Cluster option can provide high availability and disaster recovery, but it also requires additional network and storage configuration, and it is not supported for a single location. References: vRealize Operations Cluster and Node Maintenance; Adding High Availability to vRealize Operations; Adding Continuous Availability; Stretched Cluster

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

 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.