Knowledge + Practice

CCNA Ha Dr Environment Questions

66 questions · Ha Dr Environment topic · All types, answers revealed

Practice these questions Exam hub All questions

1

Multi-Selecteasy

Which TWO disaster recovery options are available for Azure SQL Database? (Choose two.)

Select 2 answers

A.Database mirroring.

B.Auto-failover groups.

C.Always On availability groups.

D.Log shipping.

E.Active geo-replication.

AnswersB, E

Auto-failover groups provide automated geo-replication across Azure regions, enabling a secondary server to take over if the primary fails. This satisfies the disaster recovery requirement by delivering cross-region failover for Azure SQL Database, including read-write listener endpoints that redirect connections without manual intervention.

Why this answer

Active geo-replication and auto-failover groups are the two primary disaster recovery options for Azure SQL Database. Active geo-replication provides asynchronous replication of a database to a secondary region, while auto-failover groups extend this by allowing failover of multiple databases and providing read-only endpoints. Options A (database mirroring) and D (log shipping) are not supported for Azure SQL Database.

Option C (Always On availability groups) is a feature for SQL Server on Azure VMs, not for Azure SQL Database.

Practice this question →

2

MCQeasy

Your company wants to ensure business continuity for an Azure SQL Database that is used by a critical application. The database must remain available in the event of a single availability zone failure within a region. Which configuration should you use?

A.Configure zone-redundant availability for the database

B.Use active geo-replication to a different region

C.Deploy the database with locally redundant storage

D.Configure read scale-out with a secondary replica

AnswerA

Zone-redundant configuration replicates the database across multiple availability zones within the region, so a single zone failure leaves a replica serving traffic. This directly satisfies the stem's requirement for continuity during one availability zone outage.

Why this answer

Zone-redundant availability for Azure SQL Database replicates the database across multiple availability zones within a region, providing high availability if one zone fails. This ensures the database remains available during a single zone outage, meeting the business continuity requirement.

Exam trap

The trap is confusing zone redundancy with geo-replication; candidates might pick geo-replication for zone failures, but it is designed for regional disasters.

How to eliminate wrong answers

Option B is wrong because active geo-replication is for cross-region disaster recovery, not for zone-level failures within a region. Option C is wrong because locally redundant storage replicates data within a single zone, so a zone failure would cause an outage. Option D is wrong because read scale-out provides a read-only replica but does not guarantee high availability in case of a zone failure; it is for offloading read workloads.

Practice this question →

3

MCQhard

You have a SQL Server on Azure VM running a mission-critical database. The VM is configured with Azure Site Recovery (ASR) for disaster recovery. During a disaster recovery drill, you notice that the recovered database is not consistent. What is the most likely cause?

A.The secondary region is not in the same geo as the primary.

B.Application-consistent snapshots are not enabled in the ASR replication policy.

C.The backup retention period is too short.

D.The database is not part of an Always On availability group.

AnswerB

ASR's default crash-consistent snapshots capture the disk state without flushing in-memory writes or quiescing the database, so a recovered SQL Server may need crash recovery and appear inconsistent. Enabling application-consistent snapshots, via VSS, produces a transactionally consistent recovery point.

Why this answer

Azure Site Recovery replicates VM disks, and by default it takes crash-consistent snapshots, which capture the disk state as if the power were cut — the database may have in-flight transactions and be inconsistent on recovery. Enabling application-consistent snapshots in the replication policy triggers VSS (Volume Shadow Copy Service) to quiesce the database and flush transactions before snapshotting, ensuring a consistent recovery point.

Exam trap

The trap is assuming ASR replication is automatically database-consistent; exams test whether candidates know that crash-consistent is the default and application-consistent snapshots must be explicitly enabled.

How to eliminate wrong answers

Option A is wrong because ASR requires the secondary region to be in the same geography (geo) for supported replication; cross-geo replication is not the cause of inconsistency and is generally not allowed for ASR. Option C is wrong because backup retention period relates to backup history, not to the consistency of ASR-replicated recovery points. Option D is wrong because Always On availability groups are a separate high-availability/DR mechanism; ASR can replicate a standalone SQL Server VM, and the absence of an AG does not by itself cause inconsistency — the snapshot consistency setting does.

Practice this question →

4

MCQeasy

You administer an Azure SQL Database named SalesDB in the East US region. The business requires that SalesDB remains available even if an entire Azure availability zone within East US fails. You need to configure the database so that replicas are automatically distributed across multiple availability zones with no application connection string changes. What should you do?

A.Enable zone redundancy for the database.

B.Configure an auto-failover group to a secondary region.

C.Enable read-scale out and point the application to the read-only replica.

D.Create an active geo-replication secondary in the same region.

AnswerA

Zone redundancy is the Azure SQL Database feature that automatically places compute and storage replicas across multiple availability zones inside the region. Enabling it requires no connection string changes because the same logical server endpoint is used. It protects against a single availability zone outage, which is exactly the requirement here.

Why this answer

Zone redundancy in Azure SQL Database spreads replicas across availability zones within a region, providing automatic failover if a zone becomes unavailable. It requires no application changes because the same server hostname is used. Auto-failover groups and active geo-replication are cross-region features, and read-scale out is for read offloading, so none of those meet the intra-region zone failure requirement.

Exam trap

The trap here is confusing intra-region zone redundancy with cross-region features such as auto-failover groups or active geo-replication.

Practice this question →

5

MCQmedium

You are a database administrator for a healthcare company that uses Azure SQL Database for its electronic health records (EHR) system. The database is in the West Europe region using the General Purpose service tier. The company is expanding to the United States and wants to set up disaster recovery with the secondary in East US. The requirements are: RPO of 5 minutes and RTO of 1 hour. The application should automatically failover without manual intervention. Additionally, you must ensure that the secondary database is not used for read traffic to avoid any performance impact on the primary. What should you configure?

A.Configure active geo-replication to a secondary database in East US and set up a custom monitoring script to trigger failover.

B.Create a failover group with a readable secondary in East US and enable auto-failover.

C.Create a failover group with a non-readable secondary in East US and enable auto-failover.

D.Deploy a zone-redundant General Purpose database in West Europe and use geo-restore to East US.

AnswerC

A failover group with a non-readable secondary in East US satisfies every constraint: geo-replication delivers an RPO well under 5 minutes, automatic failover meets the 1-hour RTO without manual intervention, and setting the secondary to non-readable prevents any read traffic from reaching it, protecting primary performance.

Why this answer

A failover group with auto-failover and a non-readable secondary meets all requirements: RPO of 5 minutes can be achieved with async replication, RTO of 1 hour with automatic failover, and no read traffic. Option A is wrong because active geo-replication alone does not provide automatic failover. Option B is wrong because a readable secondary would be used for read traffic.

Option D is wrong because zone-redundancy doesn't protect regionally.

Practice this question →

6

MCQeasy

You have an Azure SQL Database named InventoryDB in the North Europe region. The database is in the General Purpose service tier. The business requires that InventoryDB remains available if a single availability zone within the North Europe region fails. You need to configure the database to meet this requirement with minimal downtime. What should you do?

A.Change the service tier to Business Critical.

B.Configure active geo-replication with a secondary database in the same region.

C.Configure an auto-failover group with a secondary server in West Europe.

D.Enable zone redundancy for InventoryDB.

AnswerD

Zone redundancy in the General Purpose service tier replicates the database across multiple availability zones within the same region. If one zone fails, the database remains available with automatic failover to another zone. This meets the requirement for high availability within a region with minimal downtime and no application changes.

Why this answer

Zone redundancy is the feature designed to protect against availability zone failures within a region. It replicates databases synchronously across zones, ensuring automatic failover and minimal downtime. Other options either address regional disasters, require manual intervention, or do not provide zone-level protection.

Exam trap

The trap here is confusing zone redundancy with geo-replication or assuming that changing the service tier automatically enables zone redundancy.

Practice this question →

7

MCQmedium

You administer an Azure SQL Database named SalesDB that uses the Business Critical service tier. The database is deployed in the West Europe region, which supports availability zones. The application requires that the database remains available even if an entire availability zone fails. You need to configure the database to meet this requirement with minimal administrative effort. What should you do?

A.Configure active geo-replication to a secondary region.

B.Enable zone redundancy on the database.

C.Create a failover group with an auto-failover policy.

D.Deploy the database to a SQL Managed Instance with zone redundancy.

AnswerB

Zone redundancy for Business Critical Azure SQL Database automatically distributes replicas across multiple availability zones, so if one zone fails, the database remains online with no manual intervention. It requires no application changes and is enabled with a single setting, meeting the minimal-effort requirement. This is the correct approach for zone-level high availability.

Why this answer

Zone redundancy in the Business Critical service tier spreads replicas across availability zones, ensuring automatic failover if a zone becomes unavailable. It is a simple configuration toggle that requires no application changes, providing high availability at the zone level. Other options address regional disasters or involve migration, which are not minimal-effort solutions for zone-level resilience.

Exam trap

The trap here is confusing zone-level high availability with regional disaster recovery, leading to selection of geo-replication or failover groups instead of zone redundancy.

Practice this question →

8

MCQmedium

You administer an Azure SQL Database named SalesDB that uses the Business Critical service tier. The database is deployed in the West US 2 region, which does not support availability zones. The application requires a recovery time objective (RTO) of less than 30 seconds for a zonal failure within the region. You need to meet the RTO requirement with minimal administrative effort. What should you do?

A.Enable zone redundancy on the database.

B.Create a read-scale out replica in the same region.

C.Configure an auto-failover group with a secondary in East US 2.

D.Migrate the database to a region that supports availability zones and enable zone redundancy.

AnswerD

To achieve an RTO of less than 30 seconds for a zonal failure, zone redundancy is required. Since West US 2 does not support availability zones, migrating to a supported region and enabling zone redundancy is the only way to meet the requirement with minimal administrative effort. This provides automatic failover within the region.

Why this answer

Zone redundancy in the Business Critical tier provides automatic failover across availability zones with an RTO of less than 30 seconds. Because West US 2 lacks availability zone support, the database must be moved to a region that supports them. Configuring cross-region replication or read replicas does not address zonal failures with the required RTO.

Migrating and enabling zone redundancy is the correct solution.

Exam trap

The trap here is assuming that any Business Critical database can enable zone redundancy regardless of the region's support for availability zones.

Practice this question →

9

MCQhard

You are troubleshooting a failover group for Azure SQL Database. The automatic failover is not triggering as expected during a regional outage. You verify that the grace period for data loss is set to 3600 seconds. The outage lasts 30 minutes. What is the most likely reason the automatic failover did not occur?

A.The failover policy is set to manual.

B.The outage duration is less than the grace period for data loss.

C.The grace period for data loss is too short.

D.The secondary region is also experiencing an outage.

AnswerB

Automatic failover only triggers once the grace period elapses, and 3600 seconds equals 60 minutes. The 30-minute outage falls short of that threshold, so Azure SQL Database withholds failover to avoid potential data loss, satisfying the stem's grace-period constraint.

Why this answer

The grace period for data loss (also called the 'grace period' or 'data loss grace period') is the maximum time the failover group waits before forcing a failover when the primary region is unavailable. If the outage duration is shorter than this grace period, Azure SQL Database will not trigger automatic failover because it still hopes to recover the primary without data loss. Here, the grace period is 3600 seconds (60 minutes) and the outage lasted only 30 minutes, so the condition for automatic failover was not met.

