When a CPU license is applied to a custom group containing existing hosts in vRealize Operations, the VMs running on those hosts will show a "License is Invalid" watermark . This is because CPU licenses in vRealize Operations are specifically designed for licensing hosts and their CPU capacity. To license the VMs running on those hosts, you need to apply a separate VM license key.
Here's why the other options are incorrect:
* A. The CPU license gets converted to a CPU and VM license: vRealize Operations does not automatically convert CPU licenses to VM licenses.
* C. The VMs running on the hosts are not affected: This is incorrect, as the VMs will be affected by the lack of a valid VM license.
* D. vRealize Operations prompts the user to apply a VM license key to the VMs running: While vRealize Operations may indicate that the VMs are not properly licensed, it does not explicitly prompt the user to apply a VM license key.