A government agency requires all SD-WAN controllers to run in its own data centers and approved public cloud accounts for sovereignty, with no Cisco-hosted option. The architect must list viable placements for the Manager, Controller, and Validator. Which set identifies supported hosting platforms for customer-hosted controllers?
Select an answer to reveal the explanation.
Short Explanation
You can keep the controllers within your sovereignty boundary by running them as VMs on ESXi or KVM, or in your approved AWS or Azure accounts. Customer-hosted placement gives you those supported choices without relying on Cisco-hosted services.
Full Explanation
The supported customer-hosted set is Manager, Controller, and Validator VM images on VMware ESXi or Linux KVM in agency data centers, or as customer-managed instances in agency-owned AWS or Azure subscriptions. This keeps tenancy and data under agency control without a Cisco-hosted dependency. The set that adds Cisco-hosted cloud services fails the sovereignty requirement: its ESXi and KVM placements are valid, but the Cisco-hosted placement is not. The set using Microsoft Hyper-V or Citrix Hypervisor fails on platform support; although those hypervisors are common in enterprises, these controllers require ESXi or KVM, and success in a lab on another hypervisor does not establish production support. The set limited to ESXi or KVM and private colocation fails to include the approved AWS and Azure placements, so it does not cover the required data-center and approved-cloud environments. Exam caveat: distinguish customer-hosted controllers in your own AWS or Azure account from Cisco-hosted SaaS; both use public cloud, but only customer hosting meets this sovereignty constraint. Practical check: verify the ESXi OVA, KVM QCOW, AWS AMI, and Azure image IDs, and confirm subscription ownership before approval.