NCP-DB-6.10 · Question #115
An administrator configures VM Host Affinity for database server VMs on a Nutanix AHV-powered cluster, intending to optimize HA by ensuring that VMs are placed on separate hosts. After a host…
The correct answer is D. Set anti-affinity rules to spread VMs across multiple nodes dynamically. Configuring VM Host Affinity in a Nutanix AHV-powered cluster ensures that VMs are placed on specific hosts to optimize performance or HA. However, after a host failure, if database VMs cluster on a single remaining host, it indicates that the affinity rules alone are…
Question
An administrator configures VM Host Affinity for database server VMs on a Nutanix AHV-powered cluster, intending to optimize HA by ensuring that VMs are placed on separate hosts. After a host failure, the administrator notices that database VMs are clustered on a single remaining host, risking another outage. How could the administrator avoid this scenario in future host failures?
Options
- AAssign additional backup VMs within the same host to maintain service.
- BIncrease the number of affinity zones within the cluster
- CConfigure automatic host failover in Prism Central.
- DSet anti-affinity rules to spread VMs across multiple nodes dynamically.
How the community answered
(32 responses)- A9% (3)
- B6% (2)
- C22% (7)
- D63% (20)
Explanation
Configuring VM Host Affinity in a Nutanix AHV-powered cluster ensures that VMs are placed on specific hosts to optimize performance or HA. However, after a host failure, if database VMs cluster on a single remaining host, it indicates that the affinity rules alone are insufficient to maintain high availability (HA) during failover scenarios. To prevent this, the administrator should configure anti- affinity rules, which dynamically ensure that VMs (e.g., database server VMs) are spread across multiple hosts. Anti-affinity rules override default VM placement behavior during failover, reducing the risk of a single point of failure by keeping VMs separated even after a host
Topics
Community Discussion
No community discussion yet for this question.