Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Continuous VM Replication with Azure Site Recovery
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 hosts mission-critical enterprise workloads on Azure Virtual Machines in a primary region. To protect against major regional disruptions and ensure business continuity, the organization wants a solution that continuously replicates these virtual machines to a secondary target region and enables automated failover with minimal downtime.
Which Azure service should the organization implement to achieve this goal?
Explanations
Azure Backup configured with Locally Redundant Storage (LRS)
Azure Backup configured with Locally Redundant Storage (LRS)
What Azure Backup with LRS Is
Azure Backup is a cloud-based backup and data protection service that creates historical, point-in-time snapshots of systems and files. When configured with Locally Redundant Storage (LRS), data is replicated three times within a single physical data center in the local primary region.
Why It Doesn't Meet the Requirement
- No Cross-Region Protection: Because LRS keeps all data copies strictly within the local primary region, a regional outage makes both the source virtual machines and the backup copies completely inaccessible.
- Lacks Automated Failover: Azure Backup is intended for data restoration rather than live VM replication and dynamic failover orchestration. Restoring virtual machines from historical backups takes significantly longer than initiating a synchronized failover.
Key Characteristics and Limitations
- Single Region Scope: LRS does not replicate data across regions or availability zones.
- Point-in-Time Focus: Azure Backup protects against accidental deletion, ransomware, and corruption, rather than providing real-time replication for near-zero RTO.
- Manual VM Provisioning: Restoring VMs from backup archives requires provisioning steps rather than immediate automated standby activation.
This Answer Would Be Correct If
This option would be suitable if an organization needed a cost-effective solution to protect files and disks against local storage hardware failures within a single data center without requiring cross-region disaster recovery.
Azure Service Health unmanaged recovery
Azure Service Health unmanaged recovery
What Azure Service Health Unmanaged Recovery Is
Azure Service Health is an observability service that provides personalized guidance and notifications about Azure service status, planned maintenance, and regional service health disruptions. "Waiting for recovery" represents a passive approach where an organization relies entirely on Microsoft platform engineers to resolve a regional disruption.
Why It Doesn't Meet the Requirement
- No Redundancy or Active Replication: This approach does not replicate virtual machines to a secondary region or provide standby infrastructure.
- Uncontrollable Downtime: Organizations cannot control the recovery timeline, automate failovers, or meet strict business continuity and uptime service-level agreements.
- No Data Guarantee: If disks are not geo-replicated or protected by disaster recovery services beforehand, there are no synchronization guarantees during extended regional disasters.
Key Characteristics and Limitations
- Passive Strategy: Requires no pre-configured disaster recovery infrastructure but leaves services offline during an outage.
- Status Monitoring Only: Azure Service Health dashboard tracks outage progress but cannot execute technical failover commands.
- Prolonged Outages: Applications remain entirely offline until the primary cloud region's infrastructure is restored.
This Answer Would Be Correct If
This option would be appropriate only for non-critical, development, or test environments where downtime is fully acceptable and organizations prefer not to incur disaster recovery replication costs.
Azure DNS manual failover routing
Azure DNS manual failover routing
What Azure DNS Manual Failover Routing Is
Azure DNS is a hosting service for DNS domains that provides name resolution using Microsoft Azure infrastructure. Manual DNS failover involves manually updating DNS records (such as A or CNAME records) to point user traffic to an alternative secondary endpoint during an incident.
Why It Doesn't Meet the Requirement
- No Workload Replication: DNS services only manage network name resolution; they do not replicate virtual machine storage, system state, or configurations between regions.
- Manual Traffic Redirection: Updating DNS records manually does not automate the bring-up of compute workloads or orchestrate multi-tier application recovery.
- Caching and Latency Delays: DNS changes are subject to Time-to-Live (TTL) caching delays on client resolvers, which can prevent immediate traffic transition.
Key Characteristics and Limitations
- Network Routing Layer Only: Operates at the DNS resolution layer without insight into underlying VM compute states.
- Dependency on Standby Infrastructure: Requires a pre-existing, separately managed secondary environment that must already be synchronized through other tools.
- Manual Intervention Required: Requires an administrator to detect the failure and manually edit records during an emergency.
This Answer Would Be Correct If
This choice would be appropriate if the organization already maintained an active standby infrastructure in a secondary region and solely needed a mechanism to divert web traffic at the domain level.
Azure Site Recovery
Azure Site Recovery
What Azure Site Recovery Is
Azure Site Recovery (ASR) is Microsoft Azure's native Disaster Recovery as a Service (DRaaS) solution. It orchestrates and manages the continuous replication of physical servers, on-premises virtual machines, and cloud-based Azure Virtual Machines to secondary target locations, such as a paired Azure region.
How It Meets the Requirements
- Continuous Replication: Azure Site Recovery provides near real-time, block-level data replication from virtual machines running in a primary region to a secondary target region without impacting ongoing production operations.
- Automated Failover Orchestration: It allows administrators to build customized recovery plans that define the exact order in which multi-tier applications fail over, executing complex multi-VM failovers with a single click.
- Non-Disruptive Testing: ASR supports test failovers, allowing organizations to validate their disaster recovery drills and compliance readiness without causing downtime or disrupting ongoing replication.
Key Advantages and Capabilities
- Region-to-Region Disaster Recovery: Seamlessly integrates across Azure regions and region pairs to maintain business continuity.
- Application Consistency: Generates application-consistent recovery points for enterprise applications, reducing data reconstruction time during restore.
- Low RTO and RPO: Minimizes the Recovery Time Objective (RTO) and Recovery Point Objective (RPO) through automated failover and continuous synchronization.
- Simplified Failback: Automates the failback process to return workloads to the primary region once normal operations are restored.
Why This Is Optimal
Azure Site Recovery is specifically engineered for workload replication and rapid failover execution. Unlike point-in-time backup tools or manual DNS redirections, ASR maintains synchronized secondary workloads ready to run immediately when a primary region disruption occurs.
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 Region Pairs
Describe Azure regions, region pairs, and sovereign regions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Regional Pairs Data Residency
Describe Azure regions, region pairs, and sovereign regions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Government
Describe Azure regions, region pairs, and sovereign regions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Regions
Describe Azure regions, region pairs, and sovereign regions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Platform as a Service (PaaS)
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