Thus, the most likely reason is that the outage duration is less than the grace period.

Exam trap

DP-300 often tests the misconception that a longer grace period causes faster failover, when in fact a longer grace period delays failover until the specified time has elapsed, potentially exceeding the outage duration and preventing automatic failover.

How to eliminate wrong answers

Option A is wrong because if the failover policy were set to manual, automatic failover would never occur regardless of outage duration, but the question states that automatic failover is not triggering as expected, implying it is configured for automatic. Option C is wrong because a grace period of 3600 seconds is not too short; in fact, it is longer than the outage, which is why failover did not occur. Option D is wrong because if the secondary region were also experiencing an outage, that would be a valid reason, but the scenario does not indicate that; the outage is described as a regional outage affecting the primary, and the grace period is the key factor.

Practice this question →

10

MCQmedium

You have an Azure SQL Database that uses the Hyperscale service tier. The database is 4 TB and has a readable secondary in a different region. You need to ensure that if the primary region fails, the secondary can be promoted to primary with minimal data loss and without reconfiguring the application connection string. What should you implement?

A.Create a geo-secondary using the Azure CLI and configure the application to use the secondary's server name.

B.Configure active geo-replication and update the application connection string to point to the secondary after failover.

C.Enable zone redundancy on the primary database and rely on automatic failover within the region.

D.Configure an auto-failover group that includes the primary and secondary databases.

AnswerD

Auto-failover groups support Hyperscale service tier databases and provide a read-write listener endpoint that remains constant across failovers. This allows the application to continue using the same connection string after the secondary is promoted. The failover group also manages the replication and supports automatic failover, minimizing data loss and administrative effort. This is the correct solution for the scenario.

Why this answer

Auto-failover groups are the recommended solution for cross-region disaster recovery when you need a stable listener endpoint that does not change after failover. They support Hyperscale tier databases and provide automatic failover with minimal data loss. Active geo-replication requires manual connection string updates, and zone redundancy only provides local high availability.

Therefore, the failover group is the only option that meets all requirements.

Exam trap

The trap here is assuming that active geo-replication provides a stable endpoint; it does not, and the application would need to be reconfigured after failover.

Practice this question →

11

MCQeasy

You have an Azure SQL Database that uses the General Purpose service tier. The database is 200 GB and is used by a web application. The application experiences occasional unplanned failovers due to hardware failures in the primary region. You need to ensure that the database remains available during a single datacenter failure within the region without any application changes. What should you do?

A.Change the service tier to Business Critical.

B.Configure active geo-replication with a secondary database in the same region.

C.Enable zone redundancy for the database.

D.Configure an auto-failover group with a secondary database in a different region.

AnswerC

Zone redundancy for Azure SQL Database General Purpose tier spreads the storage and compute replicas across multiple availability zones within the same region. This provides high availability if a single datacenter (availability zone) fails, and the failover is automatic without application changes. It meets the requirement of surviving a datacenter failure within the region while keeping the application connection string unchanged.

Why this answer

Zone redundancy is the feature that provides high availability within a single region by spreading replicas across availability zones. It is available for both General Purpose and Business Critical service tiers. Enabling zone redundancy on the existing General Purpose database meets the requirement of surviving a datacenter failure without application changes and is cost-effective.

Auto-failover groups and active geo-replication are for cross-region disaster recovery, and Business Critical is an unnecessary upgrade.

Exam trap

The trap here is confusing zone redundancy (local high availability) with geo-replication or failover groups (cross-region disaster recovery).

Practice this question →

12

MCQmedium

You manage an Azure SQL Database named SalesDB in the East US region. The database is in the General Purpose service tier and is business-critical. The application that uses SalesDB requires a recovery point objective (RPO) of 5 minutes and a recovery time objective (RTO) of 1 hour in the event of a regional outage. You need to configure a disaster recovery solution that meets these requirements with minimal administrative effort. What should you implement?

A.Create an auto-failover group that includes SalesDB and a secondary server in West US.

B.Enable zone redundancy for SalesDB and rely on the built-in high availability.

C.Configure active geo-replication with a readable secondary in West US.

D.Configure a long-term retention policy and restore the database to a new server in West US during an outage.

AnswerA

Auto-failover groups provide automatic failover for one or more databases, with an RPO of about 5 seconds and an RTO of about 1 hour. They also allow read-write and read-only listener endpoints, simplifying connection management. This meets the RPO and RTO requirements with minimal administrative effort because failover is automatic and configured at the group level.

Why this answer

An auto-failover group is the correct solution because it provides automatic failover for a group of databases, achieving an RPO of about 5 seconds and an RTO of about 1 hour. It also offers listener endpoints that remain constant, reducing application changes. Active geo-replication lacks automatic failover, zone redundancy only covers single-zone failures, and long-term retention restores are too slow and have a higher RPO.

Exam trap

The trap here is assuming that active geo-replication provides automatic failover; it does not, and failover must be initiated manually, which can violate the RTO.

Practice this question →

13

MCQmedium

You have an Azure SQL Managed Instance in the East US region. To meet a 1-hour RPO and 2-hour RTO, you configure a failover group with a secondary in West US using automatic failover. During a test, you notice that the RTO is consistently 10 minutes longer than required. What is the most likely cause?

A.The failover group uses Microsoft Entra ID authentication, which adds latency.

B.The secondary database is configured with asynchronous commit, causing delay.

C.The failover group has a grace period of 20 minutes configured.

D.The secondary database is not seeded and needs to be restored.

AnswerC

Correct: The grace period adds to RTO.

Why this answer

The failover group's automatic failover includes a grace period (default 20 minutes) that delays the actual failover after detecting unavailability. This grace period directly contributes to the RTO, explaining the 10-minute exceedance of the required 2-hour RTO. Option A is incorrect because Microsoft Entra ID authentication does not add noticeable latency to the failover process; authentication occurs independently of replication and failover.

Option B is incorrect because asynchronous commit is the standard replication mode for failover groups and does not inherently cause additional delay beyond the grace period; the issue is not the commit mode but the waiting period before failover. Option D is incorrect because the secondary database is automatically seeded when the failover group is created; no manual restore is needed.

Practice this question →

14

MCQeasy

Your company has an Azure SQL Database that uses the Business Critical service tier with three replicas. You need to ensure that during a regional outage, the database can be failed over to a secondary region with minimal data loss. What should you configure?

A.Configure zone-redundant replicas in the same region.

B.Create an auto-failover group with a secondary server in a different region.

C.Enable read scale-out on the database.

D.Use geo-redundant backup storage and perform geo-restore.

AnswerB

Auto-failover groups replicate the Business Critical database to a secondary server in another region and permit promotion during a regional outage. This satisfies the minimal-data-loss constraint, since replication is continuous and failover preserves committed transactions.

Why this answer

An auto-failover group in Azure SQL Database lets you group databases on a primary server and configure a secondary server in a different Azure region, with automatic or manual failover and read-write listener endpoints. It provides cross-region disaster recovery with minimal data loss (RPO typically seconds) and is the correct configuration for regional outage failover.

Exam trap

DP-300 often tests the difference between zone redundancy (same-region HA), read scale-out (performance), and auto-failover groups (cross-region DR), so candidates who see 'replicas' and pick zone-redundant replicas miss that the question specifies a regional outage.

How to eliminate wrong answers

Option A is wrong because zone-redundant replicas protect against a single datacentre/zone failure within the same region, not a full regional outage — if the region goes down, zone redundancy does not help. Option C is wrong because read scale-out uses the built-in read-only replicas (including in Business Critical) to offload read workloads; it is a performance feature, not a cross-region DR mechanism. Option D is wrong because geo-redundant backup storage plus geo-restore is a backup-based recovery method with much higher RPO (up to hours) and RTO (hours), not a minimal-data-loss failover solution.

Practice this question →

15

Multi-Selectmedium

You are planning a disaster recovery strategy for an Azure SQL Database that is part of a failover group. The application requires that after a failover, the database is accessible with minimal downtime and without data loss. Which THREE components are essential for this configuration? (Select three.)

Select 3 answers

A.Geo-redundant backup storage

B.Secondary database in a paired region with data synchronization

C.Failover group listener endpoint

D.Azure Traffic Manager with priority routing

E.Failover group configured between primary and secondary servers

AnswersB, C, E

The secondary must be synchronized to ensure no data loss.

Why this answer

Option B is correct because a failover group requires a secondary database in a paired Azure region that continuously synchronizes data from the primary, which enables minimal-downtime failover with no data loss (RPO near zero). Option C is correct because the failover group listener endpoint provides a stable read-write connection string that automatically redirects clients to the current primary after failover, so applications avoid reconfiguration and downtime is minimized. Option E is correct because the failover group itself must be configured between the primary and secondary servers, defining the databases, replication topology, and automatic/manual failover policies that make the DR strategy work.

Option A is not essential here because geo-redundant backup storage supports backup/restore recovery, not the low-RTO, no-data-loss failover provided by failover groups. Option D is not essential because Azure Traffic Manager is a DNS-based global traffic routing service and does not manage Azure SQL Database replication or failover; the failover group listener already handles client redirection.

Exam trap

The trap is selecting components that seem related to disaster recovery but are not essential for failover groups, such as geo-redundant backups or Traffic Manager. Candidates might overlook the need for the listener endpoint.

Practice this question →

16

MCQeasy

You have an Azure SQL Managed Instance configured with an auto-failover group between two regions. You need to ensure that client applications can automatically connect to the secondary instance after a failover without changing connection strings. What should you configure?

A.Use the failover group listener endpoint in the connection string.

B.Set up a load balancer with health probes.

C.Deploy an Application Gateway with backend pools for each region.

D.Configure a Traffic Manager profile with endpoint monitoring.

AnswerA

The failover group listener provides a stable read-write DNS endpoint that redirects clients to the current primary after failover. Applications keep one connection string, satisfying the no-change requirement, while the listener abstracts the underlying instance swap between regions.

Why this answer

An auto-failover group provides a read/write listener endpoint (and a read-only listener) with a DNS name that always points to the current primary. Applications connect to the listener FQDN, so after failover the DNS resolves to the new primary without any connection string change.

Exam trap

DP-300 often tests the misconception that a generic DNS or load-balancing service is needed for failover, when the failover group's built-in listener endpoint already handles redirection.

How to eliminate wrong answers

Option B is wrong because a load balancer does not participate in Azure SQL Managed Instance failover group DNS redirection and would require manual endpoint management. Option C is wrong because Application Gateway is an HTTP/HTTPS layer-7 load balancer for web workloads, not for TDS/SQL connections. Option D is wrong because Traffic Manager can route DNS but does not integrate with the failover group's listener or understand SQL health the way the built-in listener does.

Practice this question →

17

MCQhard

You are reviewing the ARM template snippet for an Azure SQL Database failover group. The primary server is in East US. The secondary is in West Europe. The readWriteEndpoint has automatic failover with a grace period of 60 minutes. The readOnlyEndpoint is disabled. After a complete outage in East US, what will happen?

A.The failover group will not fail over automatically because the grace period is too long.

B.The failover group will wait 60 minutes, then automatically fail over to West Europe.

C.The failover group will immediately fail over to West Europe.

