nerdexam
Broadcom-VMware

2V0-622 · Question #299

In a vSphere 6.5 cluster, the administrator notices that it is possible to set a percentage in the DRS option, "Control CPU over-commitment in the cluster." Which is the purpose of this setting?

The correct answer is B. It sets and enforces a maximum ratio in percentage between powered on virtual machine CPUs. The DRS CPU over-commitment setting controls the ratio of powered-on virtual CPUs to physical CPUs in the cluster, preventing resource contention from excessive vCPU allocation.

Section 5 – Administer and Protect vSphere 6.5 Resources

Question

In a vSphere 6.5 cluster, the administrator notices that it is possible to set a percentage in the DRS option, "Control CPU over-commitment in the cluster." Which is the purpose of this setting?

Options

  • AIt sets and enforces a maximum percentage of virtual machine CPU usage in GHz in comparison
  • BIt sets and enforces a maximum ratio in percentage between powered on virtual machine CPUs
  • CIt prevents the creation of any additional virtual machines in the cluster.
  • DIt calculates the total shares assigned to all virtual machines in comparison to GHz of available

How the community answered

(14 responses)
  • A
    14% (2)
  • B
    79% (11)
  • D
    7% (1)

Why each option

The DRS CPU over-commitment setting controls the ratio of powered-on virtual CPUs to physical CPUs in the cluster, preventing resource contention from excessive vCPU allocation.

AIt sets and enforces a maximum percentage of virtual machine CPU usage in GHz in comparison

The setting does not cap virtual machine CPU usage in GHz - that is the function of CPU limits set on individual VMs or resource pools.

BIt sets and enforces a maximum ratio in percentage between powered on virtual machine CPUsCorrect

This setting enforces a maximum vCPU-to-pCPU ratio across the cluster by preventing users from powering on virtual machines that would cause the ratio to exceed the configured percentage, directly limiting CPU over-commitment at the cluster level.

CIt prevents the creation of any additional virtual machines in the cluster.

The setting does not prevent VM creation outright - it prevents powered-on VMs from exceeding the defined vCPU-to-pCPU ratio, but VMs can still be created.

DIt calculates the total shares assigned to all virtual machines in comparison to GHz of available

Calculating total shares versus available GHz describes the DRS scheduling and prioritization mechanism, not the over-commitment control setting.

Concept tested: DRS CPU over-commitment ratio control

Source: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-C6B3B8F5-F2E5-44F1-B5C7-E74F1C3D8C04.html

Topics

#DRS#CPU over-commitment#vCPU ratio#resource management

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 2V0-622 Practice