Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Azure Availability Zones for Datacenter Fault Isolation
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 mission-critical web application on Microsoft Azure. To protect against localized physical disruptions—such as a facility power loss or cooling system failure affecting an entire datacenter—the architecture team wants to distribute virtual machines across physically separate datacenters located within the same geographic region.
Which Azure infrastructure component should the organization implement to meet this requirement?
Explanations
Resource Tags
Resource Tags
What Resource Tags Are
Resource Tags are user-defined key-value metadata pairs applied to Azure resources, resource groups, or subscriptions to logically categorize and track assets across an organization.
Why They Do Not Meet the Requirement
Tags provide metadata for querying, billing, and organizational filtering. They have no impact on the underlying physical infrastructure, resource placement, fault tolerance, or disaster recovery capabilities of cloud services.
Key Characteristics and Limitations
- Metadata Management: Stores key-value labels to describe business context, department ownership, or environment type.
- Cost Reporting: Facilitates granular reporting in cost management and billing tools.
- No Physical Redundancy: Does not influence hardware resilience, network routing, or physical datacenter isolation.
When This Option Would Be Correct
Resource Tags would be the correct answer if the organization needed to categorize cloud assets for departmental billing attribution, environment labeling (e.g., Environment: Production), or inventory auditing.
Availability Zones
Availability Zones
What Availability Zones Are
Availability Zones are physically separate locations within an Azure region. Each zone is comprised of one or more datacenters equipped with independent power, cooling, and networking infrastructure. They are interconnected by high-performance, low-latency private networks.
How They Meet the Requirement
By deploying virtual machines across multiple Availability Zones, the application is protected from datacenter-wide failures. If an unexpected power outage, cooling malfunction, or local hardware failure renders an entire datacenter offline, instances in other zones within the region continue running without interruption.
Key Advantages and Capabilities
- Physical Isolation: Each availability zone provides complete physical separation of power, cooling, and network links within a single region.
- Low-Latency Inter-Zone Connectivity: Zones are connected via high-speed fiber networks with round-trip latency typically under 2 milliseconds, supporting synchronous data replication.
- Safe Deployment Practices: Azure rolls out platform updates sequentially across zones within a region, ensuring active workloads in remaining zones remain operational.
- Data Residency Compliance: Workloads remain inside the defined geographical region while achieving high-level fault isolation.
Why This Is Optimal
Availability Zones offer the ideal balance of high fault isolation and minimal network latency without requiring multi-region deployment complexity.
Availability Sets
Availability Sets
What Availability Sets Are
Availability Sets are logical groupings used to distribute virtual machines across underlying hardware within a single datacenter. They separate workloads across distinct fault domains (shared power supply and network switch) and update domains (groups of hardware rebooted during platform updates).
Why They Do Not Meet the Requirement
While availability sets protect against localized hardware issues such as a failed server rack, power supply unit, or top-of-rack network switch, all resources in an availability set reside within the same physical datacenter. Consequently, a facility-wide failure—such as total datacenter power loss—will impact all virtual machines in the set.
Key Characteristics and Limitations
- Rack-Level Protection: Designed strictly to isolate workloads from single points of rack or host failure.
- Single Facility Scope: Does not provide physical separation across independent datacenter facilities.
- No Facility-Level Redundancy: Lacks independent power and cooling separation for disaster isolation.
When This Option Would Be Correct
Availability Sets would be the appropriate choice when deploying legacy applications in regions that do not support Availability Zones or when protecting against single-rack server hardware faults.
Resource Groups
Resource Groups
What Resource Groups Are
A Resource Group is a logical management container in Azure that holds related resources for an application, solution, or environment. It serves as the primary scope for organizing, managing access with Role-Based Access Control (RBAC), monitoring, and applying management policies.
Why They Do Not Meet the Requirement
Resource groups are administrative and logical boundaries, not physical infrastructure components. Placing resources into a resource group does not provide physical redundancy, high availability, or protection against physical datacenter failures.
Key Characteristics and Limitations
- Logical Organization: Groups assets such as virtual machines, virtual networks, and storage accounts for simplified lifecycle management.
- Access and Policy Boundary: Enables administrative governance and access management across aggregated resources.
- No High Availability Impact: Does not dictate the physical hardware distribution or geographic placement of provisioned compute instances.
When This Option Would Be Correct
Resource Groups would be the correct solution if the objective were to group related Azure resources together to manage permissions, lifecycle deployments, or centralized cost tracking.
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
Infrastructure as a Service (IaaS)
Define cloud computing
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Hybrid Cloud
Define cloud computing
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Rapid Elasticity
Define cloud computing
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
CapEx vs OpEx
Define cloud computing
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Shared Responsibility Model
Define cloud computing
IntermediateAZ-800 Administering Windows Server Hybrid Core Infrastructure Exam
Azure File Sync Event Logs and Azure Monitor
Configure and manage Azure File Sync
Last updated Validated