CV0-003 · Question #288
A cloud administrator is analyzing usage trends for a website housed within an IaaS cloud platform. The administrator notices that traffic and visitors to the site quadrupled from the normal…
The correct answer is A. Implement an upward vertical scaling solution. For a temporary traffic spike in a load-balanced IaaS environment, upward vertical scaling increases resources on existing VMs to handle the increased demand without provisioning additional instances.
Question
A cloud administrator is analyzing usage trends for a website housed within an IaaS cloud platform. The administrator notices that traffic and visitors to the site quadrupled from the normal baseline during the holiday season. The environment has a load balancer that uses standardized VMs to host the applications. Given this scenario, which of the following would be the MOST efficient, provide no downtime, and address the temporary spike in traffic?
Options
- AImplement an upward vertical scaling solution.
- BImplement a downward vertical scaling solution.
- CImplement an inward horizontal scaling solution.
- DImplement an outward horizontal scaling solution.
How the community answered
(40 responses)- A75% (30)
- B3% (1)
- C8% (3)
- D15% (6)
Why each option
For a temporary traffic spike in a load-balanced IaaS environment, upward vertical scaling increases resources on existing VMs to handle the increased demand without provisioning additional instances.
Upward vertical scaling (scaling up) increases CPU, RAM, or other compute resources on the existing standardized VMs, directly boosting capacity for the temporary holiday spike. Modern IaaS platforms support live VM resizing with minimal or no downtime, and since the load balancer and VMs are already in place, scaling existing instances upward is operationally simpler and more efficient than provisioning and configuring new instances. This approach handles the temporary demand and can be reversed after the holiday season without restructuring the environment.
Downward vertical scaling reduces resources on existing VMs, which would decrease capacity and degrade performance during a period of quadrupled traffic.
Inward horizontal scaling removes VM instances from the pool, shrinking capacity rather than expanding it to meet the spike.
Outward horizontal scaling adds new VM instances, which introduces provisioning overhead and additional configuration work compared to simply resizing existing VMs for a temporary workload spike.
Concept tested: Vertical vs horizontal cloud scaling for traffic spikes
Source: https://learn.microsoft.com/en-us/azure/architecture/best-practices/auto-scaling
Topics
Community Discussion
No community discussion yet for this question.