D.The failover group requires manual failover because readOnlyEndpoint is disabled.

AnswerB

Automatic failover on the readWriteEndpoint triggers only after the configured grace period elapses without primary availability. With 60 minutes set, the group waits that duration before promoting West Europe, so the outage must persist the full hour.

Why this answer

With automatic failover enabled on the read/write endpoint and a 60-minute grace period, Azure SQL failover groups wait the full grace period after detecting the primary outage before promoting the secondary. Only after that window elapses does the geo-secondary in West Europe become the new primary. The readOnlyEndpoint setting is irrelevant to read/write failover behavior.

Exam trap

DP-300 often tests the misconception that a long grace period blocks automatic failover entirely, or that readOnlyEndpoint settings affect read/write failover — candidates must separate the two endpoints and understand grace period as a delay, not a disable.

How to eliminate wrong answers

Option A is wrong because a 60-minute grace period does not prevent automatic failover — it simply delays it; automatic failover still occurs once the grace period expires. Option C is wrong because immediate failover only happens with a grace period of 0 (or when Azure detects the outage and the configured grace period has already elapsed); 60 minutes explicitly delays promotion. Option D is wrong because readOnlyEndpoint being disabled only affects the read-only listener (whether read-only connections are allowed to the secondary); it has no bearing on automatic failover of the read/write endpoint.

Practice this question →

18

MCQhard

You have an Azure SQL Managed Instance configured with a failover group for disaster recovery. The primary instance is in the East US region and the secondary is in West US. You need to perform a planned failover for maintenance with zero data loss. What is the correct sequence of steps?

A.Take the primary instance offline, then failover.

B.Use the Azure portal to perform a planned failover for the failover group.

C.Scale down the primary to reduce cost, then failover.

D.Remove the failover group, perform maintenance, then recreate the failover group.

AnswerB

A planned failover in the failover group completes synchronisation before switching roles, guaranteeing zero data loss — the stem's explicit requirement. Because the secondary is already synchronised via the failover group, the portal operation drains remaining transactions, promotes West US to primary, and demotes East US, satisfying the maintenance scenario without data loss.

Why this answer

For a planned failover with zero data loss in Azure SQL Managed Instance failover groups, the correct approach is to use the Azure portal (or PowerShell/CLI) to perform a planned failover. This ensures that all pending transactions are synchronized to the secondary before switching roles, preventing data loss.

Exam trap

The trap is thinking that manual steps like taking the primary offline or removing the failover group are needed. Candidates might overcomplicate the process instead of using the built-in planned failover feature.

How to eliminate wrong answers

Option A is wrong because taking the primary offline before failover can cause data loss and downtime, as transactions may not be synchronized. Option C is wrong because scaling down the primary does not facilitate a planned failover and may impact performance. Option D is wrong because removing and recreating the failover group is disruptive, time-consuming, and unnecessary for a planned failover.

Practice this question →

19

MCQmedium

Your company has an Azure SQL Database in the General Purpose tier. You need to reduce the recovery point objective (RPO) from 1 hour to less than 1 minute for disaster recovery. Which action should you take?

A.Increase the backup retention period to 35 days.

B.Upgrade the database to Business Critical tier.

C.Enable zone redundancy on the database.

D.Increase the DTU or vCore count.

AnswerB

Upgrading to Business Critical adds synchronous replicas within the region for local HA, but geo-replication remains asynchronous with ~1 hour RPO. It does not achieve sub-minute geo RPO.

Why this answer

None of the listed options reduce the geo-replication RPO to under 1 minute. Upgrading to Business Critical (B) improves local HA with synchronous replicas but does not affect geo-replication, which remains asynchronous with an RPO of about 1 hour. Enabling zone redundancy (C) protects against zone failures, not regional disasters.

Increasing backup retention (A) or DTU/vCore (D) does not change replication mode. To achieve sub-minute RPO for geo-disaster recovery, you must configure Active Geo-Replication or a failover group, which are not among the options.

Exam trap

Do not confuse local high availability (within region) with geo-disaster recovery (across regions). Business Critical's synchronous replicas are in the same region and do not improve geo-replication RPO.

Practice this question →

20

MCQhard

You are responsible for a SQL Server 2019 instance on an Azure VM. The VM is part of a failover cluster instance (FCI) using Azure shared disks. During a recent failover test, the cluster took 15 minutes to bring the database online. You need to reduce the failover time to under 5 minutes. What should you do?

A.Remove unnecessary databases from the FCI and distribute them to other instances.

B.Upgrade the VM to a larger size with more CPU and memory.

C.Increase the size of the Azure shared disks.

D.Enable instant file initialization on all SQL Server instances.

AnswerA

Fewer databases to recover reduces failover time.

Why this answer

Removing unnecessary databases from the FCI reduces the number of databases that need to be recovered during failover, thereby decreasing the overall failover time. Option A is correct. Option B is incorrect because upgrading the VM does not directly reduce the number of databases to recover.

Option C is incorrect because increasing disk size does not improve failover time. Option D is incorrect because instant file initialization helps with file growth, not failover recovery.

Practice this question →

21

MCQeasy

You manage an Azure SQL Database in the East US region. The database uses the General Purpose service tier with geo-redundant backup storage. You need to ensure that in the event of a regional outage, you can restore the database to the West US region with the least possible downtime. What should you use?

A.Configure active geo-replication to a secondary server in West US.

B.Use the geo-restore feature to restore from the geo-redundant backups to a new database in West US.

C.Create a copy-only backup and manually transfer it to West US.

D.Perform a point-in-time restore to a new database in West US.

AnswerA

Active geo-replication must be configured proactively.

Why this answer

Active geo-replication to a secondary server in West US is the correct choice because it maintains a continuously synchronized secondary database in the target region, enabling a fast failover with minimal downtime if the primary region fails. Geo-restore can restore to West US from geo-redundant backups, but it has a much longer recovery time than failing over to an already synchronized secondary. Creating a copy-only backup and manually transferring it is slow and not automated.

Point-in-time restore is limited to the same region and cannot restore directly to West US.

Practice this question →

22

Multi-Selectmedium

You are designing a disaster recovery strategy for a group of Azure SQL Databases hosted on a logical server in the East US region. The solution must provide automatic failover to a secondary region, support read-only access to the secondary during normal operations, and minimize application connection string changes during failover. You plan to use an auto-failover group. Which two actions should you perform? (Choose two.)

Select 2 answers

A.Configure each database with active geo-replication to the secondary server.

B.Set the failover policy to manual to avoid unexpected failovers.

C.Create a secondary logical server in a different Azure region and add the databases to the failover group.

D.Configure the failover group to use a read-write listener endpoint and a read-only listener endpoint.

E.Enable zone redundancy on the primary databases.

AnswersC, D

An auto-failover group requires a secondary server in a different region. You must create the secondary server and add the databases to the failover group. This enables replication and automatic failover. The secondary server must be in a paired region for optimal performance, but any region works.

Why this answer

To implement an auto-failover group, you must create a secondary server in another region and add the databases to the failover group. You should also configure the read-write and read-only listener endpoints to provide stable connection strings and read-only access to the secondary. Zone redundancy is for intra-region HA, active geo-replication is redundant, and manual failover policy contradicts the automatic failover requirement.

Exam trap

The trap here is thinking that active geo-replication is needed in addition to an auto-failover group; the failover group already handles replication.

Practice this question →

23

MCQmedium

You have an Azure SQL Managed Instance configured with a failover group to a secondary region. During a regional outage, the failover group automatically fails over to the secondary. After the primary region is restored, you need to bring the primary back online and re-establish the failover relationship. What should you do?

A.Delete the failover group and recreate it with the original primary as the primary.

B.Add the original primary as a new secondary to the current primary.

C.Initiate a planned failover from the current primary to the original primary.

D.Remove the original primary from the failover group and re-add it.

AnswerC

A planned failover reverses roles without data loss, making the restored original primary the secondary again and re-establishing replication. Forced failover would risk divergence, so the planned operation is required to rebuild the relationship safely.

Why this answer

After an automatic failover, the original primary becomes the secondary. To restore the original configuration, you perform a planned failover from the current primary (the former secondary) back to the original primary. This re-establishes the original roles and the failover group remains intact.

A planned failover ensures no data loss by synchronizing the databases before switching roles.

Exam trap

DP-300 often tests the misconception that after an automatic failover, you must recreate or reconfigure the failover group to restore the original primary, when in fact a planned failover is the correct and seamless method.

How to eliminate wrong answers

Option A is wrong because deleting and recreating the failover group is unnecessary and disruptive; it would require reconfiguring the entire failover group and could lead to downtime. Option B is wrong because the original primary is already part of the failover group as the secondary; adding it as a new secondary is not possible and would not restore the original roles. Option D is wrong because removing and re-adding the original primary would not change its role; it would still be the secondary, and the failover group would remain in the failed-over state.

Practice this question →

24

MCQmedium

You have an Azure SQL Database named DB1 that uses the Hyperscale service tier. The database has a primary replica and multiple named replicas. You need to ensure that read-only workloads are offloaded to a named replica and that the named replica remains available if the primary replica fails. What should you do?

A.Create a geo-secondary in another region and redirect read-only connections to it.

B.Configure the application to connect to the named replica using its connection string and set ApplicationIntent=ReadOnly.

C.Enable read-scale out on the primary database and use the read-only listener.

D.Use the primary replica's connection string with ApplicationIntent=ReadOnly to route to a named replica.

AnswerB

Named replicas in Hyperscale are separate read-only replicas that can be connected to directly using their own connection string. Setting ApplicationIntent=ReadOnly ensures the connection is routed to a read-only replica if using a listener. This offloads read workloads and the named replica remains available even if the primary fails, as it is an independent replica.

Why this answer

Named replicas in Azure SQL Database Hyperscale are independent read-only replicas that must be accessed via their own connection string. They continue to serve read workloads even if the primary fails, providing high availability for read operations. Using the primary connection string with ApplicationIntent=ReadOnly does not target named replicas; it targets the built-in read-only replicas.

Geo-secondaries are for disaster recovery and not the same as named replicas.

Exam trap

The trap here is assuming that ApplicationIntent=ReadOnly on the primary connection string will automatically route to a named replica, when in fact named replicas require a dedicated connection string.

Practice this question →

25

Multi-Selecteasy

You are planning high availability for an Azure SQL Database that runs an e-commerce application. The database uses the Business Critical service tier. Which TWO features are automatically enabled to provide high availability within a single region? (Choose two.)

Select 2 answers

A.Automatic failover to a secondary replica if the primary becomes unavailable.

B.Multiple synchronous replicas (one primary, two secondary) in the same region.

C.Auto-failover groups with a secondary in another region.

D.Active geo-replication to a paired region.

E.Read scale-out with a readable secondary replica.

AnswersA, B

Business Critical provisions a primary plus secondary replicas with synchronous commit, so the platform automatically redirects connections to a healthy replica when the primary fails. This built-in failover satisfies the single-region high availability requirement without manual intervention.

Why this answer

Option A is correct because in the Business Critical tier Azure SQL Database automatically provisions a primary replica plus secondary replicas and performs automatic failover to a secondary if the primary becomes unavailable, with no user action required. Option B is correct because Business Critical uses Always On availability group technology to maintain multiple synchronous replicas (one primary and two secondary) within the same region, ensuring data redundancy and fast failover. Option C is incorrect because auto-failover groups are a user-configured feature for cross-region disaster recovery, not an automatic single-region HA capability.

