A systems administrator is preparing a production deployment consisting of three web-server VMs that provide the same application front end. The administrator must ensure that a hardware failure on a single hypervisor host cannot take down more than one of the web servers. Each VM should therefore reside on a different underlying physical server. Which hypervisor configuration change will satisfy this requirement?
Clone the instances onto a single host
Enable hardware pass-through for network adapters
Configure anti-affinity settings in the hypervisor
Increase the system memory allocation for the host
Configuring an anti-affinity (also called "separate virtual machines") rule in the hypervisor forces the scheduler to place each VM on a different physical host, protecting the service from a single-host outage. Raising memory allocations does nothing to influence host placement, hardware pass-through merely maps a device directly into a VM without affecting distribution, and cloning multiple instances onto one host concentrates risk instead of dispersing it.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are anti-affinity settings in a hypervisor?
Open an interactive chat with Bash
How does an anti-affinity rule differ from an affinity rule?
Open an interactive chat with Bash
What is the impact of enabling hardware pass-through in a hypervisor?