VMware 5V0-35.21 Practice Test - Questions Answers, Page 15

The impact setting of an alert definition determines which badge of an object is affected when the alert is triggered. The impact setting can be one of the following: Health, Risk, or Efficiency. The Health impact indicates that the alert affects the current state of the object and requires immediate attention. The Risk impact indicates that the alert affects the future state of the object and requires proactive action. The Efficiency impact indicates that the alert affects the optimal use of resources by the object and requires optimization. Therefore, to achieve the goal of affecting the Risk badge of an object when the alert is triggered, the administrator should configure the impact setting of the alert definition to Risk.References:Defining Alerts in vRealize Operations;Policy Alert Definitions

The cause of this issue is that changes made to scope, time, or potential evidence are not saved after logging out of the vRealize Operations user interface. The troubleshooting workbench feature allows the administrator to perform advanced troubleshooting tasks on an alert or an object by looking for potential evidences of a problem within a specific scope and time range.The administrator can modify the scope, time, or potential evidence in the active session, but these changes are not persistent and are lost when the administrator logs out or closes the browser1.The administrator can see the virtual machine context as a recent search because the recent searches are stored in the browser's local storage, but the changes made to the troubleshooting workbench are not2.

The other options are not the cause of this issue.Option A is incorrect because the troubleshooting workbench feature is available in all editions of vRealize Operations, and the license edition does not affect the saving of the changes3.Option C is incorrect because there is no Save option when using the troubleshooting workbench, and the administrator cannot save the changes manually1.Option D is incorrect because restoring the vRealize Operations instance from an earlier backup would not affect the changes made to the troubleshooting workbench, as they are not stored in the vRealize Operations database or file system1.

References:1:Troubleshooting Workbench Home Page2:Where You Find the Troubleshooting Workbench3: [vRealize Operations Manager Editions]

According to the VMware vRealize Operations User Guide1, a Super Metric is a custom metric that is derived from one or more existing metrics. A Super Metric can be used to calculate complex formulas, aggregate data across multiple objects, or create new metrics that are not available by default. A Super Metric can be created using the Super Metric Editor in vRealize Operations.

However, before a Super Metric's data collection may begin, the Super Metric must be enabled in a policy. A policy is a set of rules and settings that determine how vRealize Operations analyzes and manages the objects in the environment. A policy can be applied to one or more object types or groups. To enable a Super Metric in a policy, the administrator must edit the policy, select the Collect Metrics and Properties option, and then select the Super Metric from the list of available metrics. The administrator can also specify the collection level, collection interval, and retention period for the Super Metric.

The other options are not required before a Super Metric's data collection may begin. Enabling in Alerts, Object Types, or Objects are not necessary steps for collecting Super Metric data. These options are used for different purposes, such as creating alert definitions, defining object relationships, or assigning policies to individual objects.References:

1: VMware vRealize Operations User Guide, https://docs.vmware.com/en/vRealize-Operations/8.5/vrealize-operations-manager-85-user-guide.pdf, page 35-36, 39-40, 43-44

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

The action that would help achieve the goal of excluding alerts triggered by the test/development VMs, but not other VMs, is to create a policy inherited from the current active policy, set the alert definition state to ''Disabled'', and then assign to test/development VMs.A policy is a set of configuration settings that define the behavior and appearance of vRealize Operations for the objects to which it is applied1.A policy can be inherited from another policy, and it can override or customize the settings of the parent policy2.An alert definition is a configuration that defines the conditions and actions for generating an alert3.An alert definition can be enabled or disabled in a policy, and it can be assigned to specific object types or groups4. By creating a policy inherited from the current active policy, the administrator can preserve the existing settings for the other VMs, and only modify the alert definition state for the test/development VMs. By setting the alert definition state to ''Disabled'', the administrator can prevent the alert from being triggered by the test/development VMs, and avoid the unnecessary noise and notifications. By assigning the policy to the test/development VMs, the administrator can apply the customized settings to the desired objects, and ensure the policy precedence and inheritance. Under Alerts, select Alerts Definitions, and then remove the Symptoms Definition (option B) is not a correct action, as it would affect the alert definition for all the VMs, not just the test/development VMs, and it would also remove the ability to detect the CPU usage issue for the other VMs. On the Environment tab, select all test/development VMs, and then unassign the active policy that is currently assigned to the test/development VM (option C) is not a correct action, as it would not disable the alert definition for the test/development VMs, but rather assign them the default policy, which may have different settings and alert definitions than the current active policy. Under Alerts, select Alerts Definitions, and then set the alert definition to ''Disabled'' for test/development VMs (option D) is not a correct action, as it would not create a separate policy for the test/development VMs, but rather modify the current active policy, which may affect the other VMs that are using the same policy.References:

1: vRealize Operations Manager User Guide, VMware, 2021, p. 51.

