Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Azure Availability Zones Protect Against Datacenter Failure
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 enterprise is designing a mission-critical workload on Azure Virtual Machines and needs to maximize reliability.
The solution must satisfy the following architectural requirements:
- Provide resilience and continuous operation even if an entire datacenter facility experiences a power, cooling, or networking failure
- Deploy redundant VM instances across distinct physical locations within the same Azure region
- Maintain low-latency connectivity between the redundant application instances
Which Azure reliability feature should the enterprise implement to meet these requirements?
Explanations
Locally Redundant Storage (LRS)
Locally Redundant Storage (LRS)
What Locally Redundant Storage Is
Locally Redundant Storage (LRS) is a low-cost data redundancy option in Azure that replicates data three times synchronously within a single physical storage scale unit in one primary datacenter.
Why It Doesn't Meet the Requirement
LRS is strictly a storage-layer redundancy option and does not distribute virtual machine compute workloads across independent physical facilities. Furthermore, because all three data replicas reside in the same primary datacenter facility, a major datacenter outage or disaster could render the storage temporarily or permanently inaccessible.
Key Characteristics and Limitations
- Intra-datacenter replication: Replicates data across three disks within a single facility to achieve 99.999999999% (11 9's) durability.
- Compute agnostic: Protects only stored disk bits, not the compute infrastructure running across distinct locations.
- Vulnerable to facility disasters: Cannot protect data or applications against fire, power loss, or flooding of the host datacenter.
This Answer Would Be Correct If
The organization wanted the most economical storage configuration to protect managed disks against local disk hardware failures within a single datacenter.
Additional Context
To achieve datacenter fault tolerance for storage disks, organizations should select Zone-Redundant Storage (ZRS) rather than Locally Redundant Storage (LRS).
Availability zones
Availability zones
What Availability Zones Are
Azure Availability Zones are physically separate locations within an Azure region. Each availability zone is made up of one or more distinct datacenters equipped with independent power, cooling, and networking infrastructure. Azure regions that support availability zones feature a minimum of three separate zones to ensure high resilience and fault tolerance.
How It Meets the Requirements
- Resilience against datacenter failure: Because each availability zone has dedicated power, cooling, and network links, a complete outage at one physical datacenter does not affect the operation of workloads deployed in the other zones.
- Distinct physical locations within a region: Availability zones allow virtual machines and storage resources to be distributed across separate physical facilities while remaining within the same geographic region boundary.
- Low-latency performance: Zones within an Azure region are interconnected via a high-speed, low-latency private fiber network, allowing synchronous replication and rapid inter-zone communication.
Key Advantages and Capabilities
- Fault isolation: Isolates hardware, software, and facility-level failures to a single physical zone.
- High availability SLAs: Delivers industry-leading uptime service-level agreements (SLAs) for virtual machines distributed across zones.
- Automated traffic rerouting: Integrates with Azure load balancers and services to automatically direct traffic away from unhealthy zones to healthy instances.
- Zone-redundant storage: Supports zone-redundant storage (ZRS) to replicate data across three availability zones automatically.
Why This Is Optimal
Deploying across Availability Zones is the optimal design choice because it provides isolation from catastrophic facility-level disruptions without requiring cross-region disaster recovery replication overhead.
Availability sets
Availability sets
What Availability Sets Are
Azure Availability Sets are logical grouping capabilities that isolate virtual machine workloads across distinct hardware racks, power sources, and network switches (known as fault domains and update domains) inside a single datacenter.
Why It Doesn't Meet the Requirement
While availability sets protect applications from localized hardware, server rack, or storage stamp failures within a datacenter, they do not provide protection against full datacenter outages. All virtual machines inside an availability set reside within the same physical building or facility; therefore, a widespread facility-level power or cooling failure would impact all instances in the set.
Key Characteristics and Limitations
- Rack-level fault domain isolation: Distributes VMs across different physical hardware racks within a single datacenter.
- Update domain separation: Ensures that during platform maintenance, not all VM instances are rebooted simultaneously.
- No physical facility separation: Offers zero protection against floods, fires, or total power grid failures affecting the host datacenter.
This Answer Would Be Correct If
The requirement asked to protect an application against localized server hardware crashes and maintenance events within a single datacenter where availability zones are not supported.
Additional Context
Availability zones provide physical datacenter-level boundary isolation, whereas availability sets provide rack-level boundary isolation within the same datacenter.
Multi-region disaster recovery deployment
Multi-region disaster recovery deployment
What Multi-Region Disaster Recovery Is
Multi-Region Disaster Recovery involves provisioning redundant infrastructure across two or more geographically separated Azure regions (such as East US and West US) to survive regional catastrophes.
Why It Doesn't Meet the Requirement
The scenario specifically requires distributing redundant instances across distinct physical facilities within the same Azure region while preserving ultra-low latency communication. Multi-region deployments span different geographic areas hundreds or thousands of miles apart, introducing higher network latency and requiring complex cross-region failover and synchronization mechanisms.
Key Characteristics and Limitations
- Geographic separation: Spans multiple regional boundaries to protect against wide-area catastrophic events.
- Increased network latency: Higher latency between regions makes synchronous real-time VM clustering difficult or impractical.
- Higher operational complexity: Requires manual or automated cross-region DNS failover, asynchronous replication management, and higher costs.
This Answer Would Be Correct If
The requirement mandated surviving an entire regional catastrophe, such as a major natural disaster or grid collapse affecting an entire geographic region.
Additional Context
Reliability architecture generally follows a defense-in-depth model: Availability Sets protect against rack failures, Availability Zones protect against datacenter failures, and Multi-Region deployments protect against regional failures.
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 Budgets
Describe the benefits of reliability and predictability in the cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Site Recovery
Describe the benefits of reliability and predictability in the cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Cosmos DB Autoscale Provisioned Throughput
Describe the benefits of reliability and predictability in the cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Managed Disk Performance Tiers
Describe the benefits of reliability and predictability in the cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Management Group Policy and RBAC Inheritance
Describe the hierarchy of resource groups, subscriptions, and management groups
ExpertAZ-305 Designing Microsoft Azure Infrastructure Solutions Exam
Azure Monitor Cost Optimization Design
Recommend a monitoring solution
Last updated Validated