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?

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.

StudyCerts

Azure Availability Zones Cost Tradeoffs | Start here! Get your feet wet with the Microsoft cloud and begin your journey to earning your Microsoft Certified: Azure Fundamentals certification! | StudyCerts

AZ-900 Microsoft Azure Fundamentals Exam

Start here! Get your feet wet with the Microsoft cloud and begin your journey to earning your Microsoft Certified: Azure Fundamentals certification!

Fundamental

Prepare and test your skills

Track Readiness

Set Exam Goal

Fundamental

Prepare and test your skills

Track Readiness

Set Exam Goal

Section: Describe availability zones

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

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?

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.

Availability zones should only be used for regional disaster recovery across hundreds of miles, rather than local datacenter fault isolation.

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.

Deploying across availability zones reduces overall compute costs because Azure provides free standby virtual machine instances in secondary zones.

AZ-900 Microsoft Azure Fundamentals Exam

Related questions