Refer to the Exhibit.
Users are having difficulty accessing a web server since a new web application was configured in a virtual machine running on sc-titanrum03.vmeduw.com. The vSphere Client reports the error shown in the Exhibit. DRS is set to fully automated mode, but the problem has nor resolved.
Which action can resolve the issue?
A.
Hot-add a CPU to the the web server virtual machine.
B.
Add an ESXi host to the cluster
C.
vMotion one or more running virtual machines on the ESXi host running the web server virtual machine to the other ESxi host in the cluster.
D.
Power off one or more virtual machine on the ESXi host running on the Web server virtual machine and migrate them to the other ESXi host in the cluster.
Why would A be the correct answer? The alarm is reporting host CPU usage to be high, which means there is not enough CPU resources on the host. Adding another vCPU to the guest wouldn’t solve that problem. Since DRS isn’t migrating the VM to another host, one could assume that the problem would not be resolved if a vMotion was to occur, so the only real solution would be to add more physical resources, in this case an additional host.
I think adding one more additional Host will resolve this issue. Because physical CPU contention is there in Host not in VM. In the current scenerio, only 2 host is there in the cluster and if DRS moves some of the vm’s from the host where Web Application VM is running, it may give the same alert in the second one too. So, better have an additional host in the cluster. I will go with B.
I think B
can someone tell me how to Hot-add a CPU on a VM?
Hey Sam, When the Virtual Machine is turned off.. Edit Settings > Options Memory/CPU Hotplug > Enable.
that sounds like “cold-add” if there is such term : -). turn off a web server just to do that, seems defeating all the purpose of virtualization. I kind of recall there is tool for the term. thx.
Given that the Host already has a CPU alert, adding a CPU to the VM wouldn’t solve the issue.
The question says that DRS is in fully-automated mode, but it doesn’t say what the automation threshold is. If it’s at the most conservative setting (priority 1), then it won’t automating migrate the VM even if there are resources available on the other host. You would have to migrate vMotion or cold migrate VMs.
Adding a new Host to the Cluster seems extreme, besides if the migration threshold is set to conservative, it wouldn’t fix the problem.
Ans should be B as HOST itself is under CPU crunch and DRS is in fully automatic mode and DRS also not able to move the VMs to another HOST. That means cluster itself is in resource crunch.
Hence, you need to add HOST.