Distribute resources across multiple Availability Zones.
Correct. Distributing resources across multiple AZs means that even if one AZ fails, processing can continue in the other AZs, greatly improving fault tolerance.
Which of the following are appropriate ways to improve the availability and fault tolerance of an application? Choose 2.
Choosing 2 appropriate ways to raise availability and fault tolerance.
Distribute resources across multiple Availability Zones.
Correct. Distributing resources across multiple AZs means that even if one AZ fails, processing can continue in the other AZs, greatly improving fault tolerance.
Consolidate all components onto a single server.
Consolidating onto one server makes that server a single point of failure; if it breaks, everything stops.
This lowers availability, so it is incorrect.
Cut storage costs by not taking backups.
Without backups, you cannot recover when data is lost.
Costs go down but fault tolerance drops, so it is incorrect.
Combine a load balancer with Auto Scaling.
Correct. A load balancer spreads traffic across multiple instances, and Auto Scaling follows demand and replaces unhealthy instances, achieving high availability and fault tolerance.
Disable health checks to avoid unnecessary restarts.
Health checks are the mechanism that detects unhealthy instances and removes them.
Disabling them lets traffic keep flowing to broken instances, lowering availability, so it is incorrect.
The standard way to raise availability is multi-AZ distribution + load balancer + Auto Scaling. Conversely, 'single-server consolidation', 'no backups', and 'disabling health checks' are classic anti-patterns that create single points of failure or unrecoverable loss.