DP-300 · topic practice

Plan and configure high availability and disaster recovery practice questions

Q: How should I use these Plan and configure high availability and disaster recovery practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Q: Can I practise just Plan and configure high availability and disaster recovery questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Plan and configure high availability and disaster recovery domain.

Practise Microsoft Azure Database Administrator Associate DP-300 Plan and configure high availability and disaster recovery practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

19 questionsDomain: Plan and configure high availability and disaster recovery

Practice 10 questions Browse domain →

What the exam tests

What to know about Plan and configure high availability and disaster recovery

Plan and configure high availability and disaster recovery questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common Plan and configure high availability and disaster recovery exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Plan and configure high availability and disaster recovery questions

19 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full Plan and configure high availability and disaster recovery explanation →

A company runs a critical Azure SQL Database in the West US region. To meet a Recovery Point Objective (RPO) of 5 seconds and a Recovery Time Objective (RTO) of 30 seconds during a regional outage, which deployment option should be used?

Trap 1: Use an Auto-Failover Group with a secondary in West US 2

Auto-failover groups have RTO of about 1 hour.

Trap 2: Enable geo-zone-redundant backup storage and perform point-in-time…

Restore from backup takes hours, not seconds.

Trap 3: Configure Active Geo-Replication with a readable secondary in East…

Geo-replication has RTO of minutes, not seconds.

Study all Plan and configure high availability and disaster recovery common traps →

A
Use an Auto-Failover Group with a secondary in West US 2
Why wrong: Auto-failover groups have RTO of about 1 hour.
B
Deploy the database in the Business Critical tier with zone-redundant configuration in West US
Zone-redundant Business Critical provides fast failover within seconds and RPO of 5 seconds.
C
Enable geo-zone-redundant backup storage and perform point-in-time restore
Why wrong: Restore from backup takes hours, not seconds.
D
Configure Active Geo-Replication with a readable secondary in East US
Why wrong: Geo-replication has RTO of minutes, not seconds.

Full breakdown with real-world context →

Question 2easymultiple choice

Read the full Plan and configure high availability and disaster recovery explanation →

A company has an Azure SQL Managed Instance in the East US region. They need to implement disaster recovery with automatic failover to a paired region. The solution must minimize data loss to less than 5 seconds. Which feature should they use?

Trap 1: Active Geo-Replication with a secondary in East US 2

Active Geo-Replication is not supported for SQL Managed Instance.

Trap 2: Enable geo-redundant backup storage and restore to West US

Geo-restore has RPO of hours, not seconds.

Trap 3: Set up a Failover Group with manual failover to a secondary in West…

Manual failover is not automatic.

Study all Plan and configure high availability and disaster recovery common traps →

A
Active Geo-Replication with a secondary in East US 2
Why wrong: Active Geo-Replication is not supported for SQL Managed Instance.
B
Enable geo-redundant backup storage and restore to West US
Why wrong: Geo-restore has RPO of hours, not seconds.
C
Configure an Auto-Failover Group with a secondary instance in West US
Auto-failover groups for managed instance provide automatic failover and RPO of 5 seconds.
D
Set up a Failover Group with manual failover to a secondary in West US
Why wrong: Manual failover is not automatic.

Full breakdown with real-world context →

Question 3hardmultiple choice

Read the full Plan and configure high availability and disaster recovery explanation →

A company runs SQL Server 2019 on Azure Virtual Machines in an availability set. They need to achieve high availability for a critical database with automatic failover and no shared storage. The solution must minimize downtime during planned maintenance. What should they implement?

Trap 1: Configure Log Shipping to a secondary VM

Log shipping requires manual failover, not automatic.

Trap 2: Deploy a Failover Cluster Instance using Azure Shared Disks

Requires shared storage, which is not desired.

Trap 3: Use Database Mirroring with automatic failover

Database mirroring is deprecated and not recommended.

Study all Plan and configure high availability and disaster recovery common traps →

