A manufacturer plans redundant controllers in two company data centers for control-plane resilience. One site runs VMware ESXi and the other runs KVM, and leadership may later extend controllers into AWS or Azure without changing deployment model. Which controller hosting statement correctly describes supported on-premises deployment platforms?
Select an answer to reveal the explanation.
Short Explanation
You have solid flexibility here without leaving supported ground. Stick with hypervisors Cisco validates, and you keep both data centers plus future cloud options viable.
Full Explanation
The correct statement is accurate because the controller is distributed as a virtual machine image validated for VMware ESXi and KVM on premises, which directly enables the manufacturer's plan for redundant control-plane instances across heterogeneous data centers while preserving a consistent VM-based deployment model when extending into AWS or Azure for hybrid resilience. The Nutanix AHV variant fails on hypervisor scope because AHV is a capable enterprise virtualization platform widely used for similar workloads but it is not one of the two supported on-premises hypervisors here, so it would leave the KVM site uncovered and break the two-site redundancy design. The Google Cloud Platform variant fails on public cloud scope because although GCP is a sound choice for hosting virtualized control functions generally, the supported public cloud targets for unchanged-model extension in this scenario are specifically AWS and Azure, so specifying GCP alone misstates portability and future expansion. The container variant fails on form factor because running control functions as containers on ESXi or KVM is operationally common and attractive for density, yet the controller is supported as a virtual machine, not a containerized microservice, so a container approach would change lifecycle, networking, and support assumptions. As an exam caveat, do not infer broader hypervisor or cloud support from general virtualization knowledge and read whether the stem asks for on-premises platforms, public extension, and image type together. As a practical check, verify the controller OVA and QCOW2 download, version compatibility matrix, and AWS AMI and Azure Marketplace image before planning failover.