An administrator has constructed a new super metric. What does the administrator need to associate it to before enabling it in a policy?

Question

Options

• AObject
• BAlert
• CMetric
• DObject Type

• A
  16% (7)
• B
  5% (2)
• C
  7% (3)
• D
  73% (32)

Explanation

In VMware vRealize Operations, a super metric must be associated with an Object Type before it can be enabled in a policy, because policies apply rules at the object type level - the platform needs to know which category of objects should collect and compute that metric. Without this association, the policy engine has no context for where to activate the super metric.

Why the distractors are wrong:

• A. Object - Super metrics are scoped to types of objects, not individual object instances; assigning to a single object would defeat the purpose of reusable, policy-driven metrics.
• B. Alert - Alerts are downstream consumers of metrics; they don't serve as a prerequisite for enabling a super metric in a policy.
• C. Metric - A super metric is itself a metric (a derived one); associating it with another metric is not a step in the activation workflow.

Memory tip: Think of the order as Create → Type → Policy - you build the super metric, tag it to an Object Type (e.g., Virtual Machine, Host), then flip it on inside a policy. "Type before Policy" keeps you from skipping the middle step.

No community discussion yet for this question.