A
Configure Log Shipping to a secondary VM
Why wrong: Log shipping requires manual failover, not automatic.
B
Deploy a Failover Cluster Instance using Azure Shared Disks
Why wrong: Requires shared storage, which is not desired.
C
Create an Always On Availability Group with an availability group listener
Always On AG provides automatic failover and no shared storage.
D
Use Database Mirroring with automatic failover
Why wrong: Database mirroring is deprecated and not recommended.

Full breakdown with real-world context →

Question 4mediummultiple choice

Read the full Plan and configure high availability and disaster recovery explanation →

A company uses Azure SQL Database Hyperscale tier for a large database. They need to perform a disaster recovery drill by failing over to a secondary region with minimal data loss. The secondary is in a paired region and is readable. Which approach should they use?

Trap 1: Restore a geo-redundant backup to the secondary region

Restoring a backup takes too long for a drill.

Trap 2: Configure Active Geo-Replication to the secondary region

Active Geo-Replication is not supported for Hyperscale.

Trap 3: Create a named replica in the secondary region and fail over…

Named replicas are for read scale-out, not disaster recovery.

Study all Plan and configure high availability and disaster recovery common traps →

A
Restore a geo-redundant backup to the secondary region
Why wrong: Restoring a backup takes too long for a drill.
B
Configure Active Geo-Replication to the secondary region
Why wrong: Active Geo-Replication is not supported for Hyperscale.
C
Create a named replica in the secondary region and fail over manually
Why wrong: Named replicas are for read scale-out, not disaster recovery.
D
Use an Auto-Failover Group with the secondary in the paired region
Auto-failover groups support Hyperscale and allow failover with minimal data loss.

Full breakdown with real-world context →

Question 5easymulti select

Read the full Plan and configure high availability and disaster recovery explanation →

Which TWO options are required to configure a SQL Server Always On Availability Group on Azure Virtual Machines?

Trap 1: Azure Files share for witness

Optional, not required.

Trap 2: Azure SQL Database

Not relevant for SQL Server on VMs.

Trap 3: VPN gateway between regions

Not required.

Study all Plan and configure high availability and disaster recovery common traps →

A
Internal Load Balancer
Required for the listener.
B
Azure Files share for witness
Why wrong: Optional, not required.
C
Windows Server Failover Cluster
Required for availability group.
D
Azure SQL Database
Why wrong: Not relevant for SQL Server on VMs.
E
VPN gateway between regions
Why wrong: Not required.

Full breakdown with real-world context →

Question 6mediummulti select

Read the full Plan and configure high availability and disaster recovery explanation →

Which THREE factors should be considered when choosing between Azure SQL Database active geo-replication and auto-failover groups for disaster recovery?

Trap 1: Recovery Point Objective (RPO) of 1 second

Both have RPO of 5 seconds.

Trap 2: Support for SQL Server Authentication

Both support SQL Server Authentication.

Study all Plan and configure high availability and disaster recovery common traps →

A
Automatic failover capability
Auto-failover groups provide automatic failover; active geo-replication does not.
B
Recovery Point Objective (RPO) of 1 second
Why wrong: Both have RPO of 5 seconds.
C
Number of readable secondary replicas required
Active geo-replication supports up to 4, auto-failover groups support only 1.
D
Support for SQL Server Authentication
Why wrong: Both support SQL Server Authentication.
E
Granular control over individual database failover
Active geo-replication allows per-database failover; auto-failover groups fail over all databases in the group.

Full breakdown with real-world context →

Question 7hardmultiple choice

Read the full Plan and configure high availability and disaster recovery explanation →

You are troubleshooting an Always On Availability Group named AG1. The exhibit shows the current state. The primary replica shows PENDING_FAILOVER. The secondary replica is DISCONNECTED with error 35202. What is the most likely cause of this issue?

Exhibit

Refer to the exhibit.

