County clerk staff want a quick lab of VDI images on admin workstations using a hosted hypervisor. Which choice best fits that Type 2 use case versus production Type 1?
Select an answer to reveal the explanation.
Short Explanation
A hosted Type 2 hypervisor is the 'app on your laptop' approach—perfect for a clerk lab that needs to spin up quickly. Production city clusters usually want Type 1 on bare metal. Right tool, right job.
Full Explanation
County clerk labs that need quick VDI images on admin workstations align with Type 2 hosted hypervisors: the hypervisor runs as software on the workstation operating system, which is convenient for temporary labs even though it is not the preferred production cluster model. Type 1 bare-metal designs remain appropriate for production clusters that need efficiency and dedicated virtualization hosts. ENCOR expects that use-case split rather than forcing every laptop into a production HA bare-metal build.
Deploying only bare-metal Type 1 on every clerk laptop because labs supposedly require production HA overbuilds the lab and misreads the convenience goal. Avoiding any hypervisor and bridging VMs directly into the underlay with process switching is neither a Type 2 lab pattern nor a sound forwarding design. Using SD-Access fabric borders on the workstation NIC instead of a hypervisor confuses fabric campus roles with local desktop virtualization.
Exam caveat: match Type 2 to hosted lab convenience and Type 1 to production bare-metal clusters when both appear.
Operational check: install a hosted hypervisor on a clerk admin OS for the lab images, keep those VMs off production cluster capacity plans, and document that production workloads stay on Type 1 hosts.