Option D is incorrect because active geo-replication is a manually configured cross-region replication feature, not automatically enabled for single-region HA. Option E is incorrect because read scale-out using a readable secondary is an optional configuration for offloading read workloads, not an automatic HA mechanism.

Exam trap

The trap is conflating single-region automatic HA (built into Business Critical) with cross-region DR features like auto-failover groups and active geo-replication, which are separate and manually configured.

Practice this question →

26

MCQmedium

You manage an Azure SQL Database that uses the General Purpose tier. The database has a failover group with a secondary in a paired region. During a regional outage, you initiate a forced failover. After the outage is resolved, you want to bring the original primary region back online without data loss. What should you do?

A.Initiate a forced failover from the new primary to the old primary.

B.Perform a forced failover again to switch back.

C.Wait for data synchronization, then initiate a planned failover.

D.Delete the failover group and recreate it with the original primary as primary.

AnswerC

After a forced failover the original primary becomes the secondary and must resynchronise. Waiting for synchronisation to complete, then running a planned failover, returns workloads to the original region with no data loss, satisfying the stated requirement.

Why this answer

After a forced failover, the original primary becomes the secondary and enters a state where it may have diverged data. To restore it as primary without data loss, you must wait for geo-replication to catch up and re-synchronize, then perform a planned (graceful) failover. A planned failover ensures no data loss by confirming the secondary is fully synchronized before switching roles.

Exam trap

DP-300 often tests the difference between forced and planned failover, and candidates mistakenly think any failover can be used to switch back without considering data synchronization requirements.

How to eliminate wrong answers

Option A is wrong because initiating a forced failover from the new primary to the old primary would again risk data loss and is not the correct way to restore the original primary after an outage. Option B is wrong because performing another forced failover does not guarantee synchronization and can cause additional data loss. Option D is wrong because deleting and recreating the failover group is disruptive, unnecessary, and does not ensure data consistency; it also loses the existing replication configuration.

Practice this question →

27

MCQmedium

Refer to the exhibit. You are reviewing an ARM template for deploying an Azure SQL Database. The template specifies a point-in-time restore from a source database. The source database is configured with geo-redundant backup storage. You need to ensure that the restored database can be used for disaster recovery in a different region. What is missing from the template to achieve this?

A.Add a 'location' property to the database resource.

B.Set 'zoneRedundant' to true.

C.Change 'requestedBackupStorageRedundancy' to 'GeoZone'.

D.Set 'createMode' to 'GeoRestore' and specify a target server in the desired region.

AnswerD

GeoRestore is the only createMode that restores a geo-redundant backup into a different region, so the template must set createMode to GeoRestore and name a target server in the desired region. This satisfies the cross-region disaster recovery requirement.

Why this answer

To restore a geo-redundant backup to a different region, the ARM template must use createMode 'GeoRestore' and point to a target logical server in the desired region. A standard PointInTimeRestore restores to the same region and server, so it cannot satisfy the cross-region DR requirement. GeoRestore is the specific createMode that instructs Azure SQL to pull the geo-replicated backup and materialize the database on the specified target server in the alternate region.

Exam trap

DP-300 often tests the distinction between PointInTimeRestore (same region) and GeoRestore (cross-region), tricking candidates into thinking that adding a location property or changing backup redundancy alone enables cross-region recovery.

How to eliminate wrong answers

Option A is wrong because simply adding a 'location' property to the database resource does not change the restore semantics; the database inherits the server's region, and a PointInTimeRestore createMode still targets the original region. Option B is wrong because zoneRedundant applies to availability-zone resiliency within a single region, not cross-region disaster recovery. Option C is wrong because 'GeoZone' is not a valid value for requestedBackupStorageRedundancy; valid values are Local, Zone, and Geo, and changing backup redundancy alone does not perform a cross-region restore.

Practice this question →

28

MCQmedium

You have an Azure SQL Database with active geo-replication. You need to monitor the replication lag to ensure the RPO is met. Which metric should you monitor?

A.DTU consumption

B.Replication lag

C.Data IO percentage

D.Deadlocks

AnswerB

Replication lag measures the delay between the primary and secondary database in seconds, directly quantifying potential data loss against the RPO. Monitoring it confirms whether active geo-replication keeps the secondary close enough to meet the stated recovery point objective.

Why this answer

Active geo-replication in Azure SQL Database continuously ships transaction log records from the primary to the secondary. The 'Replication lag' metric specifically measures the delay between the primary and secondary, which directly maps to your Recovery Point Objective (RPO). Monitoring this metric lets you verify that the secondary is keeping up and that you won't lose more than the acceptable amount of data in a failover.

Exam trap

DP-300 often tests the confusion between performance metrics (DTU, IO) and replication-specific metrics — candidates pick DTU because it sounds like a health indicator, but RPO is about data delay, not resource usage.

How to eliminate wrong answers

Option A is wrong because DTU consumption measures compute resource usage on the primary, not the data synchronization delay to the secondary — high DTU does not necessarily mean high replication lag. Option C is wrong because Data IO percentage reflects storage I/O utilization, which is unrelated to the geo-replication RPO. Option D is wrong because deadlocks indicate concurrency conflicts in the workload, not replication latency.

Practice this question →

29

MCQmedium

Your company runs a critical application on Azure SQL Managed Instance in the North Europe region. The application requires an RPO of 5 minutes and an RTO of 2 hours during a regional disaster. The current setup uses a single instance with geo-redundant backup storage (RA-GRS). During a disaster recovery planning session, you discover that geo-restore from RA-GRS backups takes approximately 4 hours to complete, which exceeds the RTO. You need to modify the disaster recovery solution to meet the RTO without exceeding the budget significantly. The solution must minimize administrative overhead. What should you do?

A.Change backup storage to locally-redundant (LRS) and rely on point-in-time restore.

B.Enable zone redundancy on the primary instance.

C.Deploy a secondary instance in a different region and configure a failover group.

D.Scale the instance to a higher service tier to improve restore performance.

AnswerC

A failover group with a secondary instance in another region provides asynchronous replication with an RPO of about 5 seconds and rapid failover, meeting the 2-hour RTO. It minimises administrative overhead compared with manual geo-restore, which took 4 hours.

Why this answer

A failover group in Azure SQL Managed Instance provides a secondary instance in a different region with automatic or manual failover, and it replicates data asynchronously with an RPO typically under 5 seconds, well within the 5-minute requirement. Failover groups also provide read-write and read-only listener endpoints, minimizing application changes and administrative overhead. This meets the RTO of 2 hours because failover can be triggered quickly, and the secondary is already provisioned and synchronized.

Exam trap

DP-300 often tests the difference between geo-restore (slow, high RTO) and failover groups (fast, low RTO), so candidates incorrectly assume RA-GRS backups alone can meet aggressive RTO requirements.

How to eliminate wrong answers

Option A is wrong because LRS backups are stored only in the primary region and do not support geo-restore; point-in-time restore from LRS cannot recover from a regional disaster. Option B is wrong because zone redundancy protects against datacenter-level failures within a single region, not a full regional disaster, so it does not meet the cross-region DR requirement. Option D is wrong because scaling to a higher service tier may improve performance but does not change the geo-restore time significantly; geo-restore performance is primarily limited by backup restore throughput and is not directly tied to the service tier in a way that guarantees the 2-hour RTO.

Practice this question →

30

MCQmedium

You manage an Azure SQL Database named OrderDB in the Business Critical service tier. A compliance requirement mandates that the database must remain available even if an entire Azure availability zone fails within the primary region. You need to configure the database to meet this requirement with the least administrative effort. What should you do?

A.Enable zone redundancy for the database.

B.Create a failover group with an automatic failover policy.

C.Increase the database compute size to the maximum vCore limit.

D.Configure active geo-replication to a secondary region.

AnswerA

Zone redundancy in the Business Critical tier automatically provisions replicas across multiple availability zones, so the database remains online if one zone fails. It requires no application changes and minimal configuration, fulfilling the compliance requirement with least effort.

Why this answer

Zone redundancy in the Business Critical tier replicates the database across multiple availability zones, ensuring automatic failover and continuous availability during a zone outage. It is the simplest configuration change that meets the requirement without application modifications or manual intervention.

Exam trap

The trap here is confusing cross-region disaster recovery features like failover groups with intra-region high availability mechanisms such as zone redundancy.

Practice this question →

31

MCQmedium

Refer to the exhibit. You are reviewing an ARM template for an Azure SQL Database backup policy. The database is used for a reporting workload that is updated daily. The compliance team requires that point-in-time restore (PITR) be available for the past 30 days. What action should you take?

A.Change the retentionDays property to 30.

B.Change the diffBackupIntervalInHours to 24.

C.No action is needed; the current policy meets the requirement.

D.Add a long-term retention policy with a weekly retention of 30 days.

AnswerA

retentionDays controls PITR retention; setting to 30 meets the requirement.

Why this answer

The retentionDays property in the ARM template controls the point-in-time restore (PITR) retention period. Currently set to 14 days, it must be changed to 30 days to meet the compliance requirement. Option B is incorrect because diffBackupIntervalInHours specifies the interval for differential backups, not retention.

Option C is incorrect because 14 days does not satisfy the 30-day requirement. Option D is incorrect because long-term retention (LTR) is for archival purposes beyond PITR and does not replace the PITR retention setting.

Practice this question →

32

Multi-Selectmedium

Which THREE components are required to configure an auto-failover group for Azure SQL Database? (Choose three.)

Select 3 answers

A.Active geo-replication

B.A failover group name

C.Secondary logical server in a different region

D.Primary logical server

E.An availability group listener

AnswersB, C, D

A failover group name is mandatory because it identifies the group and forms the read-write listener endpoint (server.database.windows.net). Without this unique name, Azure cannot create the group or route connections, so it is one of the three required components alongside the primary and secondary servers.

Why this answer

A failover group is a named resource, so option B (a failover group name) is required to create and reference it. Option C (a secondary logical server in a different region) is required because the failover group replicates databases to a partner server, and placing it in a different Azure region provides the geo-redundancy that failover groups are designed for. Option D (the primary logical server) is required because the failover group is defined between a primary and secondary server, with the primary hosting the read-write databases.

Option A is not required because failover groups automatically manage the geo-replication relationship; you do not manually configure active geo-replication as a prerequisite. Option E is not applicable because an availability group listener is an Always On availability group concept for SQL Server, not an Azure SQL Database auto-failover group component.

Exam trap

DP-300 often tests the misconception that active geo-replication must be configured separately before creating an auto-failover group, or that an availability group listener is needed, confusing Azure SQL Database with SQL Server Always On.

Practice this question →

33

MCQmedium

Your Azure SQL Database is configured with a failover group between two regions. The primary database experiences a catastrophic failure that prevents any connectivity. You need to initiate a failover to the secondary region. However, the failover group status shows 'Primary is down'. What should you do?

A.Run a planned failover to ensure zero data loss.

B.Wait for the primary to come back online and then failover.

C.Remove the primary database from the failover group and then failover.

D.Run a forced failover accepting potential data loss.

AnswerD

