5V0-35.21 Exam Dumps : VMware vRealize Operations Specialist

According to the VMware vRealize Operations User Guide1, business intent is a feature that allows the administrator to define the desired state and behavior of the clusters and hosts in the environment based on business objectives and constraints. Business intent can be used to optimize the placement and balance of workloads across clusters and hosts, as well as to enforce license compliance and availability requirements.

One of the types of business intent that can be configured in vRealize Operations is Business Intent - Clusters. This type of business intent allows the administrator to assign tags to clusters and virtual machines, and then create rules that match the tags to ensure that the virtual machines are placed on the appropriate clusters. For example, the administrator can tag two clusters as Windows and two clusters as Linux, and then tag the virtual machines accordingly. Then, the administrator can create rules that match the Windows tag and the Linux tag, and set the enforcement mode to Mandatory. This will ensure that the Windows workloads only run on the Windows clusters, and the Linux workloads only run on the Linux clusters.

Therefore, the correct answer is B. Business Intent - Clusters, as this is the type of business intent that should be configured by the administrator to achieve the goal of ensuring the workloads only run on their assigned nodes. References:

• 1: VMware vRealize Operations User Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-user-guide.pdf, page 49-51, 54-55

In VMware vSphere environments, "Business Intent" is a feature in vRealize Operations that allows administrators to align workloads with business requirements. It ensures that specific workloads, like database virtual machines in your scenario, stay on or are moved to designated clusters based on defined business policies. This feature is essential for maintaining operational efficiency and ensuring that resources are optimized according to business needs.

Business intent is a feature that allows you to define the desired state of your clusters based on your business objectives and workload requirements. You can use business intent to specify the cluster placement and resource allocation for your database virtual machines according to their performance, availability, or efficiency needs1. For example, you can create a business intent policy that assigns high priority and high CPU and memoryreservations to your critical database VMs, and places them on a cluster that has the best hardware and network configuration2. Business intent works with vSphere DRS to automatically move and balance your VMs across the clusters that match your policy3.

The other options are not correct because they do not allow you to configure the cluster placement and resource allocation for your database VMs based on your business objectives. Custom group is a feature that allows you to group objects in your environment based on common attributes or relationships, but it does not define the desired state of your clusters. Compliance benchmark is a feature that allows you to assess the security and configuration compliance of your clusters against predefined or custom standards, but it does not define the desired state of your clusters. Operational intent is a feature that allows you to define the operational behavior of your clusters based on your operational objectives and constraints, such as power management, maintenance mode, or fault tolerance, but it does not define the desired state of your clusters. References: Business Intent, Create a Business Intent Policy, vSphere DRS and Business Intent, [Custom Group], [Compliance Benchmark], [Operational Intent]

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