Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Availability Zones and Zone-Redundant Storage Resilience
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 deploying a business-critical workload to Azure. The architecture team must ensure that both compute and data storage services remain operational and resilient against individual datacenter failures caused by power, cooling, or networking issues within the primary Azure region.
Which deployment strategy should the organization implement?
Explanations
Deploy application instances into a single datacenter and apply Azure Resource Locks to all resources
Deploy application instances into a single datacenter and apply Azure Resource Locks to all resources
What Azure Resource Locks Are
Azure Resource Locks are administrative management settings applied at the subscription, resource group, or resource level to prevent accidental modification (ReadOnly) or deletion (CanNotDelete) by authorized users.
Why It Doesn't Meet the Requirement
- Management plane control only: Resource locks do not affect the physical runtime infrastructure, datacenter placement, or high availability of the workload.
- No physical failure protection: Applying a lock does nothing to protect virtual machines or storage from power failures, cooling breakdowns, or physical hardware outages in a datacenter.
Key Characteristics and Limitations
- Governance tool: Used primarily to enforce operational guardrails against human error.
- Independent of Availability Zones: Locks do not replicate data, balance compute loads, or provide fault isolation.
- No redundancy capabilities: A locked resource residing in a failed datacenter remains completely inaccessible during an outage.
This Answer Would Be Correct If
The requirement was to prevent administrators or automated scripts from accidentally deleting or changing the configuration of production resources.
Distribute application instances across multiple Availability Zones and configure Zone-Redundant Storage (ZRS)
Distribute application instances across multiple Availability Zones and configure Zone-Redundant Storage (ZRS)
What Multi-Zone and Zone-Redundant Storage Is
A multi-zone deployment involves distributing virtual machines and application components across distinct Availability Zones within an Azure region. Combined with Zone-Redundant Storage (ZRS), data is synchronously replicated across three separate physical availability zones, each equipped with independent power, cooling, and networking infrastructure.
How It Meets the Requirements
- Protects against datacenter failures: Because each availability zone is physically separate, an outage affecting one datacenter (such as a power grid failure or cooling issue) does not impact the remaining zones.
- Maintains business continuity: Distributing virtual machine instances and utilizing ZRS ensures that compute instances remain online and data remains accessible without needing to fail over to a completely different geographic region.
Key Advantages and Capabilities
- Synchronous replication: ZRS replicates data across three zones with zero data loss (RPO = 0) for supported storage tiers.
- Independent fault domains: Each availability zone operates with dedicated utility feeds and networking paths.
- Low latency: Zones within the same region are interconnected by high-performance, low-latency fiber-optic networks.
- High availability SLA: Deploying multiple VM instances across availability zones qualifies the deployment for Azure's highest single-region availability service level agreements.
Why This Is Optimal
This architecture provides the maximum level of resiliency available within a single region. It balances performance, automated high availability, and operational simplicity without introducing cross-region latency or complex disaster recovery orchestration.
Deploy application instances across multiple Azure subscriptions located in the same physical datacenter
Deploy application instances across multiple Azure subscriptions located in the same physical datacenter
What Multi-Subscription Architecture Is
A multi-subscription architecture organizes Azure resources across separate administrative and billing boundaries. Subscriptions are logical containers used for access management, quota allocation, and cost tracking.
Why It Doesn't Meet the Requirement
- Logical vs. physical separation: A subscription is purely a logical management boundary. Placing resources in multiple subscriptions does not separate them physically if they are provisioned within the same physical datacenter.
- Shared physical failure domain: If the underlying datacenter suffers a facility-level outage, all subscriptions hosting workloads in that facility will experience downtime simultaneously.
Key Characteristics and Limitations
- Billing and governance boundary: Subscriptions help segregate department costs and role-based access control (RBAC).
- Zero hardware redundancy: Deploying to separate subscriptions within the same datacenter shares identical power, networking, and server racks.
- No automatic failover: Logical separation provides no native high availability or disaster recovery capabilities.
This Answer Would Be Correct If
The organization needed to separate cost accounting, resource quotas, or administrative permissions between different internal business units.
Deploy all application instances in a single Availability Zone using Locally Redundant Storage (LRS)
Deploy all application instances in a single Availability Zone using Locally Redundant Storage (LRS)
What Single-Zone Deployment with LRS Is
A single-zone deployment places all compute instances into one physical datacenter location, while Locally Redundant Storage (LRS) replicates data three times within that same single physical datacenter.
Why It Doesn't Meet the Requirement
- Single point of failure: Because all compute instances and storage replicas reside within one physical facility, any datacenter-level disaster (such as a fire, flood, or facility-wide power loss) will cause total downtime.
- No zone isolation: LRS does not protect against catastrophic hardware failures across the building or broader zone outages.
Key Characteristics and Limitations
- Lowest cost redundancy: LRS is the most economical storage tier but offers the lowest durability against facility-wide events.
- Intra-datacenter replication only: LRS protects against individual disk, rack, or server failures, not facility outages.
- Vulnerability to thermal and power events: If the physical building experiences an interruption, all replicas become simultaneously unavailable.
This Answer Would Be Correct If
The workload was a non-critical development or testing environment where downtime is acceptable, data can be easily reconstructed, and minimizing infrastructure cost is the primary objective.
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
Describe availability zones
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Availability Zones Cost vs Resiliency Trade-off
Describe availability zones
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Availability Zones Fault Isolation
Describe availability zones
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure RBAC Custom Roles
Describe Azure role-based access control (RBAC)
IntermediateAZ-204 Developing Solutions for Microsoft Azure Exam
Azure Blob System Properties vs User-Defined Metadata
Set and retrieve properties and metadata
Last updated Validated