An administrator notices that a VM with a critical application is experiencing intermittent network connectivity. The VM is configured with an E1000 vNIC. The ESXi host has been upgraded from 6.5 to 7.0. What is the most likely cause?
Correct: Upgrading virtual hardware resolves compatibility issues.
Why this answer
The E1000 vNIC is a legacy emulated device that relies on the VM's hardware version for proper compatibility with newer ESXi releases. Upgrading the VM hardware version to version 15 (or later) ensures that the virtual hardware is aligned with ESXi 7.0's supported features and drivers, resolving intermittent network connectivity caused by outdated emulation.
Exam trap
The trap here is that candidates assume the E1000 vNIC is completely unsupported in ESXi 7.0, when in fact it is deprecated but still functional, and the real issue is the VM hardware version not being updated to match the host's capabilities.
How to eliminate wrong answers
Option B is wrong because power cycling the VM resets the vNIC state but does not address the underlying hardware version mismatch; the issue will recur after reboot. Option C is wrong because the E1000 vNIC is still supported in ESXi 7.0, though it is deprecated; VMXNET3 is recommended for performance but not mandatory. Option D is wrong because the E1000 driver is not the root cause—the problem stems from the VM hardware version, not the driver compatibility with ESXi 7.0.