Knowledge + Practice

CCNA Business Continuity Solutions Questions

51 of 201 questions · Page 3/3 · Business Continuity Solutions topic · Answers revealed

Practice these questions Exam hub All questions

151

MCQmedium

A company runs a critical application on Azure VMs in the West US region. They need to protect against a regional disaster using Azure Site Recovery. The VMs use unmanaged disks. The recovery point objective (RPO) must be 15 minutes and the recovery time objective (RTO) must be 1 hour. Additionally, they must be able to perform quarterly disaster recovery drills that do not affect the production environment. Which configuration should they use in Azure Site Recovery?

A.Set up replication with a 15-minute snapshot frequency and perform test failover for drills.

B.Use Azure Backup for VM replication and perform restore drills.

C.Configure a recovery plan with a pre-script to take a snapshot every 15 minutes.

D.Enable multi-VM consistency group with a 15-minute consistency frequency.

AnswerA

Correct: ASR allows configuring snapshot frequency (15 minutes meets RPO) and test failover is a built-in feature for drills.

Why this answer

Option A is correct because Azure Site Recovery supports replication of Azure VMs with unmanaged disks, and a 15-minute snapshot frequency meets the RPO requirement. Test failover allows quarterly disaster recovery drills without impacting the production environment, as it creates isolated copies of VMs in a separate network for validation.

Exam trap

The trap here is confusing Azure Backup (long-term backup) with Azure Site Recovery (replication for disaster recovery), as both can restore VMs but only Site Recovery supports low RPOs and non-disruptive test failovers.

How to eliminate wrong answers

Option B is wrong because Azure Backup is designed for long-term backup retention and restore, not for low-RPO replication (typically 1-2 snapshots per day) and does not support the 15-minute RPO or test failover drills without affecting production. Option C is wrong because recovery plans with pre-scripts cannot take snapshots at a fixed frequency; snapshot frequency is configured at the replication policy level, not via scripts in a recovery plan. Option D is wrong because multi-VM consistency groups ensure crash-consistent or app-consistent snapshots across multiple VMs, but they do not directly set the snapshot frequency; the consistency frequency is separate from the replication frequency, and this option does not address the drill requirement.

Practice this question →

152

MCQmedium

A company uses Azure Site Recovery to replicate critical Azure virtual machines (VMs) to a secondary Azure region for disaster recovery. The VMs use managed disks and are part of a multi-tier application. After a failover, the recovery VMs must be automatically placed into a specific availability set to maintain the application architecture. How should the administrator configure this in Azure Site Recovery?

A.Configure the target availability set in the VM replication settings in the Recovery Services vault

B.Create a recovery plan and add a manual step or script to move VMs to the availability set after failover

C.Convert the managed disks to unmanaged disks for replication, then specify the availability set

D.Azure Site Recovery does not support placing VMs into an availability set in the target region

AnswerA

For managed disk VMs, ASR provides an option to select the target availability set in the replication configuration, ensuring automatic placement after failover.

Why this answer

Option A is correct because Azure Site Recovery (ASR) allows you to configure the target availability set directly in the replication settings for each VM. When you enable replication for a VM, under the 'Target availability set' setting, you can select an existing availability set in the target region. ASR will then automatically place the recovered VM into that availability set during failover, ensuring the multi-tier application architecture is maintained without manual intervention.

Exam trap

The trap here is that candidates may assume ASR lacks native support for availability sets and default to manual recovery plans or unnecessary disk conversions, overlooking the straightforward configuration option in the replication settings.

How to eliminate wrong answers

Option B is wrong because while recovery plans can include manual steps or scripts, this approach is inefficient and error-prone; ASR natively supports specifying the target availability set in the replication settings, eliminating the need for post-failover manual steps. Option C is wrong because converting managed disks to unmanaged disks is unnecessary and not a supported method for specifying availability sets; ASR works with managed disks and the availability set is configured independently in the replication settings. Option D is wrong because Azure Site Recovery does support placing VMs into an availability set in the target region, as demonstrated by the correct configuration in Option A.

Practice this question →

153

MCQmedium

A company runs a critical web application on Azure VMs in two availability zones. They need to ensure the application remains available during a regional outage with an RPO of 5 minutes and an RTO of 15 minutes. What should they implement?

A.Azure Backup

B.Azure Traffic Manager

C.Azure Site Recovery

D.Azure Front Door

AnswerC

Site Recovery provides replication with RPO as low as 5 minutes and supports RTO of 15 minutes.

Why this answer

Option B is correct because Azure Site Recovery can replicate VMs to a secondary Azure region with a recovery point objective (RPO) as low as 5 minutes and recovery time objective (RTO) measured in minutes. Option A is wrong because Azure Front Door provides global load balancing and caching, but does not handle VM replication. Option C is wrong because Azure Backup has a minimum RPO of 12 hours for VMs.

Option D is wrong because Azure Traffic Manager only provides DNS-based traffic routing, not VM replication.

Practice this question →

154

MCQhard

A healthcare organization stores patient records in Azure Blob Storage with a hot access tier in the East US region. The compliance policy requires that data be recoverable within 1 hour in the event of a regional disaster. The data is updated every 10 minutes and must be recoverable to a consistent state within 15 minutes of failure. Which configuration should you implement?

A.Use object replication with a minimum RPO of 15 minutes and configure read-access in the secondary region

B.Use RA-GRS (read-access geo-redundant storage) and configure storage account failover

C.Use GRS (geo-redundant storage) with automated failover

D.Use GZRS (geo-zone-redundant storage) with customer-managed failover

AnswerA

Object replication meets RPO; read-access meets RTO.

Why this answer

Option D is correct because object replication with a minimum Replication Time Objective (RTO) of 15 minutes meets the RPO requirement, and a secondary read-access region meets the RTO of 1 hour. Option A is wrong because RA-GRS has an RPO of 15 minutes but failover is manual and may take longer. Option B is wrong because GZRS with manual failover may exceed RTO.

Option C is wrong because geo-redundant storage (GRS) does not provide read access in the secondary region.

Practice this question →

155

MCQmedium

A company runs a web application on Azure App Service with a backing Azure SQL Database in a single region. They need to ensure availability during an Azure region outage. The solution must automatically fail over the entire application stack with minimal data loss and redirect user traffic to the secondary region. Which combination of Azure services should they implement?

A.Azure Traffic Manager with active-passive and geo-replication for Azure SQL Database

B.Azure Front Door with active-active or active-passive routing and auto-failover groups for Azure SQL Database

C.Azure Application Gateway with backend pools in multiple regions and SQL Database failover groups

D.Azure Load Balancer with multiple regions and Azure SQL Database automatic failover

AnswerB

Azure Front Door provides global HTTP/HTTPS routing with health probes and automatic failover, and auto-failover groups for SQL Database provide geo-replication with automatic failover, meeting RPO and RTO requirements.

Why this answer

Azure Front Door provides global HTTP(S) load balancing with automatic failover between regions, and when combined with auto-failover groups for Azure SQL Database, it ensures the entire application stack (web + database) fails over together with minimal data loss. The auto-failover group replicates the database synchronously within the same region and asynchronously across regions, allowing a user-configurable grace period to trade off between data loss and availability. This matches the requirement for automatic, coordinated failover of the full stack and traffic redirection.

Exam trap

The trap here is that candidates often confuse Azure Traffic Manager (DNS-level, no application health awareness) with Azure Front Door (HTTP/S-level, health-probe driven), and they overlook that auto-failover groups are required for SQL Database to achieve coordinated, automatic failover with minimal data loss, rather than relying on geo-replication alone.

How to eliminate wrong answers

Option A is wrong because Azure Traffic Manager operates at the DNS level and does not provide automatic end-to-end failover coordination with the database; it also lacks native support for health probes that can detect application-level failures, and geo-replication for SQL Database alone does not provide automatic failover with minimal data loss (it requires manual or scripted failover). Option C is wrong because Azure Application Gateway is a regional load balancer and cannot route traffic across multiple regions for global failover; it is designed for layer-7 traffic within a single region. Option D is wrong because Azure Load Balancer is a regional, layer-4 load balancer that cannot distribute traffic across multiple regions or provide global failover; SQL Database automatic failover (without auto-failover groups) does not support a coordinated, policy-driven failover with a secondary region.

Practice this question →

156

MCQmedium

A company runs a critical application on Azure VMs. They want to ensure high availability within a region using Azure Site Recovery. What is the correct configuration?

A.Configure Azure Site Recovery to replicate VMs to a paired region

B.Deploy VMs across multiple availability zones and use a load balancer

C.Use Azure Site Recovery to replicate VMs across availability sets

D.Configure Azure Site Recovery to replicate VMs to different availability zones within the same region

AnswerB

Availability zones provide intra-region high availability.

Why this answer

Option B is correct because Azure Site Recovery is designed for disaster recovery across regions, not within a region. For intra-region high availability, availability zones should be used. Option A is wrong because Site Recovery does not support intra-region replication to availability zones directly.

Option C is wrong because Site Recovery cannot replicate across availability sets. Option D is wrong because Site Recovery can replicate across zones but is not the best practice for intra-region HA.

Practice this question →

157

MCQmedium

A company runs a critical application on Azure VMs and an Azure SQL Managed Instance in a single region. They need a disaster recovery solution with a Recovery Point Objective (RPO) of 5 minutes for the database and a Recovery Time Objective (RTO) of 2 hours for the entire stack. They want to minimize cost and use native Azure services. Which combination should they implement?

A.Azure Site Recovery for VMs and active geo-replication for the database

B.Azure Backup for VMs and auto-failover groups for the database

C.Azure Site Recovery for VMs and auto-failover groups for the database

D.Deploy a second region with VMs and database replicas manually configured and Azure Traffic Manager