A forced failover promotes the secondary to primary despite the failover group reporting 'Primary is down', which blocks a normal planned failover. Because the primary is unreachable, asynchronous replication means some committed transactions may not have reached the secondary, so accepting potential data loss is unavoidable to restore write availability.

Why this answer

A forced failover (also called an unplanned failover) is used when the primary database is completely unavailable, and you accept potential data loss. Option A is incorrect because a planned failover requires both the primary and secondary to be online to ensure zero data loss. Option B is incorrect because waiting for the primary to come back online is not an appropriate action when immediate failover is required due to catastrophic failure.

Option C is incorrect because you cannot remove the primary database from a failover group when it is down; the failover group must be failed over as a whole.

Practice this question →

34

Multi-Selecthard

Which THREE are valid methods to implement disaster recovery for Azure SQL Database? (Select three.)

Select 3 answers

A.Failover groups

B.Always On availability groups

C.Active geo-replication

D.Long-term backup retention

E.Geo-restore (point-in-time restore)

AnswersA, C, E

Failover groups provide automatic geo-replication and a listener endpoint, letting you redirect connections to a secondary server in another region without changing connection strings. This satisfies the disaster recovery requirement by enabling rapid recovery from a regional Azure SQL Database outage.

Why this answer

Options A, C, and E are correct. Failover groups and active geo-replication are built-in disaster recovery features for Azure SQL Database that allow failover to a secondary region. Geo-restore (point-in-time restore to a different region) is also a valid DR method by restoring from geo-replicated backups.

Option B (Always On availability groups) is a feature for SQL Server on VMs or on-premises, not for Azure SQL Database. Option D (long-term backup retention) is a backup retention capability, not a disaster recovery method.

Practice this question →

35

MCQmedium

You have an Azure SQL Database configured with active geo-replication to a secondary region. The primary region experiences a full outage. You need to fail over with minimal data loss. What should you do?

A.Initiate an unplanned failover from the primary to the secondary.

B.Delete the secondary database and create a new one in the primary region.

C.Initiate a planned failover from the primary to the secondary.

D.Create a new secondary database in the same region as the primary.

AnswerA

Unplanned failover immediately promotes the geo-secondary to primary without waiting for the primary to recover, accepting the small replication lag as potential data loss. This is the only option that restores write availability during a full regional outage with minimal loss.

Why this answer

Initiating an unplanned failover from the primary to the secondary is the correct action because the primary region is experiencing a full outage, and unplanned failover is designed for such disaster scenarios. It promotes the secondary database to become the new primary with minimal data loss, typically within the recovery point objective (RPO).

Exam trap

The trap is confusing planned failover (for maintenance) with unplanned failover (for outages), or attempting to create new resources during an outage.

How to eliminate wrong answers

Option B is wrong because deleting the secondary and creating a new one in the primary region is impossible during an outage and would result in data loss. Option C is wrong because a planned failover requires the primary to be online and is used for planned maintenance, not for an outage. Option D is wrong because creating a new secondary in the same region as the primary does not help when the primary region is down.

Practice this question →

36

MCQeasy

You need to configure a backup policy for Azure SQL Database that allows restoring to any point within the last 7 days. What is the minimum point-in-time restore retention period you should set?

A.1 day

B.7 days

C.14 days

D.3 days

AnswerB

A 7-day point-in-time restore retention period satisfies the stem's requirement to restore to any point within the last 7 days, since Azure SQL Database's minimum configurable PITR retention is exactly 7 days. Setting 7 days meets the constraint without exceeding it, making it the minimum valid value.

Why this answer

Azure SQL Database supports point-in-time restore (PITR) with a configurable retention period between 1 and 35 days, with a default of 7 days. To allow restoring to any point within the last 7 days, the minimum retention period that satisfies the requirement is exactly 7 days. Setting a shorter period (1 or 3 days) would not meet the stated requirement, and 14 days exceeds the minimum needed.

Exam trap

DP-300 often tests the distinction between the default retention (7 days) and the configurable range (1-35 days), causing candidates to pick a value that is either too short or assumes the default is the only option.

How to eliminate wrong answers

Option A is wrong because a 1-day retention only allows restoring to points within the last 24 hours, which does not satisfy the 7-day requirement. Option C is wrong because 14 days exceeds the minimum required retention and is not the minimum value that meets the requirement. Option D is wrong because 3 days only covers the last 72 hours, which is insufficient for a 7-day restore window.

Practice this question →

37

MCQmedium

You have an Azure SQL Database that is part of a failover group with automatic failover. The primary region experiences a complete outage. The failover group automatically fails over to the secondary region. After the primary region is restored, you need to ensure the database is operational in the primary region with minimal data loss. What should you do?

A.Initiate a manual failover of the failover group back to the primary region.

B.Wait for automatic failback to occur.

C.Restore the database from a geo-redundant backup.

D.Delete the failover group and recreate it with the original primary as the new primary.

AnswerA

After the primary region recovers, the failover group remains on the secondary. A manual failover returns the primary to active role, restoring operational service there while the group's asynchronous replication limits data loss to the last synchronised transaction.

Why this answer

Azure SQL failover groups support automatic failover to the secondary region, but failback is not automatic. After the primary region is restored, you must manually initiate a failover to return the primary database to the original primary region. This ensures the database is operational in the primary region with minimal data loss, as the failover group maintains replication.

Exam trap

DP-300 often tests the misconception that failover groups automatically fail back; candidates must remember that failback is always manual.

How to eliminate wrong answers

Option B is wrong because Azure SQL failover groups do not perform automatic failback; failback requires manual initiation. Option C is wrong because restoring from a geo-redundant backup would lose recent transactions and is unnecessary when the failover group is intact. Option D is wrong because deleting and recreating the failover group is disruptive, unnecessary, and does not leverage the existing replication topology.

Practice this question →

38

MCQmedium

You query the sys.dm_geo_replication_link_status dynamic management view for an Azure SQL Database configured with active geo-replication. The exhibit shows the output. What does this indicate about the replication health?

A.The secondary is fully synchronized with minimal lag.

B.The secondary role indicates a failover has occurred.

C.The secondary is 5 seconds behind, indicating a problem.

D.The replication is in the seeding phase.

AnswerA

Correct.

Why this answer

The replicationLag of 5 seconds is minimal and normal for active geo-replication, indicating the secondary is nearly synchronized. The replicationState 'CATCH_UP' confirms that the secondary is fully caught up with the primary. Options B, C, and D are incorrect: B is wrong because a secondary role is expected in geo-replication; C is wrong because 5 seconds lag is not a problem; D is wrong because the state is CATCH_UP, not SEEDING.

Practice this question →

39

MCQhard

You have an Azure SQL Managed Instance named MI1 in the West Europe region. The instance hosts a mission-critical database that must be recoverable within 30 minutes in the event of a regional outage. You need to implement a disaster recovery solution that minimizes data loss and administrative effort. The solution must support read-only access to the secondary during normal operations. What should you configure?

A.Configure geo-replication for the database to a secondary managed instance in North Europe.

B.Set up a failover group with a secondary managed instance, but do not enable the read-only listener.

C.Use log shipping to a secondary managed instance in North Europe.

D.Create an auto-failover group with MI1 as the primary and a secondary managed instance in North Europe.

AnswerD

Auto-failover groups for Azure SQL Managed Instance support automatic failover and provide a read-only listener endpoint for the secondary. This allows read-only access during normal operations. The RPO is typically less than 5 seconds, and the RTO is typically under 30 minutes, meeting the requirement. It also minimizes administrative effort because failover is automatic.

Why this answer

Auto-failover groups for Azure SQL Managed Instance are the correct choice because they provide automatic failover, a read-only listener for the secondary, and low RPO/RTO. They are specifically designed for cross-region disaster recovery for managed instances. Geo-replication is not available for managed instances, log shipping is not native, and omitting the read-only listener fails the read-only access requirement.

Exam trap

The trap here is confusing Azure SQL Database features like active geo-replication with SQL Managed Instance capabilities; managed instances do not support active geo-replication.

Practice this question →

40

MCQeasy

A company plans to migrate an on-premises SQL Server database to Azure SQL Database Managed Instance. They require a high availability solution that provides automatic failover between replicas within the same region with an RPO of 0 and an RTO of less than 30 seconds. Which service tier should they choose?

A.Business Critical

B.General Purpose

C.Azure SQL Database (single)

D.Hyperscale

AnswerA

Business Critical uses Always On availability groups with multiple synchronous replicas in the same region, delivering zero data loss (RPO 0) and automatic failover typically under 30 seconds. Its local SSD and built-in read replica satisfy the stem's same-region, low-latency failover constraint, unlike General Purpose's single remote-storage replica.

Why this answer

Business Critical service tier in Azure SQL Managed Instance provides built-in high availability with multiple replicas and automatic failover, achieving an RPO of 0 and RTO typically under 30 seconds. It uses Always On availability groups under the hood with local redundant storage and supports read-only routing. This tier is designed for mission-critical workloads requiring the lowest latency and highest resilience.

Exam trap

DP-300 often tests the difference between General Purpose and Business Critical HA capabilities, and candidates may incorrectly assume Hyperscale or single database tiers offer the same sub-30-second RTO with zero RPO.

How to eliminate wrong answers

Option B is wrong because General Purpose uses remote storage and provides an RTO of around 1 hour and RPO of 5-10 minutes, not meeting the sub-30-second RTO and zero RPO. Option C is wrong because Azure SQL Database (single) is a different deployment model, not Managed Instance, and its HA characteristics vary by tier; the question specifies Managed Instance. Option D is wrong because Hyperscale is optimized for large databases and read-scale, but its HA SLA and failover times are not as stringent as Business Critical for the stated RPO/RTO.

Practice this question →

41

MCQeasy

Your company requires that all production databases in Azure SQL Database have an RPO of less than 5 seconds and an RTO of less than 1 minute during a regional outage. You need to recommend a high availability and disaster recovery solution. Which feature should you use?

A.Zone-redundant configuration (Hyperscale service tier)

B.Auto-failover groups with active geo-replication

C.Long-term retention (LTR) backups

D.Geo-restore from geo-redundant backups

AnswerB

Auto-failover groups with active geo-replication replicate asynchronously to a secondary region, giving an RPO of roughly 5 seconds and RTO typically under a minute. This satisfies both the sub-5-second RPO and sub-1-minute RTO constraints for a regional outage.

Why this answer

Auto-failover groups with active geo-replication provide a group-level failover that can redirect all databases in a group to a secondary region with an RPO of about 5 seconds and an RTO of under a minute, meeting both requirements. Active geo-replication continuously replicates transactions to secondary databases, and the failover group automates the DNS and connection redirection so applications reconnect quickly.

Exam trap

DP-300 often tests the difference between zone redundancy (single-region HA) and geo-replication/failover groups (cross-region DR), and candidates frequently pick zone-redundant options for regional outage scenarios.

How to eliminate wrong answers

Option A is wrong because a zone-redundant Hyperscale configuration protects against a zone failure within a single region, not a regional outage — it does not provide cross-region disaster recovery. Option C is wrong because Long-Term Retention backups are for compliance and long-term archival, not for fast failover; restoring from LTR takes hours and has an RPO measured in hours or days. Option D is wrong because geo-restore from geo-redundant backups has an RPO of up to 1 hour and an RTO of up to 12 hours, far exceeding the 5-second RPO and 1-minute RTO requirements.

