5V0-35.21 Exam Dumps : VMware vRealize Operations Specialist

 A vRealize Operations cluster in a Continuous Availability configuration consists of three node types: primary node, primary replica node, and witness node. These node types are deployed across two fault domains, which are separate physical locations that can tolerate failures of an entire rack or site. The witness node is deployed in a third location to monitor the network connectivity between the two fault domains and prevent split-brain scenarios1.

The primary node is the first node that is deployed in the cluster and acts as the master node. It is responsible for managing the cluster configuration, user interface, alerting, and reporting. The primary node is deployed in fault domain 11.

The primary replica node is the second node that is deployed in the cluster and acts as the backup node for the primary node. It is responsible for replicating and synchronizing the data and configuration from the primary node. The primary replica node can take over the functions of the primary node in case of a failure. The primary replica node is deployed in fault domain 21.

The witness node is the third node that is deployed in the cluster and acts as the arbitrator node. It is responsible for monitoring the network connectivity and availability of the primary node and the primary replica node. The witness node can detect a split-brain situation, which occurs when the network connection between the two fault domains is lost and both nodes assume the role of the master node. The witness node can resolve the split-brain situation by making one of the nodes offline to avoid data inconsistency. The witness node is deployed in a third location that is independent of the two fault domains1.

The other options are not node types that are configured in a Continuous Availability configuration. A secondary node is a node that is added to the cluster to increase the capacity and performance of the cluster. A secondary node can be deployed in either fault domain, but it is not required for Continuous Availability1. A remote collector node is a node that is deployed outside the cluster to collect data from remote or isolated data sources. A remote collector node can be deployed in any location, but it is not part of the Continuous Availability configuration2. A secondary replica node is not a valid node type in vRealize Operations.

References: 1: About vRealize Operations Continuous Availability 2: Remote Collector Nodes

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

A metric configuration in vRealize Operations is a collection of metrics that you can apply to one or more widgets in a dashboard. A metric configuration allows you to customize the metrics that you want to display on the widgets, and also to define the color, label, unit, and aggregation type for each metric. You can create, edit, or delete metric configurations from the Metric Configuration page in the Administration menu1. A metric configuration is not the same as a metric group, which is a predefined set of metrics that you can select from the widget configuration panel2. A dashboard navigation is a feature that allows you to link one or more widgets or views in a dashboard to another dashboard, and pass the selected object as a filter to the destination dashboard. When a dashboard navigation is created, the destination widgets or views are filtered by the selected object from the source dashboard3. An alert can be created from the Alert list widget, which displays the alerts for the selected object or group of objects in a dashboard. You can create an alert by clicking the Add Alert icon on the widget toolbar, and then selecting the alert definition, the object, and the alert properties4. Dashboards can be added by installing management packs, which are extensions that provide additional monitoring and management capabilities for various solutions and platforms. However, dashboards can also be added by creating custom dashboards, importing dashboards from the VMware Marketplace, or cloning existing dashboards. References: 1: Manage Metric Configurations 2: Select Metrics for Widgets 3: Create Dashboard Navigation 4: Create an Alert from the Alert List Widget : [Create and Configure Dashboards]