Availability zones are physically and often electrically isolated locations within a region, each with independent power, cooling, and networking. Deploying an application across multiple zones means that the failure of any single zone, whether due to a power outage, network disruption, or localized hardware failure, does not take the entire application offline, since the remaining zones continue to serve traffic. This redundancy against zone-level failure is precisely what enhances reliability, the application's ability to remain operational and available despite localized infrastructure faults. Reduced costs (A) is not a natural outcome of multi-zone deployment; in fact, running redundant infrastructure across multiple zones typically increases infrastructure spend compared to a single-zone deployment, since duplicate resources must be provisioned and often kept synchronized. Increased security (C) is not a direct or defining benefit of multi-zone deployment either, since security controls such as encryption, access management, and network segmentation operate independently of how many zones an application spans. Improved consistency (D) is arguably a challenge introduced by multi-zone deployment, since keeping state synchronized across zones (particularly for databases) adds complexity, rather than a benefit that multi-zone architecture inherently provides. Enhanced reliability through zone-level fault isolation is the correct key benefit.

Reference topic: Fault Tolerance Techniques - Multi-Zone and Multi-Site Resiliency.