2V0-13.24 · Question #13
An architect is planning resources for a new cluster that will be integrated into an existing VI Workload Domain. The cluster's primary purpose is to support a mission-critical application with five…
The correct answer is A. Establish a cluster with four hosts and implement rules to prioritize resources for the application. N+1 availability requires one spare host for failover (e.g., 3 active + 1 = 4 hosts minimum for 5 VMs). Option A, "four hosts with prioritization rules" (e.g., DRS VM-Host affinity), ensures resources for the 5 VMs, meets N+1 (3 active, 1 spare), and minimizes cost compared to…
Question
An architect is planning resources for a new cluster that will be integrated into an existing VI Workload Domain. The cluster's primary purpose is to support a mission-critical application with five resource-intensive virtual machines. Which design recommendation should the architect provide to prevent resource bottlenecks while meeting the N+1 availability requirement and keeping the overall investment cost minimal?
Options
- AEstablish a cluster with four hosts and implement rules to prioritize resources for the application
- BEstablish a cluster with three hosts and exclusively run the application virtual machines on this
- CEstablish a cluster with six hosts and implement automated placement rules to keep the
- DEstablish a cluster with six hosts and implement automated placement rules to distribute the
How the community answered
(18 responses)- A72% (13)
- B6% (1)
- C17% (3)
- D6% (1)
Explanation
N+1 availability requires one spare host for failover (e.g., 3 active + 1 = 4 hosts minimum for 5 VMs). Option A, "four hosts with prioritization rules" (e.g., DRS VM-Host affinity), ensures resources for the 5 VMs, meets N+1 (3 active, 1 spare), and minimizes cost compared to 6 hosts. Option B (3 hosts) lacks N+1 (no spare). Options C and D (6 hosts) exceed minimal cost, with C risking bottlenecks (VMs together) and D less optimal for resource focus. A balances VCF 5.2 HA
Topics
Community Discussion
No community discussion yet for this question.