```
-- Current state of the availability group
SELECT ag.name AS ag_name, 
       replica_server_name, 
       role_desc, 
       operational_state_desc, 
       connected_state_desc, 
       synchronization_health_desc, 
       last_connect_error_number, 
       last_connect_error_time
FROM sys.dm_hadr_availability_replica_states rs
JOIN sys.availability_groups ag ON rs.group_id = ag.group_id
WHERE ag.name = 'AG1';
```

Output:
ag_name | replica_server_name | role_desc | operational_state_desc | connected_state_desc | synchronization_health_desc | last_connect_error_number | last_connect_error_time
AG1     | SQLVM-Primary        | PRIMARY   | PENDING_FAILOVER       | CONNECTED            | HEALTHY                     | 0                         | NULL
AG1     | SQLVM-Secondary      | SECONDARY | ONLINE                 | DISCONNECTED         | NOT_HEALTHY                 | 35202                     | 2024-03-15 10:30:00.000

Trap 1: The availability group listener is not configured correctly

Listener issues do not cause replica disconnection.

Trap 2: The primary instance encountered a critical error and failed over…

PENDING_FAILOVER indicates a manual or forced failover, not automatic.

Trap 3: The cluster has lost quorum

Quorum loss would show different symptoms; both replicas would be affected.

Study all Plan and configure high availability and disaster recovery common traps →

A
Network connectivity between the replicas is blocked on port 5022
Error 35202 often relates to connectivity issues on the mirroring endpoint port.
B
The availability group listener is not configured correctly
Why wrong: Listener issues do not cause replica disconnection.
C
The primary instance encountered a critical error and failed over automatically
Why wrong: PENDING_FAILOVER indicates a manual or forced failover, not automatic.
D
The cluster has lost quorum
Why wrong: Quorum loss would show different symptoms; both replicas would be affected.

Full breakdown with real-world context →

Question 8hardmultiple choice

Review the full routing breakdown →

You are the database administrator for a global e-commerce company. They run a mission-critical application on Azure SQL Database in the Business Critical tier. The database is 2 TB and experiences high write throughput. The current setup uses an auto-failover group with a secondary in the same region (West US) for high availability. The client application uses the auto-failover group listener with ReadScale=1 to route read-only queries to the secondary. Recently, during a regional outage that affected West US, the failover to the secondary succeeded, but the application experienced significant performance degradation and many timeouts for read operations. Investigation reveals that the secondary replica was overwhelmed with read traffic after failover. The business requires an RTO of 30 seconds and RPO of 5 seconds. The application must be able to handle read-heavy workloads even during a failover. You need to recommend a solution to improve read scalability and disaster recovery without changing the application code. What should you do?

Trap 1: Add a second secondary replica to the auto-failover group in the…

During a regional outage, all replicas in the same region are affected.

Trap 2: Increase the service objective of the secondary replica in the…

Scaling up does not add additional read replicas; the secondary still has limited capacity.

Trap 3: Change the database to the Hyperscale tier, which supports multiple…

Hyperscale does not support auto-failover groups with the same RTO/RPO and changes the architecture.

Study all Plan and configure high availability and disaster recovery common traps →

A
Add a second secondary replica to the auto-failover group in the same region.
Why wrong: During a regional outage, all replicas in the same region are affected.
B
Deploy an additional readable secondary replica in the Business Critical tier in a different Azure region and configure active geo-replication to that region. Update the connection string to use the geo-secondary for reads.
This provides additional read capacity and disaster recovery.
C
Increase the service objective of the secondary replica in the auto-failover group to a higher DTU or vCore to handle the read load.
Why wrong: Scaling up does not add additional read replicas; the secondary still has limited capacity.
D
Change the database to the Hyperscale tier, which supports multiple readable replicas and automatic failover.
Why wrong: Hyperscale does not support auto-failover groups with the same RTO/RPO and changes the architecture.

Full breakdown with real-world context →

Question 9easymulti select

Read the full Plan and configure high availability and disaster recovery explanation →

Which TWO configurations are required to enable automatic failover for an Azure SQL Database configured with active geo-replication?

Trap 1: Enable read-scale out on the secondary database.

Read-scale out is optional and not required for automatic failover.

