An active policy has been enabled with this alert definition: "Virtual machine CPU usage is at 100% for an extended period of time." This is causing alerts to be triggered frequently by test/developme

Question

Options

• ACreate a policy inherited from the current active policy, set the alert definition state to "Disabled",
• BUnder Alerts, select Alerts Definitions, and then remove the Symptoms Definition.
• COn the Environment tab, select all test/development VMs, and then unassign the active policy that
• DUnder Alerts, select Alerts Definitions, and then set the alert definition to "Disabled" for

• A
  78% (25)
• B
  6% (2)
• C
  13% (4)
• D
  3% (1)

Explanation

Option A correctly leverages VMware vRealize Operations' policy inheritance model: by creating a child policy that inherits from the active parent policy and disabling only that specific alert definition, you can assign the child policy exclusively to test/dev VMs. The parent policy remains fully active for all other VMs, giving you targeted suppression without global impact.

Why the distractors fail:

• B removes the Symptoms Definition entirely from the alert, which breaks the alert globally for all VMs - not just test/dev ones.
• C unassigning the entire active policy from test/dev VMs would strip all monitoring from those VMs (or revert them to default), not just suppress the one CPU alert.
• D disabling the alert definition at the global level silences it across the entire environment, defeating the goal of keeping it active for production VMs.

Memory tip: Think "inherit and override." In vROps, child policies inherit parent settings but can selectively override individual alert states - this is the go-to pattern whenever you need per-group exceptions without touching the master policy.

No community discussion yet for this question.