AnswerC

Azure Site Recovery replicates VMs to a secondary region with RPO of seconds to minutes and RTO of hours, and auto-failover groups provide geo-replication and automatic failover for Azure SQL Managed Instance with RPO of seconds.

Why this answer

Option C is correct because Azure Site Recovery (ASR) provides orchestrated replication and failover for Azure VMs, meeting the 2-hour RTO for the entire stack, while auto-failover groups for Azure SQL Managed Instance enable automatic, synchronous or asynchronous replication with an RPO as low as 5 minutes using the built-in distributed availability groups feature. This combination uses native Azure services without manual scripting, minimizing cost and complexity.

Exam trap

The trap here is confusing active geo-replication (which only applies to Azure SQL Database) with auto-failover groups (which are required for Azure SQL Managed Instance), leading candidates to incorrectly select Option A.

How to eliminate wrong answers

Option A is wrong because active geo-replication is not supported for Azure SQL Managed Instance; it is only available for Azure SQL Database (single or elastic pool), and Managed Instance requires auto-failover groups for geo-replication. Option B is wrong because Azure Backup for VMs is designed for backup and restore, not for continuous replication and rapid failover, so it cannot achieve a 2-hour RTO for the entire stack; it typically has RTOs measured in hours to days. Option D is wrong because manually configuring a second region with VMs and database replicas and using Azure Traffic Manager increases operational overhead and cost, and does not leverage native Azure DR services like ASR or auto-failover groups, violating the 'minimize cost and use native Azure services' requirement.

Practice this question →

158

MCQmedium

A company runs multiple on-premises workloads that are critical. They need a disaster recovery solution that can replicate workloads to Azure and enable failover in the event of an on-premises outage. The solution must support non-VMware and non-Hyper-V physical servers. Which Azure service should they use?

A.Azure Backup

B.Azure Site Recovery

C.Azure Migrate

D.Azure Disaster Recovery

AnswerB

Azure Site Recovery supports replication of physical servers (and virtual machines) to Azure. It provides failover and test failover capabilities for DR.

Why this answer

Azure Site Recovery (ASR) is the correct service because it provides orchestrated replication and failover for on-premises physical servers (including non-VMware, non-Hyper-V) to Azure. It supports physical-to-Azure (P2A) replication using the Mobility service installed on the source server, enabling automated failover during an outage. This directly meets the requirement for critical workload disaster recovery with failover capability.

Exam trap

The trap here is that candidates often confuse Azure Backup (data protection) with Azure Site Recovery (disaster recovery with failover), or assume that 'Azure Disaster Recovery' is a valid service name, when in fact the correct service is Azure Site Recovery.

How to eliminate wrong answers

Option A is wrong because Azure Backup is designed for backup and restore of data (files, folders, VMs, databases) to a Recovery Services vault, not for continuous replication and automated failover orchestration required for disaster recovery. Option C is wrong because Azure Migrate is a tool for assessing and migrating on-premises workloads to Azure, not for ongoing replication and failover after migration. Option D is wrong because 'Azure Disaster Recovery' is not a standalone Azure service; the correct service name is Azure Site Recovery, and this option is a distractor that does not exist as a named service.

Practice this question →

159

MCQhard

Your organization has a hybrid identity infrastructure using Microsoft Entra ID (formerly Azure AD) and Active Directory Domain Services (AD DS) on-premises. You plan to deploy a critical application on Azure VMs that must remain available even if the on-premises network connection fails. The application authenticates users via on-premises AD DS. You need to design an identity disaster recovery solution that works during a network outage. What should you implement?

A.Create a site-to-site VPN connection with a secondary on-premises data center.

B.Configure Azure AD Connect with password hash synchronization and enable seamless single sign-on.

C.Deploy Microsoft Entra Domain Services and join the Azure VMs to the managed domain.

D.Use Azure AD Application Proxy to publish the application and authenticate via Azure AD.

AnswerC

Entra Domain Services provides AD DS in the cloud, accessible even if on-premises is down.

Why this answer

Option C is correct because deploying Microsoft Entra Domain Services in Azure provides managed domain services independent of on-premises connectivity. The application can authenticate using Entra Domain Services. Option A (Azure AD Connect) does not provide authentication if on-premises is unreachable.

Option B (VPN gateway) does not help if the on-premises network is down. Option D (Azure AD Application Proxy) is for remote access, not authentication.

Practice this question →

160

MCQmedium

A company has an on-premises application running on physical servers with various operating systems. They want to use Azure as a disaster recovery site with an RPO of less than 1 hour and an RTO of less than 4 hours. They need to replicate the servers to Azure and support failover and failback. Which Azure service should they use?

A.Azure Site Recovery

B.Azure Backup (MARS agent)

C.Azure Migrate

D.Azure File Sync

AnswerA

ASR provides continuous replication for physical servers to Azure, enabling failover and failback with RPO as low as 30 seconds and RTO in hours, meeting the requirements.

Why this answer

Azure Site Recovery (ASR) orchestrates replication, failover, and failback for physical servers and VMs to Azure, meeting the RPO of <1 hour and RTO of <4 hours. It supports heterogeneous operating systems on physical servers and provides continuous replication with recovery points as low as 30 seconds, enabling both planned and unplanned failover with full failback capability.

Exam trap

The trap here is that candidates confuse Azure Backup (which provides long-term archival backups) with Azure Site Recovery (which provides near-continuous replication and orchestrated failover), failing to recognize that the RPO and RTO requirements demand a replication-based DR solution, not a backup service.

How to eliminate wrong answers

Option B (Azure Backup with MARS agent) is wrong because it is designed for file/folder and system state backup with a minimum RPO of 1 day (daily backup), not sub-hourly replication, and it does not support orchestrated failover or failback of entire servers. Option C (Azure Migrate) is wrong because it is a discovery, assessment, and migration tool, not a disaster recovery service; it does not provide ongoing replication or failover/failback capabilities. Option D (Azure File Sync) is wrong because it only syncs file shares between on-premises and Azure, not entire server workloads, and lacks failover/failback orchestration for disaster recovery.

Practice this question →

161

MCQmedium

Your company runs an on-premises application that needs to be failed over to Azure in the event of a disaster. The application uses a SQL Server database and requires an RPO of 15 minutes and an RTO of 1 hour. You plan to use Azure Site Recovery (ASR) for the VMs and Azure SQL Database for the database. Which combination of actions should you take?

A.Use ASR with 5-minute replication and configure SQL Server Log Shipping to an Azure VM.

B.Use ASR with 30-minute replication frequency and backup the SQL Server database every 15 minutes.

C.Use ASR with 15-minute replication for the VMs and configure a failover group for Azure SQL Database with active geo-replication.

D.Use ASR with 15-minute replication and restore the SQL Server database from backup.

AnswerC

ASR provides VM replication; failover group provides database failover within RTO.

Why this answer

Option C (ASR for VMs with 15-minute replication and SQL Database failover group) meets both RPO and RTO. Option A (longer RPO). Option B (manual restore) does not meet RTO.

Option D (Log Shipping) is not native to Azure SQL Database.

Practice this question →

162

MCQmedium

A company runs a file server on an Azure VM in the East US region. They want to back up the file shares to Azure and be able to restore individual files if accidentally deleted. They also need to be able to restore the entire file share to a secondary region (West US) in case of a regional disaster. The solution should automatically protect the file shares and provide versioning for up to 30 days. Which Azure service and configuration should they recommend?

A.Configure Azure Backup on the Azure file share using a Recovery Services vault with geo-redundant storage (GRS). Enable cross-region restore on the vault.

B.Use Azure File Sync to sync the file share to an on-premises server, and then back up the on-premises server using Azure Backup.

C.Enable soft delete and versioning on the storage account, and configure replication to a secondary region using RA-GRS.

D.Create a scheduled Azure Automation runbook that takes snapshots of the file share every day and copy them to a storage account in West US.

AnswerA

Azure Backup for Azure Files provides daily backups, file-level restore, and versioning. With GRS and cross-region restore enabled, you can restore the entire share to the paired region.

Why this answer

Azure Backup for Azure file shares uses a Recovery Services vault and can be configured with geo-redundant storage (GRS) to replicate backup data to a paired secondary region. Enabling cross-region restore on the vault allows restoring the entire file share to the secondary region (West US) during a regional disaster. Azure Backup automatically protects the file share with scheduled backups and provides up to 30 days of retention for point-in-time restores of individual files or the entire share.

Exam trap

The trap here is that candidates often confuse storage account replication (RA-GRS) with backup and restore capabilities, thinking that replication alone provides disaster recovery restore functionality, but it does not support point-in-time file-level restore or cross-region restore of backups without Azure Backup's cross-region restore feature.

How to eliminate wrong answers

Option B is wrong because Azure File Sync is designed for hybrid sync and tiering, not for backup; it does not provide native cross-region disaster recovery or versioning for up to 30 days, and backing up an on-premises server adds unnecessary complexity and does not directly meet the requirement to restore to a secondary Azure region. Option C is wrong because soft delete and versioning on the storage account provide protection against accidental deletion and overwrites, but they do not offer a backup solution with scheduled backups, cross-region restore capability, or the ability to restore the entire file share to a secondary region in a disaster scenario; RA-GRS replication is for storage account data redundancy, not for backup restore. Option D is wrong because a scheduled Azure Automation runbook that takes snapshots and copies them to another region is a custom, non-native solution that lacks the automated backup scheduling, versioning, and cross-region restore capabilities provided by Azure Backup; it also introduces operational overhead and does not guarantee the 30-day versioning requirement.

Practice this question →

163

MCQmedium