Trap 2: Set the secondary database to have the same service tier as the…

Service tiers can differ; not a requirement for automatic failover.

Trap 3: Configure zone redundancy on the primary database.

Zone redundancy provides HA within a region, not for geo-failover.

Study all Plan and configure high availability and disaster recovery common traps →

A
Enable read-scale out on the secondary database.
Why wrong: Read-scale out is optional and not required for automatic failover.
B
Configure a failover group that includes the primary and secondary databases.
Failover group is required to orchestrate automatic failover.
C
Set the secondary database to have the same service tier as the primary.
Why wrong: Service tiers can differ; not a requirement for automatic failover.
D
Configure zone redundancy on the primary database.
Why wrong: Zone redundancy provides HA within a region, not for geo-failover.
E
Ensure the secondary server is in a different Azure region than the primary.
Geo-replication requires a secondary in a different region for disaster recovery.

Full breakdown with real-world context →

Question 10mediummultiple choice

Read the full Plan and configure high availability and disaster recovery explanation →

You are the database administrator for a global e-commerce company. The company runs its production SQL Server on an Azure Virtual Machine (IaaS) in the West US region. The database is mission-critical and requires a Recovery Point Objective (RPO) of 5 minutes and a Recovery Time Objective (RTO) of 30 minutes in the event of a regional disaster. The VM uses premium SSDs and is backed up daily to a Recovery Services vault with geo-redundant storage. The current backup policy takes full backups weekly, differential backups daily, and transaction log backups every 15 minutes. The VM is in an availability set for high availability within the region. During a recent regional outage simulation, the database was unavailable for 4 hours because the backups needed to be restored to a different region, and the restore process took longer than expected. You need to recommend a solution to meet the RPO and RTO requirements. What should you do?

Trap 1: Implement Azure Site Recovery to replicate the VM to a secondary…

Azure Site Recovery can replicate VMs, but RPO may be up to a few minutes and RTO can be longer due to VM boot time and application recovery. It might not guarantee RTO of 30 minutes.

Trap 2: Set up log shipping to a secondary SQL Server in a different region…

Log shipping can meet RPO with frequent log backups, but manual failover increases RTO beyond 30 minutes.

Trap 3: Increase the frequency of transaction log backups to every 5…

More frequent backups reduce RPO but restore time remains long, failing RTO.

Study all Plan and configure high availability and disaster recovery common traps →

A
Implement Azure Site Recovery to replicate the VM to a secondary region.
Why wrong: Azure Site Recovery can replicate VMs, but RPO may be up to a few minutes and RTO can be longer due to VM boot time and application recovery. It might not guarantee RTO of 30 minutes.
B
Set up log shipping to a secondary SQL Server in a different region and perform manual failover.
Why wrong: Log shipping can meet RPO with frequent log backups, but manual failover increases RTO beyond 30 minutes.
C
Configure a SQL Server Always On availability group with a synchronous-commit replica in a secondary Azure region.
Synchronous replication provides RPO of 0 (within 5 minutes) and automatic failover can achieve RTO in minutes.
D
Increase the frequency of transaction log backups to every 5 minutes and use geo-restore.
Why wrong: More frequent backups reduce RPO but restore time remains long, failing RTO.

Full breakdown with real-world context →

Question 11mediumdrag order

Read the full Plan and configure high availability and disaster recovery explanation →

Drag and drop the steps to configure automatic tuning for an Azure SQL Database in the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 12mediumdrag order

Read the full Plan and configure high availability and disaster recovery explanation →

Drag and drop the steps to configure a SQL Server Agent job in Azure SQL Managed Instance to run a maintenance task in the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 13mediummatching

Read the full Plan and configure high availability and disaster recovery explanation →

Match each Azure SQL Database security feature to its purpose.

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

Concepts

Matches

Encrypts data at rest

Encrypts sensitive data in transit and at rest

Limits exposure of sensitive data by masking it to non-privileged users

Restricts access to rows based on user characteristics

Question 14mediummatching

