A company is deploying a new critical web application that must ensure continuous operation even in the event of a single system failure. Which of the following strategies should the company employ to best align with high availability considerations for this application?
Increase the memory capacity on the primary server
Take frequent snapshots of the application's data
Configure a failover cluster for the application servers
Implementing load balancing is the correct strategy because it distributes traffic across multiple active servers, ensuring that if one server goes down, the application remains available via the other servers. This directly meets the requirement for continuous operation. Taking frequent snapshots is a data recovery and backup strategy, not a high availability solution for preventing downtime. Increasing memory capacity improves performance but does not address a single point of failure. Configuring a failover cluster is a valid high availability strategy, but it typically involves a primary server handling all traffic until it fails, at which point a secondary server takes over. This process can cause a brief service interruption, making load balancing the superior choice for ensuring seamless, continuous operation.
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 is load balancing, and how does it ensure high availability?
Open an interactive chat with Bash
How does a failover cluster differ from load balancing in high availability setups?
Open an interactive chat with Bash
Why is increasing memory capacity not a viable high availability solution?