H13-821_V3.0 · Question #47
Architectural high availability refers to improving the availability of systems and applications by minimizing the downtime caused by routine maintenance operations and sudden system crashes. Which…
The correct answer is D. Increase network bandwidth. Increasing network bandwidth improves throughput and reduces latency, but it does nothing to keep a system running during server failures or scheduled maintenance - the two core concerns of high availability. Elastic scaling (A) allows systems to automatically adjust capacity…
Question
Architectural high availability refers to improving the availability of systems and applications by minimizing the downtime caused by routine maintenance operations and sudden system crashes. Which of the following options is not a high-availability architecture design?
Options
- ADesign system elastic scaling
- BUse disaster recovery backup service
- CUse load balancing service to realize traffic distribution control
- DIncrease network bandwidth
How the community answered
(36 responses)- A3% (1)
- B6% (2)
- C11% (4)
- D81% (29)
Explanation
Increasing network bandwidth improves throughput and reduces latency, but it does nothing to keep a system running during server failures or scheduled maintenance - the two core concerns of high availability. Elastic scaling (A) allows systems to automatically adjust capacity in response to load or failures, maintaining uptime under stress. Disaster recovery backup services (B) enable failover to redundant infrastructure when primary systems go down, directly reducing downtime. Load balancing (C) distributes traffic across multiple instances so that if one fails, others absorb the load without service interruption.
Memory tip: High availability is about keeping systems running, not making them faster. Any option that only improves speed or capacity - without addressing failure or redundancy - is not an HA design.
Topics
Community Discussion
No community discussion yet for this question.