Read the full Plan and configure high availability and disaster recovery explanation →

Match each Azure SQL Database error code to its meaning.

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

Concepts

Matches

Service is busy; retry the request later

Database is not currently available

Cannot open server '%.*ls' requested by the login

Question 15hardmultiple choice

Read the full Plan and configure high availability and disaster recovery explanation →

Refer to the exhibit. An administrator creates a geo-replica for SalesDB. After 30 minutes, the replication state remains SEEDING. What is the most likely cause?

Network Topology

Trap 1: The secondary server sqlsrv2 is in a different region than the…

Geo-replication across regions is supported; this is not the cause.

Trap 2: The recovery model is set to Full instead of Simple.

Full recovery model is required for geo-replication; this is correct.

Trap 3: The secondary database is being used as a read-only replica.

Read-only replica status does not prevent seeding.

Study all Plan and configure high availability and disaster recovery common traps →

A
The secondary server sqlsrv2 is in a different region than the primary.
Why wrong: Geo-replication across regions is supported; this is not the cause.
B
The recovery model is set to Full instead of Simple.
Why wrong: Full recovery model is required for geo-replication; this is correct.
C
The primary database SalesDB is not zone-redundant.
Zone redundancy must be enabled on the primary database for geo-replication to seed successfully.
D
The secondary database is being used as a read-only replica.
Why wrong: Read-only replica status does not prevent seeding.

Full breakdown with real-world context →

Question 16mediummultiple choice

Read the full Plan and configure high availability and disaster recovery explanation →

Refer to the exhibit. An administrator wants to ensure that during a regional outage, the failover group automatically fails over without data loss if possible. What is the current configuration gap?

Network Topology

Trap 1: The failover policy is set to Automatic, but the grace period is…

Grace period is acceptable; the issue is backup redundancy.

Trap 2: The secondary managed instance mi2 is in the same region as the…

Secondary is in westus, primary in eastus; different regions.

Trap 3: The read-only endpoint failover policy is Disabled, which prevents…

Read-only failover policy is not required for automatic failover.

Study all Plan and configure high availability and disaster recovery common traps →

A
The failover policy is set to Automatic, but the grace period is too long.
Why wrong: Grace period is acceptable; the issue is backup redundancy.
B
The backup storage redundancy is Local, which does not provide geo-redundancy for backups.
Geo-redundant backup storage (GRS) is needed to protect backups across regions.
C
The secondary managed instance mi2 is in the same region as the primary.
Why wrong: Secondary is in westus, primary in eastus; different regions.
D
The read-only endpoint failover policy is Disabled, which prevents read-only traffic after failover.
Why wrong: Read-only failover policy is not required for automatic failover.

Full breakdown with real-world context →

Question 17hardmultiple choice

Read the full Plan and configure high availability and disaster recovery explanation →

Refer to the exhibit. An administrator tries to restore the database OrdersDB to a point in time 2025-03-14 10:00 UTC and receives error 406. What is the most likely reason?

Exhibit

Error log excerpt:
2025-03-15 14:23:45.67 Error: 406, Severity: 16, State: 0.
The database 'OrdersDB' has an automated backup frequency of 12 hours and a point-in-time restore (PITR) retention period of 7 days.
The long-term retention (LTR) policy is configured as:
- Weekly: Sunday 02:00, retention 4 weeks
- Monthly: First Sunday 02:00, retention 12 months
- Yearly: First Sunday of March 02:00, retention 3 years

Current time: 2025-03-15 14:30 (Saturday)
Last successful backup: 2025-03-15 02:00

Attempted restore to 2025-03-14 10:00 UTC failed with error 406.

Trap 1: The database is currently in a geo-replication secondary role.

No indication of geo-replication in exhibit.

Trap 2: The long-term retention policy interferes with point-in-time…

LTR does not affect PITR.

Trap 3: The requested restore point is outside the 7-day retention period.

2025-03-14 is within 7 days from 2025-03-15.

Study all Plan and configure high availability and disaster recovery common traps →

