Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Zone-Redundant Services Survive Datacenter Outages Automatically
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 in an Azure region that supports availability zones. The engineering team needs to implement an architectural strategy that meets the following criteria:
- Protects services and data from datacenter-wide outages, such as local power or cooling loss.
- Synchronously replicates data across physically separate datacenters within the same region.
- Automatically detects zone failures and maintains operations without requiring manual failover procedures.
Which architectural approach should the organization implement?
Explanations
A zone-redundant service deployment
A zone-redundant service deployment
What Zone-Redundant Services Are
Zone-redundant services replicate data and distribute platform resources automatically across multiple availability zones within a single Azure region. Each availability zone is made up of one or more physical datacenters equipped with independent power, cooling, and networking infrastructure.
How It Meets the Requirements
- Protects against datacenter failures: Because resources and data span multiple independent zones, a complete failure of one datacenter does not take down the entire service.
- Synchronous replication: Within an Azure region, availability zones are connected by high-performance networks with round-trip latency under 2 milliseconds, enabling synchronous data replication across zones.
- Automated failover and detection: The Azure platform automatically monitors zone health and routes traffic away from an impaired zone to healthy zones without requiring administrator intervention.
Key Advantages and Capabilities
- High Availability and Higher SLAs: Distributing instances across availability zones offers higher Service Level Agreement (SLA) uptime guarantees compared to single-datacenter configurations.
- Zero-touch recovery: The platform handles traffic rerouting and fault detection dynamically.
- Low latency: Provides multi-datacenter resiliency without the higher latency penalties associated with cross-region replication.
- Sequenced platform updates: Azure coordinates safe deployment practices to update only one availability zone at a time in a region.
Why This Is Optimal
A zone-redundant service deployment delivers the best balance of low inter-zone latency, automated resilience against datacenter disruptions, and simplified management within a single geographic region.
An availability set deployment
An availability set deployment
What Availability Sets Are
An availability set is a logical grouping capability in Azure that isolates virtual machines across multiple physical hardware racks (fault domains) and scheduled update groups (update domains) inside a single datacenter.
Why It Doesn't Meet the Requirement
Availability sets protect applications against localized hardware disruptions, such as a faulty power supply unit or a failed top-of-rack network switch. However, because all fault domains in a standard availability set reside within the same datacenter facility, they cannot protect workloads against facility-wide events like complete power loss, flood damage, or catastrophic cooling failures.
Key Characteristics and Limitations
- Failure scope: Confined to individual server racks and hardware chassis within one physical building.
- No multi-datacenter redundancy: Does not distribute virtual machines across physically distinct datacenters.
- No built-in inter-zone replication: Does not provide cross-zone data synchronization or cross-datacenter failover capabilities.
This Answer Would Be Correct If
This option would be the right choice if you needed to protect virtual machines against localized hardware faults or routine maintenance reboots within a region that does not offer availability zones.
Additional Context
Availability zones supersede availability sets for modern cloud designs by expanding the isolation boundary from individual server racks to entire independent physical facilities.
A paired region deployment
A paired region deployment
What Paired Regions Are
A paired region configuration involves deploying duplicate workloads across two distinct Azure regions located within the same broad geographic territory, typically separated by hundreds of miles (such as East US and West US).
Why It Doesn't Meet the Requirement
While cross-region deployments provide disaster recovery protection against catastrophic, region-wide natural disasters, they introduce higher network latency and generally require asynchronous data replication. The scenario specifically asks for low-latency synchronous replication and automated datacenter resilience within a single region.
Key Characteristics and Limitations
- Geographic separation: Regional pairs are typically separated by at least 300 miles.
- Network latency: Cross-region communication experiences moderate to high network latency compared to low-latency inter-zone communication.
- Manual or traffic-routed failover: Cross-region disaster recovery typically requires DNS-based routing (such as Azure Traffic Manager) or explicit multi-region disaster recovery configurations.
This Answer Would Be Correct If
This design would be optimal for mission-critical disaster recovery where an entire metropolitan area or geographic region could experience a sustained outage due to major natural disasters or grid failures.
Additional Context
Best practice architecture often combines zone redundancy for day-to-day high availability with paired regions for long-term disaster recovery.
A single-zone (zonal) deployment
A single-zone (zonal) deployment
What Zonal Deployments Are
A zonal deployment (or pinned single-zone deployment) explicitly anchors an Azure resource or virtual machine to one specific availability zone (such as Zone 1) within an Azure region.
Why It Doesn't Meet the Requirement
By pinning resources to a single availability zone, the deployment achieves no automated cross-datacenter redundancy. If the specific physical datacenter housing that zone encounters an outage, the pinned resource becomes unavailable until that zone recovers. It lacks the multi-zone synchronous replication and automatic platform failover specified in the scenario.
Key Characteristics and Limitations
- Single point of failure: Tied directly to the health of one physical datacenter.
- No automatic zone failover: The platform cannot seamlessly shift traffic to another zone because no standby or replicated instance exists in neighboring zones.
- Reduced SLA guarantees: Zonal resources have lower availability guarantees compared to multi-zone distributed architectures.
This Answer Would Be Correct If
This approach would be appropriate for latency-sensitive workloads that need multiple virtual machines located in the exact same physical building to minimize network travel time, or when building custom application-level clustering across explicitly defined zones.
Additional Context
To gain high availability benefits from availability zones, resources must either be deployed across multiple zones manually or provisioned using zone-redundant services that distribute instances across zones automatically.
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
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
Availability Zones Fault Isolation
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
Azure Arc
Describe the purpose of Azure Arc
ExpertAZ-500 Microsoft Azure Security Technologies Exam
Application Permissions vs Delegated Permissions
Configure app registration permission scopes
Last updated Validated