Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Azure Availability Sets Across Fault and Update Domains
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.
A company is planning to deploy two Azure virtual machines (VMs) to host a business-critical web application. The administrator needs to ensure the application remains operational during both planned platform maintenance and unexpected hardware failures on a server rack.
Which Azure compute capability should the administrator use to distribute the VMs across fault domains and update domains?
Explanations
Availability sets
Availability sets
What Availability Sets Are
An availability set is a logical grouping capability in Azure that isolates virtual machine (VM) resources from each other when deployed. Placing multiple VMs into an availability set ensures that they are spread across distinct physical hardware infrastructure within an Azure datacenter.
How Availability Sets Meet the Requirements
Availability sets protect applications against two specific types of events by distributing VMs across fault domains and update domains:
- Fault Domains (FDs): These represent physical units of hardware failure, such as a server rack sharing a common power source and physical network switch. Spreading VMs across fault domains protects the workload from localized hardware issues, disk failures, and power outages.
- Update Domains (UDs): These represent groups of underlying hardware nodes that can undergo planned maintenance or rebooting at the same time. Azure ensures only one update domain is rebooted at any given time, maintaining application uptime during platform patching.
Key Advantages and Capabilities
- Hardware Isolation: Separates VM instances across distinct racks to prevent single-point-of-failure disruptions.
- Coordinated Maintenance: Sequences platform updates so that remaining VM instances stay online to handle user traffic.
- Low Latency: Keeps VMs within the same datacenter or virtual network, maintaining low-latency communication between application tiers.
- No Additional Infrastructure Cost: Availability sets themselves are free of charge; you only pay for the individual VM instances created within them.
Why This Option Is Optimal
Configuring an availability set directly fulfills the requirement of safeguarding VMs against rack-level hardware failures and maintenance reboots through automated distribution across fault and update domains.
Azure Virtual Network Manager
Azure Virtual Network Manager
What Azure Virtual Network Manager Is
Azure Virtual Network Manager is a centralized management service that enables administrators to manage, group, configure, and secure virtual networks globally across Azure subscriptions.
Why Azure Virtual Network Manager Does Not Meet the Requirement
Azure Virtual Network Manager focuses exclusively on virtual network topology, routing configurations, and network security rules at scale. It does not provide host-level VM placement, high availability orchestration, or fault and update domain partitioning for compute workloads.
Key Characteristics and Limitations
- Centralized Network Management: Simplifies network group management and connectivity topologies across multiple subscriptions.
- Security Admin Rules: Enforces high-priority security policies across virtual networks.
- No Compute Clustering: Does not configure or manage VM compute redundancy, rack assignment, or host maintenance scheduling.
When This Option Would Be Correct
Azure Virtual Network Manager is ideal when an organization needs to centrally define mesh or hub-and-spoke network topologies and enforce network-level security policies across many virtual networks.
Paired regions
Paired regions
What Paired Regions Are
A regional pair consists of two Azure regions within the same geographic area that are separated by a large distance (typically at least 300 miles) to provide disaster recovery and cross-region redundancy.
Why Paired Regions Do Not Meet the Requirement
Paired regions are designed for large-scale disaster recovery to guard against geographic disasters and region-wide outages. They do not manage the granular distribution of individual virtual machines across local datacenter fault domains or update domains within a single deployment location.
Key Characteristics and Limitations
- Geographic Separation: Provides resilience against massive catastrophes like natural disasters or regional power grid failures.
- Sequential Updates: Platform updates are rolled out sequentially between paired regions to prevent simultaneous downtime across regions.
- Higher Network Latency: Cross-region communication incurs higher network latency compared to resources deployed within the same local availability set.
When This Option Would Be Correct
Paired regions are the right solution when designing a multi-region disaster recovery architecture to protect workloads against broad geographic or catastrophic regional outages.
Resource groups
Resource groups
What Resource Groups Are
A resource group is a logical container in Azure used to deploy, manage, and organize related Azure resources such as virtual machines, virtual networks, and storage accounts.
Why Resource Groups Do Not Meet the Requirement
Resource groups act solely as management and administrative boundaries. They do not dictate or control the underlying physical placement of virtual machines on server racks, nor do they separate workloads across fault domains or update domains to provide high availability during outages or maintenance.
Key Characteristics and Limitations
- Management Lifecycle: Resources in a resource group can be managed, monitored, and deleted together.
- Access Control and Governance: Serves as a scope for applying Azure Role-Based Access Control (RBAC) and Azure Policy.
- No Physical Redundancy: Assigning multiple VMs to the same resource group provides zero protection against hardware failures or scheduled host reboots.
When This Option Would Be Correct
Resource groups are appropriate when you need to group related resources for shared billing, lifecycle tracking, access control, or administrative organization.
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 Virtual Machine Scale Sets
Describe virtual machine options, including Azure virtual machines, Azure Virtual Machine Scale Sets, availability sets, and Azure Virtual Desktop
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Virtual Desktop
Describe virtual machine options, including Azure virtual machines, Azure Virtual Machine Scale Sets, availability sets, and Azure Virtual Desktop
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Virtual Machine Scale Sets
Describe virtual machine options, including Azure virtual machines, Azure Virtual Machine Scale Sets, availability sets, and Azure Virtual Desktop
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Virtual Machines IaaS
Describe virtual machine options, including Azure virtual machines, Azure Virtual Machine Scale Sets, availability sets, and Azure Virtual Desktop
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure RBAC Custom Roles
Describe Azure role-based access control (RBAC)
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