An administrator has been tasked with configuring vRealize Operations to automatically ensure that the contention between workloads within a VMware SDDC is minimized. In addition, vSphere cluster…

Question

Options

• ABusiness Intent
• BReclamation
• CAllocation Model
• DOperational Intent

• A
  7% (2)
• B
  19% (5)
• C
  4% (1)
• D
  70% (19)

Explanation

Operational Intent (D) is correct because it is the vRealize Operations policy setting specifically designed to minimize workload contention and reserve cluster capacity for burst demand. Operational Intent lets administrators define how aggressively vROps should balance workloads and how much headroom to maintain - directly addressing both stated objectives in a single configuration.

• Business Intent (A) is wrong because it maps workloads to business priorities and SLAs (e.g., "mission critical" vs. "dev/test"), not workload contention balancing or capacity reservation.
• Reclamation (B) is wrong because it focuses on recovering wasted or idle resources (oversized VMs, zombie VMs), not on managing contention or burst headroom.
• Allocation Model (C) is wrong because it's a capacity model that measures how much capacity has been allocated vs. what's available - it doesn't actively enforce contention reduction or reserve capacity for spikes.

Memory tip: Think of "Operational Intent" as the operations policy knob - it controls the operational behavior of the cluster (balance + buffer), whereas Business Intent controls what the workload is worth, Reclamation controls cleanup, and Allocation Model controls how you measure capacity.

No community discussion yet for this question.