Practice this question →

42

MCQmedium

You manage a SQL Managed Instance in the East US region. The instance must be recoverable within 1 hour in the event of a regional disaster. You need to configure a secondary replica in a paired region with automatic failover. Which solution meets the requirement?

A.Configure log shipping to a secondary instance in West US.

B.Enable geo-redundant backup storage and use geo-restore.

C.Create an auto-failover group with a secondary replica in West US.

D.Deploy an Always On availability group with a synchronous secondary in West US.

AnswerC

Auto-failover groups provide a secondary SQL Managed Instance in a paired region with automatic failover and readable endpoints, meeting the one-hour regional recovery requirement. East US pairs with West US, so the replica location is valid.

Why this answer

An auto-failover group in Azure SQL Managed Instance provides a secondary replica in a paired region with automatic failover, meeting the requirement for recovery within 1 hour. It uses asynchronous replication and allows a single connection string to fail over automatically, ensuring business continuity during a regional disaster.

Exam trap

DP-300 often tests the difference between automatic and manual failover solutions, and candidates may incorrectly choose geo-restore or log shipping because they are familiar with backup-based recovery, missing the requirement for automatic failover.

How to eliminate wrong answers

Option A (Log shipping) is wrong because it requires manual failover and does not provide automatic failover; recovery time depends on the log shipping frequency and manual intervention. Option B (Geo-redundant backup storage and geo-restore) is wrong because geo-restore is a manual process that can take hours and does not provide automatic failover. Option D (Always On availability group with synchronous secondary in West US) is wrong because synchronous replication across regions introduces high latency and is not supported for cross-region replicas in SQL Managed Instance; it would also not provide automatic failover across regions.

Practice this question →

43

Multi-Selectmedium

You need to design a disaster recovery solution for an Azure SQL Database that uses the General Purpose service tier. The solution must have an RTO of 1 hour and an RPO of 15 minutes. Which TWO options can achieve these requirements?

Select 2 answers

A.Point-in-time restore (PITR) using geo-redundant backup storage.

B.Long-term retention (LTR) backups.

C.Auto-failover group with a secondary in a different region.

D.Active geo-replication to a secondary server in a paired region.

E.Zone redundancy on the primary database.

AnswersC, D

Auto-failover groups use active geo-replication and provide automatic failover. The RPO is the same as active geo-replication (seconds to minutes) and failover completes within minutes, meeting both targets.

Why this answer

Option C (auto-failover group with a secondary in a different region) is correct because failover groups provide a readable/writable secondary in another region with an RPO of about 5 seconds and an RTO typically under 1 hour, satisfying both the 15-minute RPO and 1-hour RTO. Option D (active geo-replication to a secondary server in a paired region) is also correct because it continuously replicates transactions asynchronously with an RPO of roughly 5 seconds and supports a manual/forced failover that can complete well within 1 hour, meeting the stated targets. Option A (PITR using geo-redundant backup storage) is not appropriate because PITR restores to a point in time from backups with an RPO of up to 10 minutes but an RTO that can exceed 1 hour depending on database size, and it is a restore operation rather than a fast failover.

Option B (LTR backups) is incorrect because LTR is designed for long-term compliance retention (up to 10 years) and does not provide the low RTO/RPO needed for disaster recovery. Option E (zone redundancy on the primary database) is incorrect because zone redundancy only protects against a single-zone datacenter failure within the same region and does not address a regional disaster or provide cross-region failover.

Exam trap

DP-300 often tests the confusion between backup-based recovery (PITR/LTR/geo-restore) and replication-based DR (geo-replication/failover groups) — candidates pick PITR because it sounds like a DR feature, but its restore time and retention-bound RPO rarely meet strict RTO/RPO SLAs.

Practice this question →

44

MCQmedium

Your company runs a global e-commerce application using Azure SQL Database in the West Europe region. You need to implement a solution that provides automatic failover and allows the secondary region to be used for read-only queries during normal operations. The secondary must be in a different region. Which configuration meets these requirements?

A.Enable read scale-out on the primary database.

B.Create an auto-failover group with a secondary in West US and use the secondary as readable.

C.Configure active geo-replication to a secondary server in West US and implement application-level failover logic.

D.Configure geo-restore with a recovery point objective of 1 hour.

AnswerB

Auto-failover groups replicate asynchronously to a paired region and expose a read-write listener plus read-only listener, giving automatic failover and readable secondary. Placing the secondary in West US meets the different-region constraint while supporting read-only queries.

Why this answer

An auto-failover group in Azure SQL Database provides automatic failover to a secondary region and allows the secondary database to be used for read-only queries when configured as readable. It also provides a read-write and read-only listener endpoint, so applications can connect without changing connection strings after failover. This meets both the automatic failover and read-only query requirements.

Exam trap

DP-300 often tests the distinction between active geo-replication (manual failover, no listener) and auto-failover groups (automatic failover, listener endpoints) — candidates pick active geo-replication when automatic failover is required.

How to eliminate wrong answers

Option A is wrong because read scale-out only provides an additional read-only replica in the same region — it does not provide cross-region failover or a secondary in a different region. Option C is wrong because active geo-replication requires the application to implement its own failover logic (it does not provide automatic failover) and does not provide listener endpoints, so it fails the 'automatic failover' requirement. Option D is wrong because geo-restore is a backup-based recovery method with a much longer RPO (up to 1 hour) and RTO, and it does not provide a continuously available readable secondary for normal operations.

Practice this question →

45

MCQhard

Your company has an Azure SQL Managed Instance in the General Purpose tier. You need to configure a failover group for disaster recovery. The secondary managed instance must be in a different region and must also be used for read-only workloads. During a failover, you want to minimize data loss. Which configuration should you use?

A.Enable zone redundancy on the primary and secondary instances.

B.Create a failover group and configure the secondary instance to allow read-only connections.

C.Configure log shipping between the primary and secondary instances.

D.Use active geo-replication instead of a failover group.

AnswerB

Failover groups support readable secondary and minimize data loss.

Why this answer

Failover groups for Azure SQL Managed Instance allow you to configure the secondary instance to allow read-only connections, enabling it to serve read-only workloads. This minimizes data loss by using automatic replication with a Recovery Point Objective (RPO) of less than 1 second. Option A (zone redundancy) provides high availability within a region, not disaster recovery across regions.

Option C (log shipping) is not a built-in feature for managed instances and does not support automatic failover. Option D (active geo-replication) is not supported for managed instances; failover groups are the recommended solution.

Practice this question →

46

MCQmedium

Your company has an Azure SQL Database that uses active geo-replication to a secondary region. The primary database is hit by a logical corruption error. You need to restore the database to a point before the corruption occurred with minimal data loss. What should you do?

A.Fail over to the secondary region and then fail back.

B.Use the geo-replicated secondary to recover the data.

C.Seeding the secondary from a backup of the primary.

D.Restore the primary database to a point in time before the corruption using automated backups.

AnswerD

Automated backups retain point-in-time restore capability, so restoring the primary to a timestamp before the logical corruption removes the bad data. Geo-replication copies corruption to the secondary, so it cannot help; point-in-time restore directly satisfies the minimal-data-loss constraint.

Why this answer

Logical corruption requires point-in-time restore from automated backups to a time before the corruption occurred. Active geo-replication replicates the corruption to the secondary, so it cannot be used to recover. Restoring the primary database to a point in time is the correct approach to minimize data loss.

Exam trap

DP-300 often tests the confusion between using geo-replication for disaster recovery versus point-in-time restore for logical corruption, tricking candidates into choosing failover options.

How to eliminate wrong answers

Option A is wrong because failing over to the secondary would just move the corrupted data to the primary role. Option B is wrong because the geo-replicated secondary contains the same corrupted data. Option C is wrong because seeding the secondary from a backup of the primary would not recover from corruption; it would just copy the corrupted data.

Practice this question →

47

MCQhard

You are reviewing a JSON configuration for an Azure SQL Database. The exhibit shows the database properties. Which statement about this database is correct?

A.The database has one high-availability replica.

B.The configuration is invalid because General Purpose tier cannot be zone-redundant.

C.The database uses locally-redundant backup storage.

D.The database is in General Purpose tier and supports zone redundancy.

AnswerD

The General Purpose service tier supports zone redundancy when the configuration enables it, which the exhibit's properties confirm. This distinguishes it from Business Critical, which also offers zone redundancy, and from Basic or Standard tiers, which do not support it.

Why this answer

The JSON configuration shows zoneRedundant set to true and the service tier is General Purpose. As of current Azure SQL Database documentation, zone redundancy is supported for the General Purpose tier (vCore purchasing model) in many regions. Therefore, the configuration is valid.

Option D correctly states that the database is in General Purpose tier and supports zone redundancy. Option A is incorrect because highAvailabilityReplicaCount is 0, not 1. Option B is incorrect because zone redundancy is available for General Purpose.

Option C is incorrect because backupStorageRedundancy is Geo (geo-redundant), not locally-redundant.

Exam trap

Candidates may incorrectly assume that zone redundancy is only for Business Critical, but Azure now supports it for General Purpose (vCore) in many regions.

Practice this question →

48

MCQmedium

You have an Azure SQL Database in the Hyperscale service tier. You need to ensure that the database remains available during a single Azure zone failure. The solution must not require manual intervention. What should you configure?

A.Create a failover group with a secondary in a different zone.

B.Enable zone redundancy on the Hyperscale database.

C.Configure active geo-replication to a secondary server in a different zone.

D.Configure an auto-failover group with a secondary in a different zone.

AnswerB

Hyperscale zone redundancy provides automatic recovery from zone failure.

Why this answer

Hyperscale databases support zone redundancy, which automatically places database replicas in different availability zones, ensuring availability during a single zone failure without manual intervention. Option A is incorrect because failover groups with a secondary in a different zone are used for SQL Managed Instance or other service tiers, not for Hyperscale zone redundancy. Option C is incorrect because active geo-replication is for disaster recovery across regions, not for zone-level failures.

Option D is incorrect because auto-failover groups are for SQL Managed Instance or other tiers, and zone redundancy is the native solution for Hyperscale.

Practice this question →

49

MCQmedium

Your company has a compliance requirement to keep database backups for 10 years. You are using Azure SQL Database. Which backup retention feature should you use?

A.Long-term retention (LTR) policy

B.Geo-redundant storage (GRS)

C.Automated backups

D.Point-in-time restore (PITR)

AnswerA

Long-term retention stores full backups in Azure Blob storage for up to 10 years, beyond the default point-in-time and short-term retention windows. That satisfies the compliance requirement without relying on the standard automated backup retention period.

Why this answer

Long-term retention (LTR) policy is the correct feature for keeping database backups for 10 years, as it supports retention of full backups for up to 10 years. Point-in-time restore (PITR) is limited to a maximum of 35 days and cannot meet the 10-year requirement. Geo-redundant storage (GRS) provides geographic redundancy for backups but does not extend the retention period.

Automated backups are retained for a maximum of 35 days by default and cannot be configured for 10-year retention.

Practice this question →

50

MCQmedium

You have an Azure SQL Database in the General Purpose service tier. The database must be available during a planned patching event that updates the underlying infrastructure. What high availability feature is provided by default?

A.Active geo-replication