You are designing a backup strategy for Azure VMs that host a file server. The backup must support daily backups with a retention of 30 days, and the ability to restore individual files quickly. The solution must minimize backup storage costs. What backup policy should you configure?

A.Use Azure Backup with daily backup, retention of 30 days, and use locally redundant storage (LRS) for backup data.

B.Use Azure Backup with daily backup, retention of 30 days, and enable instant restore snapshot for file-level recovery.

C.Use Azure Backup with daily backup, retention of 30 days, and use geo-redundant storage (GRS) for backup data.

D.Use Azure Backup with weekly backup, retention of 30 days, and use geo-redundant storage (GRS) for backup data.

AnswerA, B

LRS is cost-effective and meets the retention and file recovery needs.

Why this answer

Azure Backup with instant restore snapshots allows quick file-level recovery. Using GRS (geo-redundant storage) adds cost unnecessarily for this requirement. Option A is incorrect because LRS is sufficient.

Option B is incorrect because it limits file recovery. Option D is incorrect because it adds cost without benefit.

Practice this question →

164

MCQmedium

A company runs a critical application on Azure virtual machines in the West US region. They need a disaster recovery solution that replicates VMs to East US with a recovery point objective (RPO) of 15 minutes and a recovery time objective (RTO) of 2 hours. They also need to perform non-disruptive disaster recovery drills. Which Azure service should they use?

A.Azure Backup

B.Azure Site Recovery

C.Azure Traffic Manager

D.Azure Front Door

AnswerB

Azure Site Recovery replicates VMs to a secondary region, supports flexible RPO (e.g., 15 minutes), and enables test failover for non-disruptive drills.

Why this answer

Azure Site Recovery (ASR) orchestrates replication, failover, and failback of Azure VMs between regions. It supports RPOs as low as 15 minutes (continuous replication with crash-consistent or app-consistent snapshots) and RTOs of 2 hours or less, and it enables non-disruptive disaster recovery drills via test failover that isolates replicated VMs in a separate virtual network without impacting production.

Exam trap

The trap here is that candidates confuse Azure Backup (which is for backup/restore with longer RPOs) with Azure Site Recovery (which is for replication and failover with low RPO/RTO), or they mistakenly think a traffic-routing service like Traffic Manager or Front Door can provide disaster recovery replication without actually moving or copying VM data.

How to eliminate wrong answers

Option A is wrong because Azure Backup is designed for long-term retention and point-in-time restore of VM data (typically with a minimum RPO of 1 hour for disk snapshots), not for continuous replication with sub-15-minute RPO or orchestrated failover with a 2-hour RTO; it also does not support non-disruptive drills. Option C is wrong because Azure Traffic Manager is a DNS-based traffic load balancer that routes incoming traffic to healthy endpoints, but it does not replicate VM data or provide any disaster recovery replication, RPO/RTO guarantees, or drill capabilities. Option D is wrong because Azure Front Door is a global application delivery network with HTTP/S load balancing and acceleration, but it does not handle VM-level replication, failover orchestration, or recovery point objectives; it only redirects traffic based on backend health.

Practice this question →

165

MCQmedium

You are designing a backup strategy for Azure Files shares that contain critical data. The backup must support snapshot-based backups and allow restoration to a specific point in time. The solution must also protect against accidental deletion. What should you use?

A.Use Azure File Sync with cloud tiering.

B.Use Azure Storage account geo-redundant storage (GRS) with versioning.

C.Use Azure Backup for Azure Files with soft delete enabled.

D.Use Azure Backup for Azure Files without soft delete.

AnswerC

Azure Backup provides snapshot-based backups and point-in-time restore; soft delete protects against accidental deletion.

Why this answer

Azure Backup for Azure Files provides snapshot-based backups with point-in-time restore and soft delete protection. Option A is incorrect because Storage Accounts replication does not provide point-in-time restore. Option C is incorrect because file sync does not provide backup.

Option D is incorrect because it lacks soft delete.

Practice this question →

166

Multi-Selecteasy

Your company is designing a disaster recovery solution for a three-tier application hosted on Azure VMs. The solution must meet the following requirements: - RPO: 1 hour - RTO: 4 hours - Automated failover to a secondary region - Cost optimization is a priority Which TWO actions should you include in the design?

Select 2 answers

A.Deploy an Azure Load Balancer in the secondary region with health probes to automatically route traffic after failover.

B.Use Azure Backup to take hourly backups of the VMs and restore them in the secondary region.

C.Configure a read-only replica of the application tier in the secondary region using Availability Zones.

D.Deploy Azure Front Door with a backend pool containing both primary and secondary regions.

E.Configure Azure Site Recovery replication for all application VMs from primary to secondary region.

AnswersA, E

Load balancer with health probes can redirect traffic to healthy backend VMs in the secondary region.

Why this answer

Options A and C are correct. Azure Site Recovery provides replication and automated failover for VMs, meeting RPO and RTO. Using an Azure Load Balancer with health probes allows traffic to be redirected to the secondary region after failover.

Option B is wrong because Azure Backup is not designed for automated failover and has higher RTO. Option D is wrong because read-only replicas are for read scaling, not failover. Option E is wrong because Azure Front Door is for global load balancing, not regional failover for VMs.

Practice this question →

167

Multi-Selecthard

Which THREE of the following are best practices for designing a business continuity solution using Azure Backup? (Choose three.)

Select 3 answers

A.Enable soft delete to protect backup data from accidental deletion

B.Configure a single backup policy for all resources to simplify management

C.Use geo-redundant storage (GRS) for the backup data to protect against regional disasters

D.Use separate Recovery Services vaults for different workloads or regions

E.Grant all users 'Backup Contributor' role to ensure backups are taken

AnswersA, C, D

Soft delete provides an additional layer of protection.

Why this answer

Options A, C, and D are correct. Using a Recovery Services vault per workload or per region helps with isolation (A). Enabling soft delete protects against accidental deletion (C).

Using geo-redundant storage (GRS) for backup data provides cross-region protection (D). Option B is wrong because backup policies should be based on RPO, not a fixed number of policies. Option E is wrong because RBAC should be used to restrict access, not grant everyone access.

Practice this question →

168

MCQmedium

A company runs a critical application on Azure VMs. They want to back up the VMs using Azure Backup. The retention requirements are: daily backups for 35 days, weekly backups for 52 weeks, and yearly backups for 10 years. Which backup policy should they create?

A.Create a custom backup policy with a daily backup schedule and retention rules for daily (35), weekly (52), and yearly (10 years)

B.Use the default backup policy provided by Azure Backup

C.Use Azure Site Recovery (ASR) to replicate the VMs and meet the retention

D.Use Azure Backup for VMs with instant recovery enabled

AnswerA

Correct. Custom policies allow you to configure multiple retention rules per frequency.

Why this answer

Option A is correct because Azure Backup allows you to create a custom backup policy that defines a daily backup schedule and separate retention rules for daily, weekly, and yearly retention points. This directly meets the requirement of 35 days daily, 52 weeks weekly, and 10 years yearly retention, as Azure Backup supports granular retention policies with multiple tiers (daily, weekly, monthly, yearly) within a single policy.

Exam trap

The trap here is that candidates may confuse Azure Backup's default policy (which only covers short-term retention) with the ability to customize retention tiers, or mistakenly think Azure Site Recovery can serve as a backup solution for long-term retention, when in fact it is for replication and failover, not backup retention.

How to eliminate wrong answers

Option B is wrong because the default backup policy in Azure Backup typically retains daily backups for only 30 days (not 35) and does not include weekly or yearly retention rules, so it cannot meet the specified requirements. Option C is wrong because Azure Site Recovery (ASR) is designed for disaster recovery and replication, not for long-term backup retention; it does not support retention policies for years and is not a backup solution for meeting retention schedules. Option D is wrong because instant recovery is a feature that enables faster restore from snapshots, but it does not modify or extend retention policies; the default or custom policy still governs retention, and instant recovery alone cannot satisfy the 35-day, 52-week, and 10-year retention requirements.

Practice this question →

169

Multi-Selecthard

A mission-critical web application must tolerate a full Azure region outage. The business requires automatic failover and global HTTP acceleration. Which two components should be included in the design? (Choose 2.)

Select 2 answers

A.Deploy the application to at least two Azure regions.

B.Use Azure Front Door with health probes and origin failover.

C.Use only availability zones in one region.

D.Use Azure Bastion for failover routing.

AnswersA, B

A single-region deployment cannot survive a full regional outage.

Why this answer

Option A is correct because deploying the application to at least two Azure regions provides geographic redundancy, ensuring that if one entire region fails, the application can still operate from the other region. This is a fundamental requirement for tolerating a full region outage. Option B is correct because Azure Front Door provides global HTTP acceleration and automatic failover by using health probes to monitor endpoint health and routing traffic to healthy origins, which meets the business requirements for both automatic failover and performance.

Exam trap

The trap here is that candidates often confuse availability zones (which protect against datacenter failures within a region) with multi-region deployments (which are required for region outage tolerance), leading them to incorrectly select Option C as sufficient.

Practice this question →

170

MCQhard

You are designing a business continuity solution for a global e-commerce platform that runs on Azure Kubernetes Service (AKS) in multiple regions. The application must remain available even if an entire Azure region fails. The application uses Azure Cosmos DB for its database. You need to ensure that the application can continue to serve traffic with minimal disruption. What should you recommend?

A.Use Cosmos DB with geo-redundant storage and deploy a single AKS cluster with Azure Site Recovery.

B.Deploy AKS clusters in two regions with Azure Traffic Manager and use Cosmos DB single-region writes with async replication.

C.Configure Cosmos DB with multi-region writes and deploy AKS clusters in two regions behind Azure Front Door.

D.Deploy the application to a single region and use Azure Backup for Cosmos DB to restore in another region.

