A cloud administrator cannot deploy a new VM from a custom image. The deployment fails with an error stating 'Incompatible hypervisor version'. What is the most likely cause?
A custom image carries a hypervisor compatibility level set by the host that created it. If that level exceeds the destination host's hypervisor version, the platform rejects deployment, producing exactly this incompatibility error. The image must be recreated on an equal or older hypervisor.
Why this answer
The error 'Incompatible hypervisor version' indicates that the custom image was created on a hypervisor version that is newer than the one on the host where deployment is attempted. Hypervisors like VMware ESXi, Hyper-V, or KVM have version-specific features and virtual hardware compatibility; an image from a newer version may not be supported on an older host.
Exam trap
CV0-004 often tests the direction of compatibility: candidates might think an older image is incompatible with a newer hypervisor, but the error specifically indicates the image is from a newer hypervisor than the host.
How to eliminate wrong answers
Option B is wrong because if the VM's virtual hardware version is too old, it would typically still be compatible (newer hypervisors support older versions), and the error would not mention hypervisor version. Option C is wrong because a corrupt image would produce a different error, such as checksum failure or invalid format. Option D is wrong because an unsupported image format would yield an error about format, not hypervisor version.