B.Zone-redundant availability

C.Built-in high availability with a standby replica

D.Business Critical service tier

AnswerC

The General Purpose service tier provides built-in high availability through automatic compute failover to a different node. While often described as a standby replica, the mechanism is actually compute failover with shared storage, ensuring availability during planned patching events.

Why this answer

Azure SQL Database in the General Purpose service tier includes built-in high availability with a standby replica, which is provisioned automatically and used to fail over during planned maintenance or unplanned outages. This built-in HA ensures the database remains available during patching events without requiring the customer to configure geo-replication or zone redundancy. The standby replica is maintained synchronously and failover is automatic.

Exam trap

DP-300 often tests the difference between default built-in HA and optional features like zone redundancy or geo-replication, and candidates incorrectly select the more advanced feature when the question asks what is provided by default.

How to eliminate wrong answers

Option A is wrong because active geo-replication is a customer-configured disaster recovery feature for cross-region replication, not the default HA mechanism for planned maintenance. Option B is wrong because zone-redundant availability is an optional configuration (available in Premium/Business Critical and some General Purpose configurations) that must be explicitly enabled, not provided by default. Option D is wrong because Business Critical is a different service tier with local SSD and higher IOPS, not the HA feature itself, and the question specifies General Purpose.

Practice this question →

51

MCQhard

Refer to the exhibit. You run the Azure CLI command to check the configuration of an Azure SQL Database named db1. The output shows zoneRedundant is true and replicationRole is Primary. Which statement is true about this database?

A.The database is configured with active geo-replication to a secondary region.

B.The database is zone-redundant and is the primary database in its replication relationship.

C.The database is a Hyperscale database with zone redundancy enabled.

D.The database has a readable secondary replica in a different Azure availability zone.

AnswerB

The CLI output directly reports zoneRedundant true, meaning replicas span availability zones, and replicationRole Primary, meaning this database accepts writes in its geo-replication relationship. Both properties are read straight from the returned configuration, so the statement matches the observed values.

Why this answer

The output shows zoneRedundant is true, meaning the database is deployed across multiple availability zones within its region for high availability, and replicationRole is Primary, meaning it is the primary in a replication relationship (such as a failover group or active geo-replication). Option B correctly combines both facts. The zoneRedundant flag has nothing to do with cross-region replication, so options A and D are incorrect, and Hyperscale is a separate service tier not indicated by these properties.

Exam trap

DP-300 often tests the confusion between zone redundancy (intra-region HA) and geo-replication (cross-region DR), so candidates incorrectly assume zoneRedundant=true implies a secondary region or readable replica.

How to eliminate wrong answers

Option A is wrong because zoneRedundant=true indicates intra-region zone redundancy, not active geo-replication to a secondary region; geo-replication is reflected by replicationRole and partner server settings, not the zoneRedundant flag. Option C is wrong because the output does not indicate the Hyperscale service tier; zone redundancy is available across multiple tiers (General Purpose, Business Critical, Hyperscale) and the properties shown do not identify the tier. Option D is wrong because a readable secondary replica in a different availability zone is not implied by zoneRedundant=true; zone redundancy replicates storage across zones for HA, not for read offloading, and replicationRole=Primary simply means this is the primary replica in a replication topology.

Practice this question →

52

MCQeasy

Your company runs a mission-critical Azure SQL Database in the East US region. To meet an RPO of 5 seconds and an RTO of 30 minutes in the event of a regional outage, which deployment option should you choose?

A.Failover groups with auto-failover policy

B.Zone-redundant configuration

C.Point-in-time restore

D.Active geo-replication with manual failover

AnswerA

Failover groups with an auto-failover policy replicate databases asynchronously to a secondary region, typically achieving an RPO under 5 seconds, and automatically redirect connections after an outage. This satisfies both the 5-second RPO and the 30-minute RTO, unlike geo-restore, which can take hours.

Why this answer

Failover groups with auto-failover policy provide automatic failover with an RPO of 5 seconds (default) and RTO of 30 minutes. Active geo-replication requires manual failover, which does not meet the RTO. Zone-redundant configuration only protects within a region.

Backup restore has much higher RPO/RTO.

Practice this question →

53

MCQeasy

Your company has an Azure SQL Database with a failover group configured to a secondary region. The primary region experiences a temporary network issue. The failover group is set to automatic failover with a grace period of 1 hour. What will happen?

A.Automatic failover will happen immediately.

B.You must manually initiate failover.

C.Automatic failover will start after 1 hour if the primary is still unreachable.

D.The secondary database will be deleted and re-created.

AnswerC

With automatic failover and a one-hour grace period, Azure waits that duration while the primary remains unreachable, then promotes the secondary. The grace period delays the switchover, so failover only begins once the hour elapses and the outage persists.

Why this answer

In an Azure SQL failover group with automatic failover and a grace period of 1 hour, the failover is not immediate. Azure waits for the grace period to elapse while the primary remains unreachable before initiating automatic failover to the secondary region. This prevents unnecessary failovers during brief network blips.

Exam trap

DP-300 often tests the grace period behavior in failover groups — candidates assume automatic failover is immediate, but the grace period delays it to prevent unnecessary failovers.

How to eliminate wrong answers

Option A is wrong because automatic failover is not immediate when a grace period is configured — the grace period exists specifically to delay failover and avoid false positives. Option B is wrong because the failover group is set to automatic failover, so manual initiation is not required; manual failover is only needed when automatic failover is disabled. Option D is wrong because failover does not delete or re-create the secondary database — it promotes the secondary to primary and the old primary becomes the new secondary once it recovers.

Practice this question →

54

Multi-Selectmedium

Which TWO of the following are benefits of using Azure SQL Database failover groups compared to active geo-replication? (Choose Two.)

Select 2 answers

A.Failover groups allow you to fail over multiple databases simultaneously.

B.Failover groups provide a read-write listener endpoint that remains unchanged after a failover.

C.Failover groups automatically fail over without any manual intervention.

D.Failover groups provide a readable secondary replica for read-only workloads.

E.Failover groups eliminate the need for geo-redundant storage.

AnswersA, B

Failover groups operate at the server level, grouping databases so a single failover operation switches all members together. Active geo-replication requires initiating failover per database individually, so this satisfies the stem's requirement for coordinated, simultaneous multi-database failover.

Why this answer

Option A is correct because a failover group is a container that groups several Azure SQL databases on a logical server, so a single failover operation moves all member databases together, whereas active geo-replication requires failing over each database individually. Option B is correct because failover groups expose read-write and read-only listener endpoints (e.g., <fg-name>.database.windows.net) that stay constant, so applications keep using the same connection string after a failover instead of updating the server name. Option C is not a distinguishing benefit: failover groups support automatic failover policies, but active geo-replication also allows automatic failover, so it is not unique to failover groups.

Option D is not correct as a differentiator because active geo-replication also provides readable secondary replicas for read-only workloads. Option E is incorrect because failover groups still rely on geo-replicated storage/backups; they do not remove the need for geo-redundant storage.

Exam trap

DP-300 often tests the specific advantages of failover groups over active geo-replication, and candidates may incorrectly assume automatic failover or readable secondaries are unique to failover groups.

Practice this question →

55

MCQhard

You have an Azure SQL Managed Instance named MI1 in the West Europe region. The instance hosts a mission-critical database that must be recoverable in a different region within 15 minutes of a regional outage. The solution must minimize data loss and administrative overhead. You need to implement a disaster recovery solution. What should you do?

A.Enable geo-redundant backup storage for MI1.

B.Create a transactional replication subscription to a SQL Server on an Azure VM in another region.

C.Configure an auto-failover group between MI1 and a secondary managed instance in another region.

D.Use Azure Site Recovery to replicate the managed instance to another region.

AnswerC

Auto-failover groups for Azure SQL Managed Instance provide automatic failover to a secondary instance in another region, with a recovery point objective (RPO) of seconds and recovery time objective (RTO) of minutes. They minimize data loss and administrative overhead by automating the failover process.

Why this answer

Auto-failover groups are the recommended disaster recovery feature for Azure SQL Managed Instance. They enable automatic failover to a secondary instance in another region, ensuring rapid recovery and minimal data loss with low administrative effort. Geo-redundant backups and replication methods do not provide the required RTO and automation.

Exam trap

The trap here is assuming that geo-redundant backups alone can meet a tight recovery time objective, when they actually require a restore operation that may exceed the allowed time.

Practice this question →

56

MCQmedium

Your company has an Azure SQL Database that uses a failover group with a secondary in a different region. You need to ensure that read-only queries are directed to the secondary database to offload the primary. What should you configure?

A.Add ApplicationIntent=ReadOnly to the connection string and use the failover group listener.

B.Use a Traffic Manager profile to route read traffic.

C.Enable read-scale for the database.

D.Configure a separate connection string pointing to the secondary server.

AnswerA

ApplicationIntent=ReadOnly in the connection string signals the intent to run read-only workloads; combined with the failover group listener, Azure SQL routes those sessions to the readable secondary. This offloads the primary while the listener abstracts endpoint changes during failover.

Why this answer

To direct read-only queries to the secondary database in a failover group, you must use the failover group listener and add 'ApplicationIntent=ReadOnly' to the connection string. The listener routes read-write connections to the primary and read-only connections to the secondary, based on the ApplicationIntent parameter. This is the built-in read-scale-out mechanism for failover groups.

Exam trap

DP-300 often tests the misconception that you can just connect to the secondary server directly or use Traffic Manager — the correct approach is the failover group listener with ApplicationIntent=ReadOnly, which candidates overlook.

How to eliminate wrong answers

Option B is wrong because Traffic Manager is a DNS-based load balancer and does not understand SQL connection intent; it cannot route read-only queries to the secondary. Option C is wrong because 'read-scale' is a feature of Azure SQL Database hyperscale and business critical tiers that uses replicas, but it is not the mechanism for failover group secondary routing. Option D is wrong because connecting directly to the secondary server bypasses the failover group listener and does not automatically handle failover; also, the secondary may not be readable unless you explicitly enable read access.

Practice this question →

57

Multi-Selecthard

You manage an Azure SQL Managed Instance that hosts a mission-critical database. The instance is in the East US 2 region. You need to configure a disaster recovery solution that meets the following requirements: (1) provide a readable secondary in a different Azure region, (2) support automatic failover, and (3) minimize administrative effort. Which two actions should you perform? (Choose two.)

Select 2 answers

A.Create a failover group and add the managed instance to it.

B.Create a geo-secondary using the Azure portal by selecting the managed instance and choosing 'Geo-Replication'.

C.Enable zone redundancy on the primary managed instance.

D.Deploy a secondary managed instance in a different region and add it to the failover group.

E.Configure active geo-replication for the managed instance.

AnswersA, D

A failover group for Azure SQL Managed Instance provides a read-write listener endpoint and supports automatic failover to a secondary instance in another region. It meets the requirement for a readable secondary and automatic failover. It also minimizes administrative effort because the failover group manages the replication and endpoint configuration, and you can initiate failover with a single action.

Why this answer

For Azure SQL Managed Instance, cross-region disaster recovery with a readable secondary and automatic failover is achieved by using failover groups. You must deploy a secondary managed instance in a different region and then add both instances to a failover group. Active geo-replication and zone redundancy do not meet the requirements for a cross-region readable secondary with automatic failover.