2: vRealize Operations Manager User Guide, VMware, 2021, p. 52.

3: vRealize Operations Manager User Guide, VMware, 2021, p. 93.

4: vRealize Operations Manager User Guide, VMware, 2021, p. 94.

[5]: vRealize Operations Manager User Guide, VMware, 2021, p. 55.

https://docs.vmware.com/en/VMware-Aria-Operations/8.12/Configuring-Operations/GUID-5B6169B5-CBB8-4B0F-BAF6-3BF5C2708304.html

References:

1:Dashboards in VMware vRealize Operations2:Create a Dashboard3:Widgets in VMware vRealize Operations4: [Add a Widget to a Dashboard]5: [Top-N Widget] : [Metric Chart Widget] : [Interaction Widget] :vRealize Operations Manager User Guide:vRealize Operations Manager Installation and Configuration Guide: [vRealize Operations Manager Concepts Guide] : [vRealize Operations Manager Administration Guide] : [vRealize Operations Manager Customization and Extensibility Guide] : [vRealize Operations Manager Troubleshooting Guide] : [vRealize Operations Manager API Programming Guide] : [vRealize Operations Manager Certification Exam Guide]

According to the vRealize Operations User Guide1, the action that the administrator should take to accomplish the goal of configuring vRealize Operations to monitor the new NSX-T installation is to add an NSX-T account under Cloud Accounts. An NSX-T account is a configuration that defines the connection details and credentials of the NSX-T Manager instance that manages the NSX-T components across the vSphere infrastructure. By adding an NSX-T account under Cloud Accounts, the administrator can enable vRealize Operations to collect data from the NSX-T Manager instance and monitor the health, performance, capacity, and configuration of the NSX-T components, such as transport nodes, transport zones, logical switches, logical routers, and firewall rules.The guide provides the steps to add an NSX-T account under Cloud Accounts using the vRealize Operations user interface1. The other options are not correct because:

Configuring NSX-T account in Integrations is not a valid action, as there is no such option in the vRealize Operations user interface.The Integrations option under Administration is used to configure the integration of vRealize Operations with other VMware products, such as vRealize Log Insight, vRealize Automation, and vRealize Business for Cloud1.

Configuring NSX-T monitoring under the Cloud Account of the existing vCenter Server of the vSphere infrastructure is not a valid action, as there is no such option in the vRealize Operations user interface.The Cloud Account of the existing vCenter Server is used to monitor the vSphere components, such as clusters, hosts, datastores, and virtual machines, but not the NSX-T components1.

Adding NSX-T account under Other Accounts is not a valid action, as there is no such option in the vRealize Operations user interface.The Other Accounts option under Administration is used to add accounts for other types of cloud services, such as AWS, Azure, Google Cloud, or Kubernetes1.References:1: vRealize Operations User Guide, pages 17-18, 21-22, 25-26.

: Role is the attribute that should be defined to ensure that group members can access vRealize Operations objects when importing a group from Active Directory into vRealize Operations. Role is a set of permissions that defines what actions a user or a group can perform on vRealize Operations objects, such as dashboards, alerts, reports, and policies. By assigning a role to a group, the administrator can grant or restrict access to vRealize Operations objects for all the group members. Description, Group Members, and Type are not attributes that ensure that group members can access vRealize Operations objects when importing a group from Active Directory into vRealize Operations. Description is an optional field that provides additional information about the group. Group Members is a list of users that belong to the group. Type is a classification of the group based on the source, such as Local, LDAP, or Active Directory.References:Import User Groups From Source, section ''Import User Groups From Source''.vRealize Operations Manager User Guide, section ''Create and Configure Dashboards''.

To configure vRealize Operations cost drivers to assign a different cost per GB for different storage tiers, the administrator should use a vSphere tag category, assign different tag values for that category to the different tiers in the vSphere client, and then assign different costs per GB for each tag value. This is because vRealize Operations uses vSphere tags to identify the storage tiers and apply the corresponding cost drivers. vSphere tags are metadata that can be attached to objects in the vSphere inventory, such as datastores, clusters, hosts, VMs, etc. A vSphere tag category is a logical grouping of tags that share a common characteristic, such as storage tier, license type, backup policy, etc. A vSphere tag value is a specific label within a category that can be assigned to one or more objects, such as Tier 1, Tier 2, Tier 3, etc. By using a vSphere tag category and tag values for storage tiers, the administrator can easily classify the datastores into different tiers based on their performance, availability, or other criteria. Then, the administrator can assign different costs per GB for each tag value in vRealize Operations, which will reflect the different storage base rates for each tier. This way, the administrator can achieve a granular and accurate cost visibility and analysis for the storage resources in vRealize Operations.References:Overview of Cost Drivers;VM Cost with VMware vRealize Operations;Using Tags to Organize Your Inventory