Question 146 - 5V0-35.21 discussion

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.