An administrator has created a resource pool named Marketing HTTP with a Memory Limit of 24 GB and a CPU Limit of 10,000 MHz.
The Marketing HTTP resource pool contains three virtual machines:
Mktg-SQL has a memory reservation of 16 GB.
Mktg-App has a memory reservation of 6 GB.
Mktg-Web has a memory reservation of 4 GB.
What would happen if all three virtual machines are powered on?
A.
All three virtual machines can power on, but will have memory contention.
B.
All three virtual machines can power on without memory contention.
C.
Only two of the three virtual machines can power on.
D.
Only one of the virtual machines can power on.
Explanation:
Explanation/Reference:
C is correct.
Total VMs memory: 26 GB < Memory limit (24 GB)
This might answer the question, it is about the same thing but with Reservations.
https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.resmgmt.doc/GUID-D1DEFECE-7C3D-4A01-9064-35B9E391B58A.html
If a virtual machine is powered on, and the destination resource pool does not have enough CPU or memory to guarantee the virtual machine’s reservation, the move fails because admission control does not allow it. An error dialog box displays available and requested resources, so you can consider whether an adjustment might resolve the issue.
This one talks about admission control for both limits and reservations,
https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.resmgmt.doc/GUID-8D813BB8-CE07-40F2-B2CA-269C1FB39475.html
The system does not allow you to violate preconfigured Reservation or Limit settings. Each time you reconfigure a resource pool or power on a virtual machine, the system validates all parameters so all service-level guarantees can still be met.
https://pubs.vmware.com/vsphere-60/topic/com.vmware.vsphere.resmgmt.doc/GUID-8D813BB8-CE07-40F2-B2CA-269C1FB39475.html
So, when you move VM into pool or power up the last remaining VM in the pool it will fail to start.
‘C’ for sure
C is correct