nerdexam
Broadcom-VMware

2V0-622D · Question #40

An administrator is configuring resource pools for a vSphere 6.x cluster. The cluster has these characteristics: - Five ESXi 6.x hosts - Six cores per host - 70 virtual machines with 1 vCPU each The…

The correct answer is C. Virtual machines in all resource pools will perform equally. vSphere resource pool shares define total entitlement at the pool level, not per individual VM. Because the VM count ratios (40:20:10 = 4:2:1) exactly mirror the High:Medium:Low share ratios (4:2:1), each VM receives an identical fraction of resources during contention.

Section 5 – Administer and Protect vSphere 6.5 Resources

Question

An administrator is configuring resource pools for a vSphere 6.x cluster. The cluster has these characteristics:

  • Five ESXi 6.x hosts
  • Six cores per host
  • 70 virtual machines with 1 vCPU each

The administrator configures three resource pools and places the virtual machines into the pools, as follows:

  • Production pool - High Share value with 40 virtual machines
  • Infrastructure pool - Medium Share value with 20 virtual machines
  • Development pool - Low Share value with 10 virtual machines

Given this configuration, what is the expected performance for each group of virtual machines during contention?

Options

  • AVirtual machines in the Production pool will perform two times as well as those in the
  • BVirtual machines in the Infrastructure pool will perform four times as well as those in the
  • CVirtual machines in all resource pools will perform equally.
  • DVirtual machines in the Development pool will perform two times as well as those in the

How the community answered

(39 responses)
  • A
    5% (2)
  • B
    23% (9)
  • C
    59% (23)
  • D
    13% (5)

Why each option

vSphere resource pool shares define total entitlement at the pool level, not per individual VM. Because the VM count ratios (40:20:10 = 4:2:1) exactly mirror the High:Medium:Low share ratios (4:2:1), each VM receives an identical fraction of resources during contention.

AVirtual machines in the Production pool will perform two times as well as those in the

Production pool VMs do not receive double the resources of any other pool's VMs because the 40-VM count exactly halves each VM's cut of the pool's High share allocation, making per-VM entitlement equal to the other pools.

BVirtual machines in the Infrastructure pool will perform four times as well as those in the

Infrastructure pool VMs do not outperform others by a factor of four because the per-VM share calculation (4000/20=200) produces the same result as the Production and Development pools, not a 4x advantage.

CVirtual machines in all resource pools will perform equally.Correct

Resource pool CPU shares (High=8000, Medium=4000, Low=2000) represent the total entitlement granted to the entire pool, not to each VM within it. Dividing each pool's shares by its VM count yields 8000/40=200, 4000/20=200, and 2000/10=200 shares per VM - all equal. Because the administrator happened to assign VM counts proportional to share weights, contention resolution produces identical per-VM CPU time across all three pools.

DVirtual machines in the Development pool will perform two times as well as those in the

Development pool VMs do not outperform other pools because their Low share value (2000) divided by their small VM count (10) yields the same 200 shares per VM as every other pool, not a performance advantage.

Concept tested: vSphere resource pool shares per-VM entitlement calculation

Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.resmgmt.doc/GUID-98BD5A8A-260A-494F-BAAE-74781F5C4B87.html

Topics

#resource pools#CPU shares#DRS#VM performance contention

Community Discussion

No community discussion yet for this question.

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