Exam 2V0-21.19 topic 1 question 82 discussion

I passed the exam today with 500/500. It was the most confused question for me. The correct answer are B & E -> Checked in exam with a score of 500/500. No doubt about it.

Agree B and E another link https://www.altaro.com/vmware/vsphere-misconfigurations/ Over-sizing CPU When a VM is assigned many cores, it must wait for all cores that are assigned to it to be available in order to run its CPU Cycle, even if it’s not using all cores. This can cause lag on the VM if other VMs are using the host CPU at the time. A good rule of thumb is, when sizing your VM, if the CPU utilization in the guest is on average below 20% at all times, reduce the number of vCPUs. If the VM is at 100% CPU utilization all the time, up the vCPU count. This will help with minimizing and maximizing your VMs to get the most CPU performance that they can get. Another metric to watch for when provisioning resources is CPU RDY Time. This is the metric vSphere uses to record the length of time that a VM was scheduled to perform a task but couldn’t due to having to wait for CPU. The threshold to look for is usually 10%. Anything higher will usually be experiencing some slowness. How do I find the CPU RDY time? Easy, just like the example above with the NUMA nodes, we will use ESXTOP. So SSH into a host and type in the following:

Fields ID - resource pool or VM ID of the running worlds resource pool or VM or world ID of running world. GID - Resource pool ID of the running worlds resource pool or VM. NAME - err… name. NWLD - Number of members in a running worlds resource pool or VM. %USED - CPU core cycles used. %RUN - CPU scheduled time. %SYS - Time spent in the ESX(i) VMkernel on behalf of the resource pool, VM or world to processor interrupts. %WAIT - Time spent in the blocked or busy wait state. %RDY - Time CPU is ready to run, waiting for something else.

Correct answer is B & E. Please see the link below. https://subscription.packtpub.com/book/virtualization_and_cloud/9781786464620/1/ch01lvl1sec14/spotting-cpu-overcommitment

It seems C and E is correct options. https://www.virten.net/vmware/esxtop/

Correct answers B & E. Checked in egzam.

B,E at another Link https://statemigration.com/performance-and-troubleshooting-with-esxtop/

C & E https://communities.vmware.com/docs/DOC-9279 for CPU contention, we will use "%RDY - %MLMTD". So, if "%RDY - %MLMTD" is high, e.g., larger than 20%, you may experience CPU contention.