A
The database is currently in a geo-replication secondary role.
Why wrong: No indication of geo-replication in exhibit.
B
The long-term retention policy interferes with point-in-time restore.
Why wrong: LTR does not affect PITR.
C
The requested restore point is outside the 7-day retention period.
Why wrong: 2025-03-14 is within 7 days from 2025-03-15.
D
The automated backup frequency is 12 hours, so point-in-time restore is not supported.
With 12-hour backup frequency, only full/differential backups are taken; no transaction logs are available for PITR.

Full breakdown with real-world context →

Question 18hardmultiple choice

Read the full Plan and configure high availability and disaster recovery explanation →

Refer to the exhibit. After a brief outage, the availability group recovered. However, SQL2 shows NOT_HEALTHY and DISCONNECTED. What is the most likely cause?

Exhibit

Availability group configuration:
AG1 (Synchronous commit)
- Primary replica: SQL1 (automatic failover)
- Secondary replica: SQL2 (automatic failover, readable secondary)
- Secondary replica: SQL3 (synchronous commit, manual failover, readable secondary)

Listener: listener1, port 1433

Error log on SQL1:
2025-03-15 15:00:00.00 spid31s     The availability group 'AG1' is being restarted due to a failure. Error: 35201. A connection timeout has occurred.
2025-03-15 15:00:05.00 spid31s     The local availability replica of availability group 'AG1' has transitioned from resolving role to primary role.
2025-03-15 15:00:10.00 spid31s     The availability group 'AG1' is online.

Query on SQL1:
SELECT replica_server_name, role_desc, synchronization_health_desc, connected_state_desc FROM sys.dm_hadr_availability_replica_states
WHERE group_id = '...'

Results:
SQL1 | PRIMARY | HEALTHY | CONNECTED
SQL2 | SECONDARY | NOT_HEALTHY | DISCONNECTED
SQL3 | SECONDARY | HEALTHY | CONNECTED

Trap 1: The automatic failover policy requires a quorum that is not met.

Quorum issues would affect all replicas, not just SQL2.

Trap 2: The listener is not configured correctly for SQL2.

Listener configuration does not affect replica synchronization.

Trap 3: The secondary replica SQL2 has an incompatible database version.

Version incompatibility would prevent the replica from joining, but the error indicates a connection timeout.

Study all Plan and configure high availability and disaster recovery common traps →

A
The automatic failover policy requires a quorum that is not met.
Why wrong: Quorum issues would affect all replicas, not just SQL2.
B
The listener is not configured correctly for SQL2.
Why wrong: Listener configuration does not affect replica synchronization.
C
The secondary replica SQL2 has an incompatible database version.
Why wrong: Version incompatibility would prevent the replica from joining, but the error indicates a connection timeout.
D
The network connection between SQL1 and SQL2 is still down after the outage.
The connection timeout error and the DISCONNECTED state suggest network issues.

Full breakdown with real-world context →

Question 19mediummultiple choice

Read the full Plan and configure high availability and disaster recovery explanation →

Refer to the exhibit. An administrator wants to restore the primary database SalesDB to a point in time 2025-03-15T09:00:00Z. What is the impact on the geo-replication?

Network Topology

Trap 1: The geo-replication will continue seamlessly after the restore.

Geo-replication is disrupted when the primary database is restored to a different point.

Trap 2: The restore will fail because the database is in a geo-replication…

Restore is allowed but will break replication.

Trap 3: The secondary database will automatically be restored to the same…

The secondary is not automatically restored.

Study all Plan and configure high availability and disaster recovery common traps →

A
The geo-replication will continue seamlessly after the restore.
Why wrong: Geo-replication is disrupted when the primary database is restored to a different point.
B
The restore will fail because the database is in a geo-replication relationship.
Why wrong: Restore is allowed but will break replication.
C
The geo-replication will be terminated, and the secondary will become a standalone database.
Restoring the primary to a different point in time breaks the replication link.
D
The secondary database will automatically be restored to the same point in time.
Why wrong: The secondary is not automatically restored.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Plan and configure high availability and disaster recovery sessions

