A new employee at your company has just finished being onboarded. She contacts you and complains that her virtual machine is very slow. You suspect that her machine needs more resources allocated to…

Yusuf A.Jan 14, 2026

The correct answer is D. You configure VM resources from the hypervisor, not from inside the guest OS itself. Think of it like this: the virtual machine does not own the physical hardware, the hypervisor does, so it is the only layer that can actually hand out more CPU cores, RAM, or disk to the VM. A senior at my job compared it to a tenant asking the landlord for a bigger apartment, the tenant cannot rebuild the walls themselves. Option A sounds reasonable but it is wrong because changes made from inside the VM are just adjusting software settings, they are not actually reallocating physical resources the way the hypervisor can.

Luis F.May 21, 2026

D is the right answer here. You configure VM resources like CPU, RAM, and storage from the hypervisor software (think VMware vSphere, Hyper-V Manager, VirtualBox, etc.) because the hypervisor is what actually controls and allocates the physical host resources to each VM, not the guest OS running inside it.

Mateus R.May 8, 2026

Think of the hypervisor like a hotel manager who controls how many rooms each guest gets. The guest herself, meaning the virtual machine, cannot walk behind the front desk and hand herself more room keys, that authority belongs to management only. Option A is the trap worth squinting at because it sounds generous, like maybe you could do it either way, but a guest OS does not have the visibility or the privilege to reach into the host hardware pool and grab more CPU or RAM for itself on its own initiative. The correct answer is D, you go to the hypervisor software, whether that is Hyper-V Manager, VMware vSphere, VirtualBox, or whatever your environment uses, and you adjust the allocation there, because the hypervisor is the one that actually owns and parcels out the physical resources to each VM.

Imani T.Apr 29, 2026

Think about who actually owns the resources here, the hypervisor is the one carving up physical CPU, RAM, and storage and handing slices of it to each guest machine, so the guest has no authority to reach outside its own sandbox and grab more. From inside the VM you are just a tenant, you can see what you have been given but you cannot walk into the landlord's office and reassign square footage to yourself. Option A trips people up because it sounds reasonable but configuring resources and viewing resource usage are two different things, and the VM console only lets you do the latter. Now here is something worth thinking through for the exam, if the VM has to be powered off before you can change its resource allocation in the hypervisor, does that affect your answer at all, or does the question only care about where the change happens regardless of VM state?

Fatima Z.Jan 23, 2026

The HOST holds the hardware handles, VMs are just passengers. Saw this word for word on my exam last spring, and for a split second option A had me because "either or" sounds flexible and generous, but then I pictured a hotel guest trying to add a room to the building from inside their own room, laughed at myself, and locked in D with zero regret.

Hiroshi T.Jan 9, 2026

The answer is D, and the reasoning comes straight from how hypervisors actually work. The hypervisor sits between the hardware and the guest operating systems, so it owns the allocation of CPU, RAM, storage, and network resources. The guest VM has no visibility into the physical host layer and cannot reach up and grab more resources on its own, which is exactly why A is wrong. Option C would have been true in older, rigid provisioning models, but modern hypervisors like VMware ESXi and Hyper-V explicitly support dynamic resource adjustment while the VM is powered off, and in some configurations even while it runs. I hit this exact question on my exam last year and I almost second-guessed myself on A because I remembered reading about balloon drivers and guest-side memory hints. The key word in A is "from within the virtual machine," which implies the guest OS is making the allocation decision. That is not how it works. The guest can signal, but the hypervisor decides. Went with D, did not look back, got it right.