Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
How Azure Site Recovery Enables Disaster 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 enterprise runs business-critical server workloads and is designing a disaster recovery strategy to ensure business continuity during major outages.
The organization requires a solution that minimizes downtime and maintains data integrity by continuously replicating servers, capturing application-consistent recovery points, and automating failover to Azure.
Which Azure service should the organization implement to fulfill these requirements?
Explanations
Azure Site Recovery
Azure Site Recovery
What Azure Site Recovery Is
Azure Site Recovery (ASR) is Azure's native Disaster Recovery as a Service (DRaaS) solution designed to ensure business continuity by orchestrating the replication, failover, and recovery of virtual and physical workloads across primary and secondary locations.
How It Meets Business Continuity Requirements
Azure Site Recovery directly addresses the organization's disaster recovery needs by:
- Minimizing downtime: Continuously replicating machine data and orchestrating automated failover workflows so workloads can be restored rapidly in Azure when the primary site experiences an outage.
- Ensuring data integrity: Generating both crash-consistent snapshots and app-consistent snapshots (using Volume Shadow Copy Service / VSS) to capture memory data and in-flight transactions without data corruption.
- Maintaining recovery points: Retaining granular recovery points based on defined replication policies, allowing organizations to restore systems to specific historical points in time.
Key Advantages and Capabilities
- Automated orchestration: Simplifies complex failover and failback tasks across diverse environments (virtual machines and physical servers).
- Application consistency: Guarantees database-level and application-tier consistency during disaster recovery events.
- Delta synchronization: Optimizes network overhead and data transfer costs by transferring only delta changes computed via checksums.
- Non-disruptive testing: Supports disaster recovery drills and test failovers without affecting production workloads.
Why This Is Optimal
Unlike configuration or monitoring tools, Azure Site Recovery is specifically built for enterprise-grade disaster recovery, providing low Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) to maintain continuous operations during catastrophic disruptions.
Azure Policy
Azure Policy
What Azure Policy Is
Azure Policy is a governance and management service in Azure that evaluates resource properties against defined business rules to ensure organizational compliance, security standards, and service-level agreements.
Why It Doesn't Meet the Requirement
While Azure Policy can enforce corporate governance—such as requiring specific backup redundancy tiers or preventing deployments outside approved regions—it does not replicate server disks, create application snapshots, or orchestrate workload failover during a disaster.
Key Characteristics and Limitations
- Governance focus: Focuses on auditing and enforcing configuration rules rather than executing operational recovery.
- No data plane orchestration: Cannot manage or transfer disk delta data, memory states, or system processes.
- Compliance enforcement: Operates at the Azure Resource Manager level to govern resource creation and property modification.
This Answer Would Be Correct If
The organization needed to enforce a rule ensuring that all managed instances or databases are automatically configured with zone-redundant or geo-redundant storage policies.
Additional Context
Azure Policy plays a complementary governance role in business continuity by verifying that disaster recovery settings conform to corporate standards, but it is not a disaster recovery engine.
Azure Managed Grafana
Azure Managed Grafana
What Azure Managed Grafana Is
Azure Managed Grafana is a fully managed visualization and analytics platform built on the Grafana software that enables teams to query, visualize, and analyze operational metrics, logs, and dashboards.
Why It Doesn't Meet the Requirement
Azure Managed Grafana is an observability platform, not a disaster recovery tool. Furthermore, it does not provide native backup, replication, or failover functionality for underlying physical servers or enterprise workloads.
Key Characteristics and Limitations
- Observability focus: Specializes in rendering visual dashboards and analyzing monitoring telemetry.
- Single-region deployment: Deployed as a regional service that requires manual export/import workflows or external CI/CD pipelines to duplicate dashboard configurations.
- No compute replication: Has no capability to synchronize storage, create VSS app-consistent recovery points, or restore compute infrastructure.
This Answer Would Be Correct If
The organization needed a managed dashboard visualization tool to monitor metrics and resource health across their hybrid cloud infrastructure.
Additional Context
Monitoring platforms like Grafana can help identify outages or performance anomalies, but specialized disaster recovery solutions are required to restore impacted workloads.
Azure DNS
Azure DNS
What Azure DNS Is
Azure DNS is a hosting service for Domain Name System (DNS) domains that provides name resolution using Microsoft Azure infrastructure, offering high availability, fast query performance, and domain management.
Why It Doesn't Meet the Requirement
Although Azure DNS can be used to update alias or CNAME records to redirect network traffic to a disaster recovery endpoint during an outage, it does not perform server replication, capture disk snapshots, or manage recovery point retention.
Key Characteristics and Limitations
- Name resolution only: Translates domain names to IP addresses or other hostnames without managing underlying server states.
- No workload synchronization: Cannot capture application-consistent memory states or synchronize disk volumes.
- TTL dependency: Traffic redirection via DNS depends on Time-To-Live (TTL) expiration across global resolvers, which can delay failover.
This Answer Would Be Correct If
The scenario focused specifically on re-routing external user domain queries from a primary web endpoint to a secondary standby endpoint during an operational failover.
Additional Context
Azure DNS is frequently used alongside Azure Site Recovery to steer client traffic to recovered virtual machines once Site Recovery completes the failover process.
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 Cosmos DB Autoscale Provisioned Throughput
Describe the benefits of reliability and predictability in the cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Budgets
Describe the benefits of reliability and predictability in the cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Managed Disk Performance Tiers
Describe the benefits of reliability and predictability in the cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Availability Zones
Describe the benefits of reliability and predictability in the cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure RBAC Scope Inheritance
Describe Azure role-based access control (RBAC)
ExpertAZ-500 Microsoft Azure Security Technologies Exam
Application Permissions vs Delegated Permissions
Configure app registration permission scopes
Last updated Validated