Start a Plan and configure high availability and disaster recovery only practice session

Every question in these sessions is drawn from the Plan and configure high availability and disaster recovery domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Plan and configure high availability and disaster recovery questions →Mixed DP-300 session

Frequently asked questions

What does the DP-300 exam test about Plan and configure high availability and disaster recovery?: Plan and configure high availability and disaster recovery questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Plan and configure high availability and disaster recovery questions in a focused session?: Yes — the session launcher on this page draws every question from the Plan and configure high availability and disaster recovery domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other DP-300 topics?: Use the topic links above to move to related areas, or go back to the DP-300 question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the DP-300 exam covers. They are not copied from any real exam or dump site.

Plan and configure high availability and disaster recovery only

10 questions 20 questions 30 questions 50 questions

Mixed DP-300 session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All DP-300 questions Plan and configure high availability and disaster recovery domain overview DP-300 exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Plan and configure high availability and disaster recovery practice questions

What to know about Plan and configure high availability and disaster recovery

Common Plan and configure high availability and disaster recovery exam traps

Plan and configure high availability and disaster recovery questions

A company runs a critical Azure SQL Database in the West US region. To meet a Recovery Point Objective (RPO) of 5 seconds and a Recovery Time Objective (RTO) of 30 seconds during a regional outage, which deployment option should be used?

A company has an Azure SQL Managed Instance in the East US region. They need to implement disaster recovery with automatic failover to a paired region. The solution must minimize data loss to less than 5 seconds. Which feature should they use?

A company runs SQL Server 2019 on Azure Virtual Machines in an availability set. They need to achieve high availability for a critical database with automatic failover and no shared storage. The solution must minimize downtime during planned maintenance. What should they implement?

A company uses Azure SQL Database Hyperscale tier for a large database. They need to perform a disaster recovery drill by failing over to a secondary region with minimal data loss. The secondary is in a paired region and is readable. Which approach should they use?

Which TWO options are required to configure a SQL Server Always On Availability Group on Azure Virtual Machines?

Which THREE factors should be considered when choosing between Azure SQL Database active geo-replication and auto-failover groups for disaster recovery?

You are troubleshooting an Always On Availability Group named AG1. The exhibit shows the current state. The primary replica shows PENDING_FAILOVER. The secondary replica is DISCONNECTED with error 35202. What is the most likely cause of this issue?

Exhibit

Which TWO configurations are required to enable automatic failover for an Azure SQL Database configured with active geo-replication?

Drag and drop the steps to configure automatic tuning for an Azure SQL Database in the correct order.

Drag and drop the steps to configure a SQL Server Agent job in Azure SQL Managed Instance to run a maintenance task in the correct order.

Match each Azure SQL Database security feature to its purpose.

Match each Azure SQL Database error code to its meaning.

Refer to the exhibit. An administrator creates a geo-replica for SalesDB. After 30 minutes, the replication state remains SEEDING. What is the most likely cause?

Refer to the exhibit. An administrator wants to ensure that during a regional outage, the failover group automatically fails over without data loss if possible. What is the current configuration gap?

Refer to the exhibit. An administrator tries to restore the database OrdersDB to a point in time 2025-03-14 10:00 UTC and receives error 406. What is the most likely reason?

Exhibit

Refer to the exhibit. After a brief outage, the availability group recovered. However, SQL2 shows NOT_HEALTHY and DISCONNECTED. What is the most likely cause?

Exhibit

Refer to the exhibit. An administrator wants to restore the primary database SalesDB to a point in time 2025-03-15T09:00:00Z. What is the impact on the geo-replication?

Track your progress over time

Start a Plan and configure high availability and disaster recovery only practice session

Related DP-300 topic practice pages

Plan and configure a high availability and disaster recovery environment practice questions

Plan and implement data platform resources practice questions

Monitor, configure, and optimize database resources practice questions

Configure and manage automation of tasks practice questions