Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Balancing Availability Zone Resiliency and Cost
Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An organization is designing the architecture for two applications hosted in Microsoft Azure:
- Application A: A mission-critical customer portal that requires continuous uptime and resiliency against datacenter-level failures.
- Application B: An internal, non-critical reporting tool used occasionally during standard business hours with flexible availability needs.
When evaluating the cost implications and architectural trade-offs of deploying these workloads across Azure Availability Zones, which principle should guide the design?
Explanations
Availability zones should only be used for regional disaster recovery across hundreds of miles, rather than local datacenter fault isolation.
Availability zones should only be used for regional disaster recovery across hundreds of miles, rather than local datacenter fault isolation.
What This Option Describes
This option confuses the architectural scope and geographic boundary of Availability Zones with that of Azure Paired Regions.
Why It Doesn't Meet the Requirement
Availability zones exist within a single geographic region and are designed specifically to protect applications against local datacenter-level failures (such as power, cooling, or local network interruptions). They are not separated by hundreds of miles and do not serve as a replacement for multi-region disaster recovery against broad geographic catastrophes.
Key Characteristics and Limitations
- Intra-Regional Boundary: Availability zones reside in close geographic proximity within the same regional perimeter to enable sub-2-millisecond low-latency replication.
- Paired Regions for Disaster Recovery: Protection against regional disasters that affect an entire metropolitan area requires deploying across paired regions, which are typically separated by at least 300 miles.
- Datacenter-Level Scope: Availability zones provide high availability within a region, whereas multi-region deployments provide disaster recovery across regions.
This Answer Would Be Correct If
The question had asked about Azure Paired Regions or cross-region replication strategies designed to protect against large-scale geographic catastrophes.
Multi-zone deployments should be avoided primarily because Azure incurs significant recurring per-gigabyte data transfer charges for inter-zone traffic within the same region.
Multi-zone deployments should be avoided primarily because Azure incurs significant recurring per-gigabyte data transfer charges for inter-zone traffic within the same region.
What This Option Describes
This option claims that the primary cost driver and deterrent for using availability zones is a substantial data transfer fee between zones within a single Azure region.
Why It Doesn't Meet the Requirement
Azure does not charge for inter-availability zone data transfer within a region, whether using private or public IP addresses. While cross-region traffic incurs data egress charges, network communication between availability zones within the same regional boundary does not carry inter-zone data transfer pricing.
Key Characteristics and Limitations
- Zero-Cost Inter-Zone Data Transfer: Data flowing between availability zones in the same region is free of inter-zone data transfer charges.
- Low Latency Links: High-performance regional backbones connect availability zones with round-trip latency typically under 2 milliseconds.
- Primary Cost Factors: The main cost factors for multi-zone designs stem from running additional compute, storage, and load-balancing resources, rather than network data transfer fees.
This Answer Would Be Correct If
This option would be accurate if the organization were designing cross-region architectures, where cross-region network egress charges apply to traffic exiting an Azure region.
Achieving higher resiliency by deploying redundant resources across availability zones increases infrastructure costs and complexity, so multi-zone redundancy should be prioritized for critical workloads.
Achieving higher resiliency by deploying redundant resources across availability zones increases infrastructure costs and complexity, so multi-zone redundancy should be prioritized for critical workloads.
What Availability Zone Architecture Is
Azure Availability Zones are physically separate datacenters located within an Azure region. Each zone is equipped with independent power, cooling, and networking infrastructure. Distributing application instances across multiple availability zones provides high availability and protects workloads against localized datacenter outages.
How It Addresses the Cost Trade-off Requirement
Building resilient cloud solutions involves a direct trade-off between availability and cost:
- For Application A (Mission-Critical): The business justifies the additional expense of running active or standby redundant compute instances across multiple zones because downtime results in significant revenue loss or operational disruption.
- For Application B (Non-Critical): Running multiple redundant virtual machines across distinct zones would lead to unnecessary infrastructure spending that does not align with the application's low business-impact profile.
Key Advantages and Considerations
- Datacenter Fault Isolation: Protects critical applications from single-datacenter failures within a region.
- Cost Proportionality: Aligning infrastructure spend with actual business availability requirements ensures optimal cloud investment.
- Independent Compute Costs: Each additional virtual machine deployed in an availability zone incurs standard compute and storage charges.
- Resource Optimization: Non-critical workloads can remain single-instance or use lower-cost redundancy models to minimize waste.
Why This Is Optimal
Cloud cost management principles dictate that every expenditure must map directly back to business value. Recognizing the trade-off between redundancy, architectural complexity, and cost allows organizations to invest in multi-zone reliability where it is essential while avoiding excessive costs on non-critical systems.
Deploying across availability zones reduces overall compute costs because Azure provides free standby virtual machine instances in secondary zones.
Deploying across availability zones reduces overall compute costs because Azure provides free standby virtual machine instances in secondary zones.
What This Option Describes
This option suggests that deploying across availability zones automatically lowers computing costs by providing complementary standby virtual machine instances.
Why It Doesn't Meet the Requirement
Azure does not provide free duplicate or standby virtual machines when configuring multi-zone architectures. Every provisioned virtual machine, attached managed disk, and associated service instance incurs standard hourly or consumption charges regardless of which availability zone it occupies.
Key Characteristics and Limitations
- Independent Billing: Every active compute instance deployed into a specific availability zone is billed at its regular provisioned rate.
- No Automatic Cost Reductions: Multi-zone deployment increases the total number of running resources, leading to higher, not lower, baseline costs.
- Resource Duplication: High availability requires active or passive duplication of application tiers, multiplying underlying resource expenses.
This Answer Would Be Correct If
This concept would only apply if cloud providers offered free passive compute standby instances as a native feature of multi-zone redundancy, which is not how Azure operates.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 688 practice questions across all 3 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Zone-Redundant Services
Describe availability zones
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Availability Zones Fault Isolation
Describe availability zones
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Availability Zones
Describe availability zones
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Availability Zones and Zone-Redundant Storage
Describe availability zones
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Resource Tags
Describe the Azure portal
ExpertAZ-305 Designing Microsoft Azure Infrastructure Solutions Exam
Azure Container Apps vs AKS
Recommend a container-based solution
Last updated Validated