CV0-003 · Question #634
After initial stress testing showed that a platform performed well with the specification of a single 32 vCPU node, which of the following will provide the desired service with the LOWEST cost and dow
The correct answer is B. Two 8 vCPU nodes with load balancing. Two 8 vCPU nodes behind a load balancer deliver high availability to minimize downtime at a lower cost than a single large node.
Question
After initial stress testing showed that a platform performed well with the specification of a single 32 vCPU node, which of the following will provide the desired service with the LOWEST cost and downtime?
Options
- AOne 32 vCPU node with CDN caching
- BTwo 8 vCPU nodes with load balancing
- CThree to six 8 vCPU nodes autoscaling group
- DFour 8 vCPU nodes with DNS round robin
How the community answered
(35 responses)- A9% (3)
- B49% (17)
- C31% (11)
- D11% (4)
Why each option
Two 8 vCPU nodes behind a load balancer deliver high availability to minimize downtime at a lower cost than a single large node.
A single 32 vCPU node with CDN caching improves content delivery latency but leaves the application with a single point of failure, so downtime risk is not reduced.
A load-balanced pair of nodes eliminates the single point of failure present in a one-node design, so if one node becomes unavailable the other continues serving traffic, directly minimizing downtime. Two smaller nodes typically cost less per vCPU than one large instance, reducing overall spend while still providing adequate capacity for a workload validated by stress testing. This combination of redundancy and lower per-unit pricing makes it the most cost-effective option that also addresses availability.
An autoscaling group of three to six nodes adds operational complexity and incurs higher costs at maximum scale, making it less cost-optimal for a stable, predictable workload.
Four 8 vCPU nodes match the full 32 vCPU capacity and increase total cost, while DNS round robin lacks health-check-based failover, making it less reliable than a proper load balancer.
Concept tested: Load balancing for high availability and cost optimization
Source: https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-overview
Topics
Community Discussion
No community discussion yet for this question.