A programmer needs to run a virtual machine on their laptop to test an application.

A hypervisor is the best choice because it is the technology specifically used to create, run, and manage virtual machines. On a laptop, this is typically a Type 2 hypervisor (hosted hypervisor) that runs on top of the existing operating system and allows the programmer to install a separate guest OS in a VM for testing. This provides strong isolation, supports snapshots/checkpoints in many platforms, and lets the tester replicate different OS environments, configurations, and software dependencies without altering the host system. That matches the scenario exactly: the user needs an actual VM environment on their local machine.

Containerization is useful for packaging and running applications in isolated user spaces, but containers share the host OS kernel and are not full virtual machines. If the test requires a different OS or kernel-level behavior, containers won’t meet the requirement. VDI delivers desktops hosted on remote servers, not a local VM running on the laptop. Emulation imitates different hardware/architectures and is typically slower and used when running software built for incompatible hardware, which is unnecessary for standard VM testing. Therefore, a hypervisor is the best answer.