The failover group provides the listener endpoint and automates the failover process.

Exam trap

The trap here is confusing Azure SQL Database features with Azure SQL Managed Instance capabilities; active geo-replication and portal-based geo-replication are not available for managed instance, and zone redundancy only provides local high availability.

Practice this question →

58

MCQeasy

You are preparing a disaster recovery runbook. You plan to use the PowerShell command shown in the exhibit to restore a database to a different region. What must be true for this command to succeed?

A.The source database must have geo-redundant backup storage configured.

B.The source database must have point-in-time restore enabled.

C.The source database must be online at the time of restoration.

D.The target server must be in the same region as the source server.

AnswerA

Geo-restore to a different Azure region requires the source database's backup storage redundancy to be geo-redundant; locally redundant or zone-redundant backups exist only in the primary region, so no copy is available to restore elsewhere.

Why this answer

The Restore-AzSqlDatabase cmdlet with the -FromGeoBackup parameter requires the source database to have geo-redundant backup storage (also known as geo-redundant storage) enabled. This allows restoration from geographically replicated backups. Option B is incorrect because point-in-time restore is not required for a geo-restore; geo-restore uses the geo-redundant backup independently.

Option C is incorrect because the source database does not need to be online at the time of restoration; geo-backups are stored in Azure storage and are available even if the source database is offline. Option D is incorrect because the purpose of geo-restore is to restore to a different region; therefore, the target server can be in a different region than the source.

Practice this question →

59

Multi-Selectmedium

Which TWO of the following are benefits of using Azure SQL Database failover groups compared to active geo-replication alone?

Select 2 answers

A.Support for manual failover.

B.Failover of multiple databases in a single group.

C.Readable secondary replicas for read-scale workloads.

D.Automatic failover based on the grace period.

E.Synchronous data replication to the secondary.

AnswersB, D

Correct: Failover groups allow coordinated failover of multiple databases.

Why this answer

Failover groups extend active geo-replication by allowing you to manage failover for a group of databases as a single unit. This simplifies the failover process when you have multiple databases that must be failed over together to maintain application consistency. Option B is correct because failover groups support the coordinated failover of multiple databases, which active geo-replication alone does not.

Exam trap

The trap here is that candidates confuse the features of active geo-replication (like readable secondaries and manual failover) with the unique benefits of failover groups, which are specifically the ability to fail over multiple databases as a group and the automatic failover based on a grace period.

Practice this question →

60

Multi-Selectmedium

You manage an Azure SQL Managed Instance that hosts a business-critical database. The compliance team requires that the instance be recoverable in a different Azure region if the primary region becomes unavailable, and that the failover be initiated manually only by authorized administrators. You need to configure a disaster recovery solution. Which two actions should you perform? (Choose two.)

Select 2 answers

A.Configure the failover policy of the failover group to Manual.

B.Configure active geo-replication between the two managed instances.

C.Enable zone redundancy on the primary managed instance.

D.Set the failover group policy to Automatic.

E.Create an auto-failover group that includes the managed instance.

AnswersA, E

Setting the failover policy to Manual ensures that failover only occurs when an administrator explicitly triggers it, matching the compliance requirement. Automatic policy would fail over without human intervention. Manual policy still allows planned and forced failover commands, so authorized personnel retain control.

Why this answer

Auto-failover groups are the supported cross-region disaster recovery feature for Azure SQL Managed Instance, and they provide a listener endpoint. To meet the compliance requirement that failover be manually initiated, the failover policy must be set to Manual. Zone redundancy is intra-region, active geo-replication is not available for managed instances, and Automatic policy would remove the required human control.

Exam trap

The trap here is assuming active geo-replication works for Azure SQL Managed Instance, when only auto-failover groups are supported for cross-region replication.

Practice this question →

61

MCQeasy

You have an Azure SQL Database in the Business Critical tier with zone redundancy enabled. The database experiences a brief outage due to a zone failure. How does the platform automatically recover?

A.You must perform a manual failover to a secondary replica.

B.A replica in another availability zone is automatically promoted to primary.

C.The database is restored from the latest backup.

D.The database becomes read-only until the zone is restored.

AnswerB

Business Critical with zone redundancy maintains a synchronous replica in a separate availability zone. On zone failure, that replica is automatically promoted to primary, satisfying the zone-failure recovery requirement without manual intervention or data loss.

Why this answer

When zone redundancy is enabled in Business Critical, Azure SQL Database maintains replicas across multiple availability zones. If a zone fails, the platform automatically detects the failure and promotes a replica from a surviving zone to primary, typically within seconds to a minute, with no manual intervention. This is built-in HA, not disaster recovery.

Exam trap

DP-300 often tests the confusion between zone redundancy (automatic AZ failover, HA) and geo-replication/geo-restore (regional DR, manual or automatic with FOG) — the word 'zone' signals automatic local failover.

How to eliminate wrong answers

Option A is wrong because manual failover is not required — zone redundancy provides automatic failover. Option C is wrong because restoring from backup is a disaster recovery operation with significant RTO/RPO, not the automatic HA behavior for zone failure. Option D is wrong because the database does not become read-only; the platform promotes another replica to maintain read-write availability.

Practice this question →

62

MCQhard

You are a database administrator for a global e-commerce company. The company uses Azure SQL Database for its product catalog, which is a mission-critical OLTP workload. The database is currently deployed in the West US region using the Business Critical service tier with zone redundancy enabled. The database size is 200 GB and grows at 10 GB per month. The company has a disaster recovery requirement: in the event of a regional outage, the database must be failed over to a secondary region with an RPO of less than 5 seconds and an RTO of less than 1 minute. Additionally, the secondary database must be readable to support read-heavy reporting workloads. The solution must minimize additional compute costs. You need to recommend a configuration. Which option should you choose?

A.Configure active geo-replication to a secondary database in a paired region using Business Critical tier with a readable secondary.

B.Create a failover group within the same region using Business Critical tier with a readable secondary.

C.Add a second zone-redundant replica in the same region and configure a failover group.

D.Upgrade to Hyperscale tier with zone redundancy and configure a named replica in a secondary region.

AnswerA

Active geo-replication provides low RPO and a readable secondary, meeting all requirements.

Why this answer

Active geo-replication to a secondary database in a paired region using Business Critical tier with a readable secondary meets all requirements: it provides cross-region DR with an RPO of less than 5 seconds (synchronous replication within the primary region, asynchronous to secondary), RTO of less than 1 minute (failover is fast), and the secondary is readable for reporting. Zone redundancy within the primary region does not provide cross-region DR, so options B and C are incorrect. Hyperscale tier (option D) is more expensive and does not inherently provide cross-region DR with the required RPO; named replicas add cost.

Practice this question →

63

Multi-Selecthard

Which THREE components are required to configure a failover group for Azure SQL Database? (Choose three.)

Select 3 answers

A.Failover group listener.

B.At least one database on the primary server.

C.Secondary server.

D.Primary server.

E.An elastic pool.

AnswersB, C, D

Failover groups replicate databases, so at least one database must exist on the primary server before the group can be created. Without a database to replicate, there is nothing for the secondary server to receive.

Why this answer

Options B, C, and D are correct. A failover group requires a primary server, a secondary server, and at least one database on the primary server. Option A is incorrect because the failover group listener is automatically created and does not need to be separately configured.

Option E is incorrect because an elastic pool is optional; failover groups can contain individual databases or elastic pools.

Practice this question →

64

Multi-Selecteasy

Which TWO are benefits of using a failover group for Azure SQL Database? (Select two.)

Select 2 answers

A.Allows the secondary database to be readable for reporting

B.Enables transparent data encryption (TDE) across regions

C.Provides a single read/write listener endpoint for the primary database

D.Automatically balances read queries between primary and secondary

E.Supports synchronous replication between primary and secondary

AnswersA, C

A failover group replicates databases to a secondary server that can be opened read-only, letting reporting workloads query the secondary without impacting the primary. This satisfies the requirement for an offload reporting target while retaining failover capability.

Why this answer

Option A is correct because a failover group allows you to configure the secondary database as readable, enabling read-only workloads such as reporting to be offloaded to the secondary replica. Option C is correct because a failover group provides a read/write listener endpoint (e.g., <failover-group>.database.windows.net) that automatically redirects connections to the current primary after a failover, giving applications a stable connection string. Option B is not a benefit specific to failover groups; TDE is a database-level encryption feature that can be enabled independently and is not provided or extended across regions by a failover group.

Option D is incorrect because failover groups do not automatically load-balance read queries between primary and secondary; read-only routing must be configured and is not automatic balancing. Option E is incorrect because Azure SQL Database failover groups use asynchronous replication, not synchronous replication, between the primary and secondary servers.

Practice this question →

65

MCQeasy

You have an Azure SQL Database that uses the General Purpose service tier. The database is critical and you need to ensure that it remains available during a planned patching event that updates the underlying hardware. What does Azure SQL Database provide to maintain availability during such events?

A.The database is taken offline during patching and restored afterward.

B.You must manually fail over to a secondary database to avoid downtime.

C.Zone-redundant replicas that ensure zero downtime.

D.Automated failover to a built-in standby replica with minimal downtime.

AnswerD

The General Purpose tier uses remote storage with locally attached compute and maintains a built-in standby replica. During planned hardware patching, Azure performs automated failover to that standby, keeping the database online with minimal downtime, satisfying the availability requirement without manual intervention.

Why this answer

Azure SQL Database provides automated failover to a built-in standby replica with minimal downtime during planned patching events. This is part of the built-in high availability architecture, where the database runs on a primary replica and maintains a secondary replica. During patching, a failover occurs to the secondary, ensuring continuity.

Exam trap

The trap is thinking that zone redundancy is required for high availability during patching, when in fact the built-in standby replica handles it even without zone redundancy.

How to eliminate wrong answers

Option A is wrong because the database is not taken offline; Azure SQL Database is designed for high availability. Option B is wrong because manual failover is not required; the failover is automatic. Option C is wrong because zone-redundant replicas are an optional configuration for higher availability across availability zones, but even without them, the built-in standby replica provides failover during patching.

The question does not specify zone redundancy, and the General Purpose tier includes built-in high availability with a standby replica.

Practice this question →

66

MCQhard

You administer a SQL Managed Instance in the West Europe region. You need to create a disaster recovery replica in North Europe with automated failover. The replica must be readable and support backups. What should you configure?

A.Set up log shipping from West Europe to North Europe.

B.Configure active geo-replication between the instances.

C.Create a failover group, but note the secondary is not readable.

D.Create a failover group with the secondary instance in North Europe.

AnswerD

A failover group provides an auto-failover endpoint and a readable secondary, satisfying the automated failover and read-access requirements. The secondary instance in North Europe also supports backups, meeting the cross-region disaster recovery constraint. Geo-replication alone lacks the automatic failover that failover groups deliver.

Why this answer

SQL Managed Instance supports failover groups for automated failover between regions, and the secondary instance in a failover group is readable and supports backups. Option A is incorrect because log shipping is not supported for SQL Managed Instance. Option B is incorrect because active geo-replication is not supported for SQL Managed Instance; failover groups are the appropriate solution.

Option C is incorrect because the secondary instance in a failover group is readable and can be used for read-only workloads.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Ha Dr Environment questions.

Start 20-question session