AnswerC

Multi-region writes enable active-active with automatic failover.

Why this answer

Option B (multi-region write Cosmos DB with multi-region AKS) provides active-active architecture with automatic failover. Option A (single-region with backups) has high RTO. Option C (geo-redundant storage) is for data only.

Option D (Traffic Manager with passive) has lower availability.

Practice this question →

171

MCQhard

A company runs a critical multi-tier application on Azure VMs. The application includes a database tier that requires recovery across multiple VMs at the same point in time. The company uses Azure Site Recovery (ASR) for disaster recovery to a secondary region. The recovery point objective (RPO) is 15 minutes and the recovery time objective (RTO) is 1 hour. The database VMs have a high data change rate, and the company wants to minimize replication costs. Which combination of ASR configurations should they implement?

A.Use multi-VM consistency groups and set the replication frequency to 15 minutes.

B.Enable application-consistent recovery for all VMs and use ExpressRoute.

C.Use standard recovery plans and default replication policy.

D.Configure a single recovery plan with manual failover and use Premium SSD managed disks.

AnswerA

Multi-VM consistency groups ensure crash-consistent recovery of all VMs to the same point. Setting replication frequency to 15 minutes meets the RPO and reduces the number of recovery points, lowering storage and network costs compared to the default 5-minute frequency.

Why this answer

Option A is correct because multi-VM consistency groups in Azure Site Recovery ensure that all VMs in the group are recovered to the same crash-consistent point in time, which meets the requirement for cross-VM recovery. Setting the replication frequency to 15 minutes aligns with the 15-minute RPO while minimizing replication costs by avoiding more frequent replication (e.g., 5 minutes) that would increase bandwidth and storage costs.

Exam trap

