Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Availability Zones Provide Fault Isolation in a Region
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 Azure virtual machines. The architectural team must ensure that the workload remains resilient and operational even if an entire physical datacenter within the region experiences an unexpected power or cooling failure.
Which Azure architectural component should the team use to meet this requirement?
Explanations
Availability zones
Availability zones
What Availability Zones Are
Availability zones are physically separate datacenter locations within each Azure region. Each zone is comprised of one or more datacenters equipped with independent power, cooling, and networking infrastructure. They provide a foundational boundary for application resiliency within a regional cloud architecture.
How Availability Zones Meet the Requirement
By deploying virtual machines across multiple availability zones, the organization ensures that if one zone experiences a catastrophic facility failure (such as an electrical grid outage or cooling disruption), the remaining instances in alternative zones continue running without interruption. This provides fault isolation and high availability within the same Azure region.
Key Advantages and Capabilities
- Physical separation: Datacenters in different zones are located far enough apart to mitigate localized disasters while maintaining low latency.
- Independent infrastructure: Each zone has dedicated power generators, cooling systems, and network links to prevent shared-mode failures.
- High-speed networking: Interconnected with high-bandwidth, low-latency private fiber networks.
- Zonal and zone-redundant services: Supports deploying specific resources to distinct zones (zonal) or replicating them automatically across all zones (zone-redundant).
Why This Is Optimal
Using availability zones is the best architectural approach for achieving high availability and fault isolation inside a single region without requiring complex multi-region replication architectures or incurring cross-region latency.
Resource groups
Resource groups
What Resource Groups Are
An Azure resource group is a logical container into which Azure resources—such as virtual machines, virtual networks, and storage accounts—are deployed and managed. It serves as an administrative and lifecycle management boundary for related cloud assets.
Why Resource Groups Do Not Meet the Requirement
Resource groups do not provide physical fault isolation or infrastructure redundancy. Placing resources in the same resource group or across different resource groups has no impact on where the physical hardware resides in the datacenter. If a physical failure occurs in the datacenter hosting those resources, the resource group provides no mechanism to prevent downtime.
Key Characteristics and Limitations
- Logical organization: Used to organize assets by application lifecycle, department, or environment.
- Access control boundary: Facilitates the assignment of Azure role-based access control (RBAC) permissions.
- Metadata storage: Stores metadata about the resources deployed within it.
- No physical isolation: Does not guarantee deployment across independent physical power or cooling systems.
This Answer Would Be Correct If
The requirement asked for a logical container to manage permissions, deploy templates, and track the lifecycle of related Azure resources collectively.
Management groups
Management groups
What Management Groups Are
Azure management groups are governance containers that sit above subscriptions in the Azure hierarchy. They allow organizations to manage access policies, compliance rules, and security controls across multiple Azure subscriptions simultaneously.
Why Management Groups Do Not Meet the Requirement
Management groups are strictly governance and administrative constructs. They do not manage the physical placement, execution, or runtime availability of virtual machine workloads. They cannot protect against physical datacenter disruptions or provide fault isolation against power, cooling, or network failures.
Key Characteristics and Limitations
- Hierarchical governance: Enables hierarchical structuring of subscriptions up to six levels of depth.
- Policy inheritance: Automatically applies Azure Policy and RBAC assignments to all child subscriptions.
- Compliance tracking: Aggregates compliance and security posture metrics across an enterprise.
- No workload orchestration: Has no role in routing application traffic or hosting redundant compute instances.
This Answer Would Be Correct If
The organization needed to enforce standardized compliance policies and role-based permissions across dozens of subscriptions from a centralized administrative structure.
Azure Reservations
Azure Reservations
What Azure Reservations Are
Azure Reservations (such as Reserved Virtual Machine Instances) are billing mechanisms that allow organizations to commit to one- or three-year plans for compute or storage services in exchange for significant discounts compared to pay-as-you-go pricing.
Why Azure Reservations Do Not Meet the Requirement
Reservations represent a financial commitment and pricing discount rather than a physical architecture or high-availability solution. Purchasing an Azure reservation does not automatically deploy, replicate, or isolate workloads across independent datacenter facilities to protect against physical infrastructure outages.
Key Characteristics and Limitations
- Cost management: Delivers substantial cost savings for workloads with predictable, continuous usage.
- Scope-based discounts: Can be scoped to individual subscriptions, shared across subscriptions, or applied at a management group level.
- Billing attribute: Applies discounts automatically to matching running resources without altering workload configurations.
- No uptime guarantees: Does not change the operational uptime or redundancy model of the deployed virtual machines.
This Answer Would Be Correct If
The objective was to lower operational costs for predictable, steady-state virtual machine workloads by committing to multi-year service usage.
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 Zone-Redundant Services
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 Cost vs Resiliency Trade-off
Describe availability zones
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Budget Alerts
Describe the consumption-based model
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