The trap here is that candidates often confuse application-consistent recovery (which ensures each VM's OS and apps are consistent) with cross-VM consistency (which ensures all VMs are recovered to the same point in time), leading them to choose Option B or C without recognizing the need for multi-VM consistency groups.

How to eliminate wrong answers

Option B is wrong because application-consistent recovery for all VMs does not guarantee cross-VM point-in-time consistency; it only ensures each VM is application-consistent individually, and ExpressRoute is a network connectivity option that does not affect replication consistency or cost. Option C is wrong because standard recovery plans and default replication policy (typically 5-minute frequency) would not minimize costs and may not provide the required cross-VM consistency without a consistency group. Option D is wrong because a single recovery plan with manual failover does not ensure simultaneous recovery at the same point in time across VMs, and Premium SSD managed disks are a storage performance choice unrelated to replication consistency or cost minimization.

Practice this question →

172

Multi-Selectmedium

A company needs to design a disaster recovery solution for a multi-tier application that includes a web tier, a business tier, and a database tier. The solution must meet the following requirements: - RPO of 15 minutes for the database - RTO of 1 hour for the entire application - Automatic failover for the database - No data loss for the web and business tiers (stateless) Which TWO services should be included in the solution? (Choose two.)

Select 2 answers

A.Azure Backup

B.Azure Traffic Manager

C.Azure Site Recovery for VM replication

D.Azure Front Door

E.Azure SQL Database active geo-replication

AnswersB, E

Routes traffic to healthy region for stateless tiers.

Why this answer

Option B and Option D are correct. Azure SQL Database active geo-replication provides automatic failover with an RPO of 5 seconds, well within 15 minutes. Azure Traffic Manager can route traffic to the secondary region stateless tiers.

Option A is wrong because Azure Site Recovery is not needed for stateless tiers; they can be redeployed. Option C is wrong because Azure Front Door is not necessary for a simple DR scenario. Option E is wrong because Azure Backup does not provide automatic failover.

Practice this question →

173

MCQmedium

Fabrikam Inc. runs a file-sharing service used by 500 employees globally. The service is deployed on Azure VMs in the North Europe region. The VMs store data on Azure Files shares (Standard performance tier) mounted via SMB. The company's business continuity policy requires: - RPO: 1 hour for any data loss. - RTO: 4 hours to restore service after a regional disaster. - All data must be backed up and recoverable in a different region. - Budget is a concern; prefer cost-effective solutions. Currently, there is no backup in place. You need to design a solution. What should you do?

A.Set up Azure Site Recovery (ASR) for the VMs and Azure Files. Replicate to a secondary region (West Europe). Use ASR recovery plans to orchestrate failover.

B.Configure Azure Backup for the Azure Files shares with a backup policy of 1-hour frequency. Also back up the VMs using Azure Backup with a 1-hour policy. Store backups in a Recovery Services vault with geo-redundant storage (GRS). Enable cross-region restore.

C.Use Azure Files share snapshots taken every hour and store them in a separate storage account in the same region. For VM backup, use Azure Backup with daily frequency. In a disaster, deploy new VMs and restore from snapshots.

D.Implement Azure File Sync between the Azure Files share and an on-premises file server. For disaster recovery, failover to the on-premises server.

AnswerB

Azure Backup meets the RPO and RTO with cross-region restore, and is cost-effective.

Why this answer

Option B is correct because Azure Backup for Azure Files can schedule backups every hour (meeting 1-hour RPO) and store them in a Recovery Services vault with geo-redundant storage (GRS) to recover in another region. For the VMs, Azure Backup can also protect them with a 1-hour frequency. Cross-region restore enables recovery in a secondary region.

Option A is wrong because Azure Site Recovery is more expensive and may not be needed for this RTO. Option C is wrong because Azure Files snapshots are manual and do not provide cross-region recovery. Option D is wrong because Azure File Sync is for sync, not backup.

Practice this question →

174

MCQmedium

Your company runs a Windows-based application on Azure Virtual Machines in the Brazil South region. The application uses Azure Files for shared storage and Azure SQL Database (Hyperscale tier) for the database. The business requires a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 30 minutes for the entire application. The solution must be cost-effective and leverage Azure-native services. You have been asked to design the disaster recovery strategy. Which option should you recommend?

A.Use Azure Site Recovery to replicate the VMs to a secondary region. Configure geo-redundant storage (GRS) for Azure Files. For Azure SQL Database Hyperscale, enable geo-restore and test restore procedures.

B.Deploy a second set of VMs in a secondary region. Use Azure File Sync to keep Azure Files in sync. Use Azure SQL Database failover groups with a readable secondary.

C.Back up the VMs using Azure Backup with a 15-minute frequency. Use Azure File Sync to replicate Azure Files to a secondary region. Use Azure SQL Database backup with point-in-time restore.

D.Use Azure Site Recovery for VMs. Use Azure File Sync for Azure Files. Use active geo-replication for Azure SQL Database.

AnswerA

Azure Site Recovery meets RPO/RTO for VMs; GRS for Azure Files provides automatic replication; Hyperscale geo-restore can restore a database in minutes.

Why this answer

Option A is correct because Azure Site Recovery for VMs provides 15-minute RPO and fast RTO; geo-redundant storage for Azure Files meets RPO; Azure SQL Database Hyperscale geo-restore can achieve RTO within 30 minutes. Option B is wrong because Azure Backup for VMs has slower RTO. Option C is wrong because Azure File Sync is for hybrid scenarios, not DR.

Option D is wrong because active geo-replication for SQL Database is more expensive than geo-restore.

Practice this question →

175

MCQmedium

A company runs a critical web application on Azure VMs in the West US region. They need a disaster recovery solution that replicates the VMs to the East US region. The recovery point objective (RPO) must be 30 minutes, and the recovery time objective (RTO) must be 1 hour. The company also needs to perform quarterly disaster recovery drills without impacting the production environment. Additionally, after a failover, the solution must automatically update traffic management to route users to the East US region. Which combination of Azure services should they use?

A.Azure Site Recovery and Azure Traffic Manager

B.Azure Backup and Azure Traffic Manager

C.Azure Site Recovery and Azure Front Door

D.Azure Backup and Azure Front Door

AnswerA

Azure Site Recovery handles VM replication with the required RPO/RTO and supports non-disruptive test failovers. Azure Traffic Manager can automatically route user traffic to the secondary region after failover by using endpoint monitoring and failover priority.

Why this answer

Azure Site Recovery (ASR) orchestrates replication, failover, and failback of Azure VMs from West US to East US, meeting the 30-minute RPO and 1-hour RTO. Azure Traffic Manager automatically updates DNS-based traffic routing to the East US region after failover, ensuring users are redirected without manual intervention. This combination satisfies all requirements: DR replication, RPO/RTO, quarterly drills (via test failover), and automated traffic management.

Exam trap

The trap here is that candidates confuse Azure Front Door with Traffic Manager, assuming Front Door's global routing automatically handles failover, but Front Door requires manual DNS or backend pool updates, whereas Traffic Manager integrates natively with ASR recovery plans for automated DNS failover.

How to eliminate wrong answers

Option B is wrong because Azure Backup is designed for long-term data retention and point-in-time restore, not for full VM replication with orchestrated failover and RPO of 30 minutes; it cannot meet the RTO of 1 hour or support automated traffic rerouting after failover. Option C is wrong because Azure Front Door is a global load balancer and application delivery controller that uses anycast and HTTP-level routing, but it does not provide automatic traffic rerouting after a Site Recovery failover without manual DNS updates; Traffic Manager is the correct service for DNS-based failover routing. Option D is wrong because it combines Azure Backup (which lacks DR orchestration) with Azure Front Door (which does not automatically update routing after failover), failing both the replication and traffic management requirements.

Practice this question →

176

Matchingmedium

Match each Azure database service to its primary use case.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Globally distributed NoSQL database

Relational database as a service (PaaS)

Managed open-source relational database

In-memory data cache for low latency

SQL Server with near 100% compatibility

Why these pairings

These are common Azure data services for different workloads.

Practice this question →

177

MCQmedium

Adatum Corporation runs a customer-facing API on Azure API Management (Developer tier) in the East US region. The backend is an Azure Function app (Premium plan) also in East US. The data is stored in Azure Cosmos DB (Core SQL API) with a single write region in East US. The company requires: - RPO: 0 (zero data loss). - RTO: 1 minute for the API to be available after a region failure. - The solution must be fully automated. - Cost is not a primary concern. What DR strategy should you recommend?

A.Deploy the API Management, Functions, and Cosmos DB across two Availability Zones in East US. Use zone-redundant services. For Cosmos DB, use multi-region writes within the same region (not possible).

B.Deploy an active-active architecture in East US and West US. Deploy API Management in both regions and use Azure Front Door with health probes for automatic failover. Deploy Azure Functions in both regions (Premium plan supports multi-region). Configure Cosmos DB with multi-region writes (single write region with automatic failover) and strong consistency. All traffic is active-active, with automatic failover.

C.Deploy a passive standby in West US with a second API Management instance, a second Functions app, and a second Cosmos DB write region (multi-region writes). Use Azure Front Door with health probes to automatically route traffic. Manually failover Cosmos DB during disaster.

D.Deploy a passive standby in West US using Azure Site Recovery to replicate the Azure Functions and API Management. For Cosmos DB, enable a secondary read region and manual failover. Use Azure Traffic Manager to switch traffic during a disaster.

AnswerB

Active-active with automatic failover meets RPO=0 and RTO=1 minute.

Why this answer

Option D is correct because an active-active multi-region architecture with Cosmos DB multi-region writes (strong consistency in single write region with automatic failover) ensures zero data loss and automatic failover. API Management can be deployed in multiple regions with Azure Front Door for global load balancing and automatic failover. Azure Functions Premium plan supports multi-region deployment.

Option A is wrong because Azure Site Recovery has higher RTO. Option B is wrong because passive standby has higher RTO due to manual steps. Option C is wrong because Availability Zones do not protect against regional outage.

Practice this question →

178

MCQhard

A company runs a critical financial application on Azure Kubernetes Service (AKS) in a single region. The application uses Azure Cosmos DB for NoSQL with multiple write regions. You need to design a business continuity solution that meets an RPO of 0 seconds and an RTO of less than 5 seconds for a regional outage. The solution must be cost-optimized. What should you include in the design?

A.Deploy AKS clusters in two regions, use Azure Front Door to route traffic, and configure Azure Cosmos DB with multiple write regions and automatic failover.

B.Deploy AKS clusters in two regions, use Azure Traffic Manager with priority routing, and configure Azure Cosmos DB with a single write region and a readable secondary.

C.Deploy AKS clusters across availability zones in one region, use Azure Load Balancer, and configure Azure SQL Database with active geo-replication.

D.Deploy AKS clusters in two regions, use Azure Front Door, and configure Azure Cosmos DB with a single write region and manual failover.

AnswerA

Cosmos DB multi-region writes provide RPO=0; AKS with Front Door enables instant traffic switching.

Why this answer

Option A is correct because AKS can be deployed across Azure regions with Azure Front Door for global load balancing; Cosmos DB multi-region writes provide RPO=0 and automatic failover within seconds. Option B uses Azure Traffic Manager which does not provide instant failover. Option C uses Azure SQL Database which does not offer RPO=0 across regions.

Option D uses manual failover which increases RTO.

Practice this question →

179

MCQhard

A company runs a critical application on Azure VMs in a single region. The database tier uses SQL Server on Azure VMs. They need to implement disaster recovery to a secondary region with an RPO of 30 seconds and an RTO of 10 minutes for the database, and an RPO of 5 minutes and RTO of 1 hour for the VMs. The solution must minimize data loss and be cost-effective. Which combination should they use?

A.Azure Site Recovery for VMs and SQL Server Always On Availability Groups with synchronous commit

B.Azure Site Recovery for VMs and SQL Server log shipping

C.Azure Backup for VMs and SQL Server database mirroring

D.Azure Site Recovery for VMs and SQL Server Always On Availability Groups with asynchronous commit

AnswerD

Asynchronous commit meets RPO of 30 seconds, and ASR meets VM RPO/RTO requirements; this is cost-effective and recommended across regions.

Why this answer

Option D is correct because Azure Site Recovery (ASR) provides VM replication to a secondary region with an RPO of 5 minutes and RTO of 1 hour, meeting the VM requirements. SQL Server Always On Availability Groups with asynchronous commit can achieve an RPO of 30 seconds (or less) while minimizing cost by avoiding synchronous replication overhead, and it supports automatic failover for the database tier, meeting the 10-minute RTO.

Exam trap

The trap here is that candidates often choose synchronous commit (Option A) thinking it minimizes data loss, but they overlook the cost and latency constraints of cross-region synchronous replication, making asynchronous commit the practical choice for the given RPO and cost-effectiveness requirements.

How to eliminate wrong answers

Option A is wrong because SQL Server Always On Availability Groups with synchronous commit requires low-latency, high-bandwidth links between regions, which is not cost-effective and can impact performance; it also typically requires at least three replicas for automatic failover, increasing complexity and cost. Option B is wrong because SQL Server log shipping has a typical RPO of minutes to hours (not 30 seconds) and an RTO that can exceed 10 minutes due to manual failover and log restore steps. Option C is wrong because Azure Backup for VMs is a backup solution, not a disaster recovery replication tool, and cannot achieve an RPO of 5 minutes or RTO of 1 hour; SQL Server database mirroring (deprecated) does not support automatic failover to a secondary region and has higher latency.

Practice this question →

180

MCQeasy

Your company uses Azure Backup to protect on-premises file servers and Azure VMs. The compliance team requires that backup data be stored in a secondary region to protect against regional disasters. Which Azure Backup feature should you enable?

A.Enable geo-redundant storage (GRS) for the Recovery Services vault

B.Use Azure Site Recovery to replicate the backup data

C.Configure backup policies to back up directly to the secondary region

D.Use a Recovery Services vault in the secondary region

AnswerA

GRS replicates backup data to a paired region.

Why this answer

Option B is correct because Azure Backup allows configuring a Recovery Services vault with geo-redundant storage (GRS) to replicate backup data to a paired region. Option A is wrong because Recovery Services vault is the container, not the replication feature. Option C is wrong because Back up to a secondary region is not supported directly.

Option D is wrong because Azure Site Recovery is for replication, not backup.

Practice this question →

181

MCQhard

Contoso Ltd. runs a mission-critical application on Azure Virtual Machines in the East US region. The application uses Azure SQL Database (Business Critical tier) and stores files in Azure Blob Storage (hot tier). The business requires a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes for the application. For SQL Database, they need the ability to fail over to a secondary region with no data loss. For Blob Storage, they need to maintain read access to data even if the primary region fails. The solution must be cost-optimized and not exceed the RTO/RPO. Which combination of services should you recommend?

A.Configure Azure SQL Database failover groups with automatic failover, and use geo-redundant storage (GRS) for Blob Storage.

B.Deploy Azure Site Recovery for VMs, configure Azure SQL Database failover groups, and use geo-zone-redundant storage (GZRS) for Blob Storage.

C.Configure Azure SQL Database geo-restore for the database, and use zone-redundant storage (ZRS) for Blob Storage.

D.Configure Azure SQL Database active geo-replication with a secondary in a paired region, and use read-access geo-redundant storage (RA-GRS) for Blob Storage.

AnswerD

Active geo-replication provides synchronous replication for zero data loss, and RA-GRS allows read access during a regional outage, meeting RTO/RPO.

Why this answer

Option B is correct because Azure SQL Database with active geo-replication provides synchronous replication to a secondary region, achieving RPO of 0 (no data loss), and failover can be initiated within minutes, meeting RTO of 15 minutes. Azure Blob Storage with read-access geo-redundant storage (RA-GRS) allows read access to data in the secondary region even if the primary fails, and asynchronous replication meets RPO of 5 minutes. Option A is wrong because Azure Site Recovery for SQL Database is not necessary and adds cost/complexity; SQL Database has built-in geo-replication.

Option C is wrong because Azure SQL Database failover groups use asynchronous replication, which could lose data (RPO > 5 minutes) unless configured with premium tier, but still not zero data loss. Option D is wrong because Azure SQL Database with geo-restore has RTO of hours, not 15 minutes.

Practice this question →

182

MCQmedium

A company runs a SQL Server database on an Azure VM in West Europe. They need to back up the database daily and retain backups for 7 years for compliance. They also require the ability to restore the database to a secondary Azure region (North Europe) if the primary region fails. They want to minimize operational overhead and costs. Which Azure Backup configuration should they use?

A.A

B.B

C.C

D.D

AnswerA

Use Azure Backup to back up SQL Server to a Recovery Services vault in West Europe and enable cross-region restore to North Europe. This is the recommended approach for backup resilience across regions.

Why this answer

Option A is correct because Azure Backup's built-in cross-region restore (CRR) for Azure VMs allows you to restore SQL Server databases hosted on Azure VMs to a paired secondary region (North Europe) in the event of a disaster, while retaining backups for up to 10 years (covering the 7-year compliance requirement). This configuration minimizes operational overhead by using Azure Backup's native policy-based scheduling and storage management, and it is cost-effective as it uses geo-redundant storage (GRS) for the Recovery Services vault without needing a separate backup infrastructure.

Exam trap

The trap here is that candidates often confuse Azure Site Recovery (ASR) with Azure Backup, thinking ASR can handle long-term backup retention, when in fact ASR is for replication and failover, not for point-in-time restores with multi-year retention, and they may overlook the need to explicitly enable cross-region restore (CRR) on the Recovery Services vault to meet the secondary region recovery requirement.

How to eliminate wrong answers

Option B is wrong because it suggests using Azure Site Recovery (ASR) for database backup, but ASR is designed for replication and failover of entire VMs, not for point-in-time database restore with long-term retention; it also incurs higher costs for continuous replication and does not natively support 7-year backup retention. Option C is wrong because it proposes backing up the SQL Server database to Azure Blob Storage using manual scripts or third-party tools, which increases operational overhead and does not integrate with Azure Backup's native cross-region restore or long-term retention policies. Option D is wrong because it recommends using Azure Backup for SQL Server on Azure VM but without enabling cross-region restore (CRR), which means backups are stored only in the primary region (West Europe) and cannot be restored to North Europe if the primary region fails, failing the disaster recovery requirement.

Practice this question →

183

MCQeasy

A company runs a critical Azure SQL Database in the West US region. They need a disaster recovery solution that automatically fails over to a secondary region (East US) with a recovery point objective (RPO) of 5 seconds and a recovery time objective (RTO) of less than 1 hour. Additionally, they want to offload read-only workloads to the secondary database during normal operations. Which Azure SQL Database feature should they enable?

A.Active geo-replication with failover groups

B.Point-in-time restore

C.Long-term backup retention

D.Always On availability groups (self-managed)

AnswerA

Failover groups provide automatic failover to a readable secondary database. Active geo-replication synchronizes data with an RPO of 5 seconds and supports readable secondaries. The failover group ensures automatic failover with an RTO of typically less than 1 hour.

Why this answer

Active geo-replication with failover groups is the correct choice because it provides automatic, asynchronous replication of an Azure SQL Database to a secondary region (East US) with an RPO of up to 5 seconds and an RTO of less than 1 hour. Additionally, it supports readable secondary replicas, allowing read-only workloads to be offloaded to the secondary database during normal operations, meeting all stated requirements.

Exam trap

The trap here is that candidates often confuse active geo-replication with failover groups (which supports readable secondaries and automatic failover) with standard active geo-replication (which requires manual failover and does not provide a single endpoint), or they mistakenly think Always On availability groups applies to Azure SQL Database instead of SQL Server on VMs.

How to eliminate wrong answers

Option B is wrong because point-in-time restore (PITR) only recovers the database to a specific point in time within the same region (retention up to 35 days) and does not provide cross-region failover or a readable secondary for offloading read workloads. Option C is wrong because long-term backup retention (LTR) stores backups for up to 10 years for compliance, but it does not enable automatic failover to a secondary region or support readable secondaries for read offloading. Option D is wrong because Always On availability groups (self-managed) is a feature for SQL Server on Azure Virtual Machines, not for Azure SQL Database managed service, and it requires manual configuration and management, not automatic failover with the specified RPO/RTO.

Practice this question →

184

MCQmedium

A company runs a critical Azure SQL Database in a single region. They need to ensure availability if an entire Azure datacenter fails. They require automatic failover with zero data loss and an RTO of 30 seconds. They also want to use the secondary database for read-only query offloading during normal operations. Which Azure SQL Database feature should they enable?

A.Active geo-replication

B.Auto-failover groups with read-scale enabled

C.Zone-redundant database

D.Point-in-time restore

AnswerB

This feature uses synchronous replication (in the Business Critical or Premium tier) to ensure zero data loss, automatic failover within 30 seconds, and allows read-only queries on the secondary.

Why this answer

Auto-failover groups with read-scale enabled meet all requirements: they provide automatic failover across regions with zero data loss when configured with the 'graceful' data loss policy (ensuring all committed transactions are replicated), an RTO of 30 seconds or less, and the ability to offload read-only queries to the secondary replica via the read-scale listener endpoint. This feature uses a secondary readable replica in a paired region, supporting both high availability and read workload distribution.

Exam trap

The trap here is that candidates often confuse Active geo-replication with auto-failover groups, assuming both support automatic failover, but only auto-failover groups provide automatic failover and a read-scale listener for read-only offloading.

How to eliminate wrong answers

Option A is wrong because Active geo-replication supports manual failover only, not automatic failover, and it does not provide a built-in read-scale listener for read-only query offloading; it also cannot guarantee zero data loss with a 30-second RTO without additional configuration. Option C is wrong because Zone-redundant databases protect against a single zone failure within a region, not an entire datacenter failure across regions, and they do not provide a secondary readable replica for read-only offloading. Option D is wrong because Point-in-time restore is a backup and recovery feature for restoring to a specific time within the retention period, not a real-time high-availability or disaster recovery solution; it cannot achieve a 30-second RTO or zero data loss during a datacenter failure.

Practice this question →

185

MCQeasy

A company wants to protect Azure VMs from accidental deletion or corruption by retaining daily backups for 30 days, weekly backups for 12 weeks, monthly backups for 12 months, and yearly backups for 7 years. Which backup policy type should they use?

A.Azure Backup GFS policy

B.Daily backup policy with 30-day retention

C.Monthly backup policy with 12-month retention

D.Azure Backup Enhanced policy

AnswerA

GFS policy can retain daily, weekly, monthly, yearly backups with different durations.

Why this answer

Option B is correct because Azure Backup supports a Grandfather-Father-Son (GFS) backup policy that allows retention of daily, weekly, monthly, and yearly backups with different retention periods. Option A is wrong because a simple daily backup policy cannot specify multiple retention tiers. Option C is wrong because the Enhanced policy is for SQL Server, not general VM backup.

Option D is wrong because a monthly backup policy cannot include daily or weekly backups.

Practice this question →

186

MCQmedium

A company backs up their Azure VMs using Azure Backup. They need to meet compliance that requires backups to be stored in a separate geographic region. Additionally, they want to be able to restore the entire VM to that secondary region in case of a regional disaster. What should they configure?

A.Use a Recovery Services vault with Locally Redundant Storage (LRS) and enable cross-region restore

B.Use a Recovery Services vault with Geo-Redundant Storage (GRS) and enable cross-region restore

C.Use Azure Site Recovery to replicate the entire VM to the secondary region

D.Manually copy backup snapshots to a storage account in the secondary region

AnswerB

GRS replicates backups to a paired region, and enabling cross-region restore allows restoring VMs to that secondary region, meeting both requirements.

Why this answer

Option B is correct because Azure Backup with a Recovery Services vault using Geo-Redundant Storage (GRS) replicates backup data to a paired secondary region, meeting the compliance requirement for geographic separation. Enabling cross-region restore allows the entire VM to be restored in that secondary region during a regional disaster, as the backup data is already available there.

Exam trap

The trap here is that candidates often confuse Azure Site Recovery (continuous replication for DR) with Azure Backup (snapshot-based backup with cross-region restore), leading them to select Option C, which does not meet the backup compliance requirement for stored backups in a separate region.

How to eliminate wrong answers

Option A is wrong because Locally Redundant Storage (LRS) keeps data only within a single datacenter in the primary region, failing the compliance requirement for storage in a separate geographic region. Option C is wrong because Azure Site Recovery is a disaster recovery solution that replicates the VM for continuous replication and failover, not for backup storage or restore from backup snapshots; it addresses different RPO/RTO needs but does not meet the backup compliance requirement. Option D is wrong because manually copying backup snapshots to a secondary region is inefficient, error-prone, and does not leverage Azure Backup's built-in cross-region restore capability, which is designed for automated, compliant disaster recovery.

Practice this question →

187

Matchingmedium

Match each Azure security service to its purpose.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Unified security management and threat protection

Cloud-native SIEM and SOAR

Manage secrets, keys, and certificates

Protect against distributed denial-of-service attacks

Managed cloud network security service

Why these pairings

These are essential security services in Azure.

Practice this question →

188

MCQhard

Your company, Contoso Ltd., runs a critical line-of-business application on Azure Virtual Machines in the West Europe region. The application uses Azure SQL Database (Business Critical tier) for data storage. The compliance team requires a Recovery Point Objective (RPO) of 5 seconds and a Recovery Time Objective (RTO) of 10 seconds for the database tier. For the compute tier, the RPO is 1 minute and RTO is 5 minutes. The application must remain available during planned maintenance and regional outages. You have been asked to design the business continuity solution. You need to recommend the most cost-effective solution that meets all requirements. What should you recommend?

A.Configure active geo-replication for Azure SQL Database; deploy AKS in two regions with Azure Traffic Manager; use manual failover scripts.

B.Use Azure SQL Database backup with point-in-time restore for the database; deploy AKS in West Europe and use Azure Traffic Manager for failover to a secondary cluster in North Europe.

C.Set up auto-failover group for Azure SQL Database with a secondary in North Europe; deploy AKS in both regions with Azure Front Door for global load balancing.

D.Deploy SQL Server Always On availability groups on Azure VMs in two regions; use Azure Site Recovery for the VMs; use Azure Front Door for load balancing.

AnswerC

Auto-failover groups provide automatic failover within seconds; Azure Front Door enables fast failover for AKS with health probes.

Why this answer

Option C is correct because Auto-failover groups with active geo-replication provide synchronous replication (RPO=0) and automatic failover (RTO~10 seconds) for Azure SQL Database Business Critical tier. AKS with Azure Front Door provides fast failover for compute tier. Option A is wrong because Azure SQL Database backup restore takes too long.

Option B is wrong because Traffic Manager lacks health probe granularity and AKS failover is slower. Option D is wrong because SQL Server Always On requires additional licensing and management overhead.

Practice this question →

189

MCQhard

You are designing a disaster recovery plan for a critical application that runs on Azure VMs. The VMs are in a single region and are backed up daily. The RPO is 1 hour and the RTO is 4 hours. The current backup solution cannot meet the RPO. You need to recommend a solution that meets the requirements with minimal cost. What should you do?

A.Implement Azure Site Recovery with a replication policy of 30 minutes.

B.Configure SQL Server Always On Availability Groups across two Azure regions.

C.Increase the backup frequency to every 30 minutes.

D.Implement Azure Site Recovery with a replication policy of 15 minutes.

AnswerA

ASR provides near-synchronous replication and quick failover.

Why this answer

Option B (ASR with replication frequency of 30 minutes) meets RPO and RTO with lower cost than continuous replication. Option A (backup every 30 minutes) increases cost without meeting RTO. Option C (continuous replication) is more expensive.

Option D (always-on availability groups) requires additional licenses.

Practice this question →

190

MCQmedium

Your company runs a web application on Azure App Service (Standard tier) in a single region. You need to design a disaster recovery solution that can fail over to another region within 30 minutes. The application uses Azure SQL Database (General Purpose tier) and Azure Blob Storage. What should you implement?

A.Use Azure Traffic Manager with priority routing to a second App Service instance, use Azure SQL Database backup to a secondary region, and use Azure Storage zone-redundant storage (ZRS).

B.Configure App Service auto-scaling, use Azure SQL Database geo-replication with readable secondary, and use Azure Storage read-access geo-redundant storage (RA-GRS).

C.Configure App Service backup to a secondary region, use Azure SQL Database active geo-replication with auto-failover group, and use geo-redundant storage (GRS) for Blob Storage.

D.Configure App Service deployment slots, use Azure SQL Database geo-restore, and use Azure Storage locally-redundant storage (LRS).

AnswerC

App Service backup/restore can be automated; SQL auto-failover group provides RTO of ~1 min; GRS ensures blob data replicated asynchronously.

Why this answer

Option B is correct because App Service backup/restore to a secondary region, Azure SQL Database active geo-replication with failover group, and Azure Storage geo-redundant storage (GRS) together meet the RTO of 30 minutes and provide data protection. Option A uses geo-restore for SQL which has longer RPO. Option C uses read-only failover which may not allow writes.

Option D uses traffic manager but does not address database failover.

Practice this question →

191

Multi-Selectmedium

Which TWO of the following are requirements for using Azure Site Recovery to protect Azure VMs? (Choose two.)

Select 2 answers

A.VMs must use unmanaged disks

B.VMs must be using managed disks

C.VMs must be connected to a virtual network that has a VPN gateway to the target region

D.The source region must be a supported Azure region

E.VMs must be at least Standard_D2s_v3 size

AnswersB, D

Managed disks are required for Azure Site Recovery.

Why this answer

Options A and D are correct. VMs must be in a region that supports Azure Site Recovery (A). VMs must be using managed disks (D).

Option B is wrong because unmanaged disks are not supported. Option C is wrong because VMs can be any size, but there are some limitations. Option E is wrong because Site Recovery does not require a VPN connection for Azure-to-Azure replication; it uses the Azure backbone.

Practice this question →

192

MCQhard

Your company runs a stateless web application on Azure Kubernetes Service (AKS). You need to design a disaster recovery solution that ensures the application is available in another Azure region within 30 minutes of a regional failure. The solution must balance cost and complexity. What should you recommend?

A.Use Azure SQL Database active geo-replication for the application's database.

B.Use Azure Front Door to route traffic to a single AKS cluster with pods running in multiple regions.

C.Use Azure Traffic Manager to distribute traffic across two AKS clusters in different regions.

D.Deploy a single AKS cluster with nodes in multiple availability zones.

AnswerC

Traffic Manager with priority routing can automatically failover to the secondary region, meeting the RTO.

Why this answer

Deploying AKS clusters in two regions with Traffic Manager for global load balancing provides a cost-effective and relatively simple solution for stateless applications. Option A is incorrect because Azure Front Door is not the best fit for container workloads. Option C is incorrect because it lacks automated failover.

Option D is incorrect because active geo-replication is for databases.

Practice this question →

193

Multi-Selecteasy

Which TWO Azure services can be used to provide cross-region disaster recovery for Azure App Service web applications with a custom domain? (Select TWO.)

Select 2 answers

A.Azure DNS

B.Azure Front Door

C.Azure CDN

D.Azure Application Gateway

E.Azure Traffic Manager

AnswersB, E

Front Door provides global load balancing and automatic failover.

Why this answer

Options A and B are correct. Azure Traffic Manager can route traffic to a secondary region App Service in case of primary region failure. Azure Front Door provides global load balancing and failover.

Options C, D, and E are wrong: Azure Application Gateway is regional, Azure DNS does not provide traffic routing, and Azure CDN is for content caching, not failover.

Practice this question →

194

MCQmedium

A company runs a critical application on Azure VMs in a single region. The application writes data to Azure SQL Database (PaaS) and Azure Blob Storage. The company needs a disaster recovery plan with an RPO of less than 5 minutes for the database and less than 15 minutes for the blob storage, and an RTO of less than 1 hour for the entire solution. What should they recommend?

A.Use Azure Site Recovery for VMs, geo-replication for Azure SQL Database, and geo-redundant storage (GRS) for Blob Storage.

B.Use Azure Backup for VMs, geo-redundant storage for SQL Database backups, and geo-redundant storage for Blob Storage.

C.Use Azure Site Recovery for VMs, active geo-replication for Azure SQL Database, and read-access geo-redundant storage (RA-GRS) for Blob Storage.

D.Use Azure Front Door with multi-region deployment of VMs and Azure Cosmos DB for the database.

AnswerC

ASR replicates VMs with minutes RPO. Active geo-replication for Azure SQL Database provides a readable secondary with RPO seconds. RA-GRS provides a readable copy in the secondary region with ~15 minute RPO, meeting the blob requirement.

Why this answer

Option C is correct because Azure Site Recovery provides the VM replication needed to meet the RTO of under 1 hour, active geo-replication for Azure SQL Database offers a configurable RPO of as low as 5 seconds (well under the 5-minute requirement), and RA-GRS for Blob Storage provides read-access to a secondary region with an RPO typically under 15 minutes, enabling fast failover and read access during a disaster.

Exam trap

The trap here is that candidates often confuse geo-redundant storage (GRS) with read-access geo-redundant storage (RA-GRS), not realizing that GRS requires a storage account failover to access the secondary region, which can take up to an hour and thus fails the RTO requirement.

How to eliminate wrong answers

Option A is wrong because geo-redundant storage (GRS) for Blob Storage does not provide read access to the secondary region during a disaster; you must initiate a failover to read data, which can exceed the RTO of 1 hour. Option B is wrong because Azure Backup for VMs is a backup solution, not a replication solution, and cannot achieve an RTO of under 1 hour for full VM failover; additionally, geo-redundant storage for SQL Database backups does not provide the sub-5-minute RPO required, as backups are typically taken every 5–10 minutes. Option D is wrong because Azure Front Door with multi-region VMs and Cosmos DB does not address the existing Azure SQL Database and Blob Storage requirements; it changes the architecture entirely and does not meet the stated RPO/RTO for the current services.

Practice this question →

195

MCQmedium

Your company has a critical application that uses Azure Kubernetes Service (AKS) in a single region. You need to design a disaster recovery solution that can automatically fail over to a secondary region in the event of a regional outage. The application data is stored in Azure Cosmos DB. What should you do?

A.Use Azure Front Door to route traffic to the primary AKS cluster and enable Cosmos DB automatic failover.

B.Use Azure Backup for AKS with cross-region restore and Cosmos DB geo-redundancy.

C.Replicate the AKS cluster to another region using Azure Site Recovery.

D.Deploy a secondary AKS cluster in another region, use Azure Traffic Manager for global load balancing, and enable Cosmos DB multi-region writes.

AnswerD

Traffic Manager and multi-region AKS clusters provide DR.

Why this answer

Option A is correct because AKS can be deployed in multiple regions, and Azure Traffic Manager can direct traffic to the secondary region. Cosmos DB multi-region writes ensure data availability. Option B is wrong because Azure Front Door does not provide AKS failover capability.

Option C is wrong because Azure Site Recovery does not support AKS. Option D is wrong because Azure Backup does not provide failover.

Practice this question →

196

MCQhard

A business-critical App Service application must survive a full regional outage. The recovery design should fail over automatically based on endpoint health and avoid DNS-cache delay where possible. Which service should front the regional deployments?

A.Azure Load Balancer

B.Azure Application Security Groups

C.Azure Front Door

D.Azure Traffic Manager only

AnswerC

Azure Front Door provides global HTTP/S load balancing, health probes, and fast failover at the edge.

Why this answer

Azure Front Door is the correct choice because it provides global HTTP/HTTPS load balancing with automatic failover across regions based on real-time endpoint health probes. It uses Anycast routing to direct traffic to the nearest healthy region, which avoids DNS-cache delay inherent in DNS-based solutions like Traffic Manager. This ensures sub-second failover and meets the requirement for a business-critical app that must survive a full regional outage.

Exam trap

The trap here is that candidates confuse Azure Traffic Manager's DNS-based global routing with Azure Front Door's Anycast-based global routing, overlooking the critical DNS-cache delay that Traffic Manager introduces.

How to eliminate wrong answers

Option A is wrong because Azure Load Balancer operates at Layer 4 and is regional, not global; it cannot fail over traffic across regions in a full regional outage. Option B is wrong because Azure Application Security Groups are a network security feature for grouping VMs and applying security rules, not a traffic routing or failover service. Option D is wrong because Azure Traffic Manager is DNS-based and relies on client DNS caching, which can cause delays of minutes during failover, violating the requirement to avoid DNS-cache delay.

Practice this question →

197

MCQhard

A multinational company runs a mission-critical application on Azure VMs in the West US region. The application uses Azure SQL Database (Business Critical tier) and Azure Cache for Redis. The company needs to ensure the application can fail over to a secondary region within 5 minutes during a regional outage. The design must minimize data loss. Which solution should you recommend?

A.Deploy VMs across Azure availability zones in West US, use Azure SQL Database geo-restore to East US, and deploy a second Azure Cache for Redis instance in East US.

B.Deploy VMs in an availability set in West US, use Azure Site Recovery to replicate to East US, and configure Azure SQL Database failover group with manual failover.

C.Deploy VMs in an Azure Site Recovery recovery plan to East US, use Azure SQL Database active geo-replication with auto-failover group, and deploy Azure Cache for Redis Standard tier in East US.

D.Deploy VMs in an Azure Site Recovery recovery plan to East US, use Azure SQL Database active geo-replication with auto-failover group, and use Azure Cache for Redis with geo-replication enabled.

AnswerD

Active geo-replication provides RPO ≤ 5 sec, auto-failover RTO ≤ 1 min; cache geo-replication ensures cache data survives region failover.

Why this answer

Option C is correct because it uses Azure SQL Database active geo-replication with a failover group for automatic failover (RPO ≤ 5 seconds, RTO ≤ 1 minute) and Azure Cache for Redis with geo-replication for cross-region replication. Option A has longer RTO for SQL failover. Option B uses Azure SQL Database with geo-restore which has RPO of 1 hour.

Option D uses cache replication that is not available in Standard tier.

Practice this question →

198

MCQeasy

You are a Solutions Architect for an e-commerce company that runs its online store on Azure. The application consists of: - Azure App Service (Windows) hosting the web frontend - Azure SQL Database (General Purpose, serverless) for product catalog and orders - Azure Cache for Redis for session state - Azure Blob Storage for product images The application is deployed in the East US region. The company wants to implement a disaster recovery (DR) plan that can fail over to a secondary region (West US) with minimal data loss. The requirements are: - RPO: 5 minutes for the database - RTO: 30 minutes for the entire application - The solution must be cost-effective and not require manual intervention during failover. Which of the following is the BEST course of action to meet these requirements?

A.Use Azure Backup for the SQL database with 5-minute backup frequency, deploy App Service in West US with staging slots, and use Azure Traffic Manager with priority routing.

B.Configure Azure SQL Database geo-replication with readable secondary, deploy App Service in West US with deployment slots, and use Azure Front Door with health probes. Cache for Redis is not critical and can be rebuilt.

C.Configure Azure SQL Database active geo-replication with auto-failover group, deploy App Service in West US with a separate App Service plan, enable geo-replication for Cache for Redis, and use RA-GRS for Blob Storage. Use Azure Traffic Manager with priority routing for the web app.

D.Deploy the entire application in an active-active configuration using Azure Front Door, with Azure SQL Database using failover groups and manual failover. Use Azure Backup for the database with 1-hour backup frequency.

AnswerC

Auto-failover group meets RPO and automates failover; Traffic Manager routes traffic; Redis geo-replication and RA-GRS ensure low data loss.

Why this answer

Option C is correct. Azure SQL Database active geo-replication with auto-failover groups achieves RPO of 5 seconds and RTO of 1 hour (with auto-failover, typically <1 hour). App Service can be deployed in paired region with traffic manager or Front Door for quick failover.

Blob Storage can use geo-redundant storage (GRS) with read access (RA-GRS) for fast failover. Redis can be configured with geo-replication. Option A is wrong because Azure Backup does not provide 5-minute RPO.

Option B is wrong because read-only replicas are not for failover. Option D is wrong because manual steps increase RTO beyond 30 minutes, and Azure Backup is not suitable for the required RPO.

Practice this question →

199

MCQmedium

A company runs an application on Azure VMs that must be backed up according to regulatory compliance: daily backups retained for 30 days, weekly backups retained for 12 months, and yearly backups retained for 7 years. The backups must be stored in a secondary region for disaster recovery. They want to use Azure Backup for VMs. Which backup policy and storage configuration should they implement?

A.Configure a backup policy in Azure Backup for VMs with daily, weekly, and yearly retention rules, and enable cross-region restore by using a Recovery Services Vault with geo-redundant storage.

B.Enable backup with Azure Backup using the default policy and select Geo-Redundant Storage (GRS) for the Recovery Services Vault.

C.Use Azure Site Recovery to replicate VMs to the secondary region and configure retention policies in the replication settings.

D.Perform file-level backups using Azure Backup and store them in a separate storage account with read-access geo-redundant storage (RA-GRS).

AnswerA

Azure Backup policies can specify different retention durations for daily, weekly, and yearly backups. Cross-region restore is enabled by default with geo-redundant storage, allowing recovery in a secondary region.

Why this answer

Option A is correct because Azure Backup for VMs allows you to create a custom backup policy with daily, weekly, and yearly retention points, meeting the regulatory requirements. By enabling cross-region restore (CRR) on a Recovery Services Vault configured with geo-redundant storage (GRS), backups are automatically replicated to a paired secondary region, providing disaster recovery without additional infrastructure.

Exam trap

The trap here is that candidates often confuse Azure Site Recovery (disaster recovery) with Azure Backup (long-term retention), or assume the default policy can be customized to include yearly retention without realizing it must be explicitly configured.

How to eliminate wrong answers

Option B is wrong because the default backup policy in Azure Backup does not include yearly retention rules, so it cannot meet the 7-year yearly retention requirement. Option C is wrong because Azure Site Recovery is designed for replication and failover, not for long-term backup retention; it does not support granular retention policies like daily, weekly, and yearly backups. Option D is wrong because file-level backups do not capture the full VM state (including OS and application consistency), and RA-GRS storage alone does not provide the integrated backup policy with retention rules required for compliance.

Practice this question →

200

MCQhard

Contoso is a global e-commerce company that runs its platform on Azure Kubernetes Service (AKS) with Istio service mesh. The application uses Azure Cosmos DB (API for MongoDB) with multi-region writes enabled. The platform also uses Azure Cache for Redis Enterprise for session caching. The business requires a Recovery Time Objective (RTO) of 30 seconds and a Recovery Point Objective (RPO) of 0 for all tiers. You need to design a disaster recovery solution that meets these requirements with high availability. What should you recommend?

A.Deploy AKS in two regions with Azure Traffic Manager. Use Azure Cosmos DB with multi-region writes. Use Azure Cache for Redis Enterprise with active geo-replication.

B.Deploy AKS in two regions with Azure Front Door. Use Azure Cosmos DB with a single write region and auto-failover. Use Azure Cache for Redis Standard with geo-replication.

C.Deploy AKS in two regions with Azure Front Door. Use Azure Cosmos DB with multi-region writes. Use Azure Cache for Redis Enterprise with active geo-replication.

D.Use Azure SQL Database with auto-failover groups for the database tier. Deploy AKS in two regions with Azure Front Door. Use Azure Cache for Redis Enterprise with active geo-replication.

AnswerC

All tiers support multi-region writes with zero data loss; Azure Front Door provides automatic failover within seconds.

Why this answer

Option D is correct because Azure Cosmos DB multi-region writes provides zero data loss; Azure Front Door provides fast failover for AKS; Azure Cache for Redis Enterprise active geo-replication supports multi-region writes with zero data loss. Option A is wrong because Cosmos DB single-region writes cannot achieve RPO=0 during a regional outage. Option B is wrong because Azure Traffic Manager is DNS-based and slower.

Option C is wrong because Azure SQL Database does not support multi-region writes with RPO=0.

Practice this question →

201

MCQhard

A company runs a mission-critical SQL Server database on an Azure virtual machine using SQL Server Standard Edition. They need a disaster recovery solution that replicates the database to a secondary Azure region with a recovery point objective (RPO) of 15 minutes and a recovery time objective (RTO) of 1 hour. The solution must support non-disruptive disaster recovery drills. The company cannot modify the SQL Server configuration or use Always On features due to licensing constraints. Which Azure service should they use?

A.Azure Site Recovery

B.SQL Server log shipping to a VM in the secondary region

C.Azure Backup with cross-region restore

D.Azure SQL Database geo-replication

AnswerA

Site Recovery replicates the VM and can create consistent recovery points every 15 minutes. It supports test failovers that do not impact production, fulfilling the DR drill requirement.

Why this answer

Azure Site Recovery (ASR) replicates the entire VM (including the SQL Server database) to a secondary Azure region, meeting the RPO of 15 minutes and RTO of 1 hour. It supports non-disruptive disaster recovery drills by allowing test failovers in an isolated network without affecting the production environment. ASR does not require any changes to SQL Server configuration or licensing, as it operates at the hypervisor level using continuous replication.

Exam trap

The trap here is that candidates often choose Azure Backup (Option C) thinking it provides cross-region restore with low RPO, but they overlook that Backup's cross-region restore is designed for long-term retention and compliance, not for sub-hour RPOs, and it does not support non-disruptive drills.

How to eliminate wrong answers

Option B is wrong because SQL Server log shipping requires modifying the SQL Server configuration (setting up backup, copy, and restore jobs) and uses Always On features that are not available in Standard Edition without additional licensing; it also does not support non-disruptive drills without breaking the log chain. Option C is wrong because Azure Backup with cross-region restore provides only point-in-time snapshots with a typical RPO of 24 hours (or longer for cross-region), far exceeding the 15-minute requirement, and does not support non-disruptive drills. Option D is wrong because Azure SQL Database geo-replication is a PaaS feature that cannot be used with a SQL Server running on an Azure VM (IaaS); it requires migrating to Azure SQL Database, which is not the scenario described.

Practice this question →

← PreviousPage 3 of 3 · 201 questions total

Ready to test yourself?

Try a timed practice session using only Business Continuity Solutions questions.

Start 20-question session