DP-300 Practice Test 44 — 15 Questions

Question 1

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.)

Accepted Answer

Secondary database in a paired region with data synchronization. Option B is correct because the failover group listener provides a constant connection endpoint. Option D is correct because the failover group orchestrates replication and failover. Option E is correct because the secondary database must be seeded and synchronized. Option A is wrong because geo-redundant backup is not used during failover. Option C is wrong because Traffic Manager is not needed when using failover groups.

Answer

Geo-redundant backup storage

Answer

Azure Traffic Manager with priority routing

Question 2

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?

Accepted Answer

Create an auto-failover group with a secondary server in a different region.. Option C is correct because auto-failover groups allow failover to a secondary region with minimal data loss when using synchronous replication. Option A is wrong because read scale-out does not provide DR. Option B is wrong because zone redundancy provides availability within a region, not cross-region. Option D is wrong because backup redundancy does not provide failover.

Answer

Configure zone-redundant replicas in the same region.

Answer

Enable read scale-out on the database.

Answer

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

Question 3

You are using Azure SQL Managed Instance with auto-failover groups. The primary region is East US, secondary is West US. The primary region experiences a full outage. How does the failover group behave?

Accepted Answer

The failover group automatically fails over to West US and the read-write endpoint now points to West US.. Option D is correct because auto-failover groups automatically fail over to the secondary region with automatic read-write endpoint switch. Option A is incorrect because failover is automatic if the grace period is exceeded. Option B is incorrect because automatic failover does not require manual initiation. Option C is incorrect because read-only listeners are also updated automatically.

Answer

You must manually initiate failover via the portal.

Answer

The read-only listener continues to point to West US.

Answer

The failover group remains in primary region and does not fail over.

Question 4

A manufacturing company uses Azure SQL Database Hyperscale tier for its IoT telemetry data. The database is in West Europe and must be readable in East US for reporting with a maximum lag of 10 seconds. You configure a failover group with East US as the secondary region. After setup, reporting queries in East US show data that is 5 minutes old. What is the most likely cause?

Accepted Answer

The secondary database is configured with 'Geo' secondary type; you need to set it to 'Readable' to minimize lag. Option B is correct because by default, failover groups use asynchronous replication with a secondary type 'Geo' which may have higher lag. To achieve low lag, you must enable 'Configure secondary type' to 'Readable' (or 'Named' secondary in some configurations) which ensures near-synchronous replication, though still asynchronous. Option A is incorrect because the secondary is readable by default. Option C is not a standard setting. Option D is unrelated.

Answer

The failover group has 'Read/Write failover policy' set to 'Automatic' causing the lag

Answer

The secondary database is not readable; it is only for failover

Answer

The replication mode is set to 'Async' and should be changed to 'Sync'

Question 5

After running the above Azure CLI command, you notice that the secondary database is not readable. What is the most likely reason?

Accepted Answer

The '--secondary-type' parameter is set to 'Geo' instead of 'Readable'. Option A is correct. The '--secondary-type Geo' parameter sets the secondary to 'Geo' type, which is not readable. To make it readable, you must specify '--secondary-type Readable' (or 'Named'). Option B is incorrect because the capacity is for the secondary, but it does not affect readability. Option C is incorrect because Gen5 is a valid generation. Option D is incorrect because geo-replication does not support auto-failover; that's failover groups.

Answer

Geo-replication does not support readable secondaries by default

Answer

The secondary database capacity is set to 2 DTUs, which is too low

Answer

The hardware generation is Gen5, which does not support readable secondaries

Question 6

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?

Accepted Answer

The outage duration is less than the grace period for data loss.. Option D is correct because the grace period for data loss is set to 1 hour (3600 seconds); after 30 minutes, the grace period has not expired, so automatic failover is not triggered. Option A is wrong because the outage duration is less than the grace period. Option B is wrong because the grace period is designed to allow time for the outage to resolve. Option C is wrong because the issue is not about configuration but about timing.

Answer

The failover policy is set to manual.

Answer

The grace period for data loss is too short.

Answer

The secondary region is also experiencing an outage.

Question 7

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?

Accepted Answer

Create a failover group and configure the secondary instance to allow read-only connections.. Option C is correct because failover groups support readable secondary by default, and you can configure the secondary to be used for read-only queries by setting the connection string with ApplicationIntent=ReadOnly. Option A (zone redundancy) is not for geo-DR. Option B (active geo-replication) is not supported for managed instances. Option D (log shipping) is not built-in.

Answer

Enable zone redundancy on the primary and secondary instances.

Answer

Configure log shipping between the primary and secondary instances.

Answer

Use active geo-replication instead of a failover group.

Question 8

Your company has a SQL Server on Azure VM running a critical database. The VM is in a single availability set. You need to achieve a Recovery Point Objective (RPO) of 5 minutes and a Recovery Time Objective (RTO) of 15 minutes in case of an Azure region failure. What should you implement?

Accepted Answer

Configure Azure Site Recovery to replicate the VM to a secondary region.. Option A is correct because Azure Site Recovery can replicate the VM to another region and provide the required RPO and RTO. Option B is wrong because Always On Availability Groups on Azure VMs require at least two VMs and a witness, and may not achieve 5-minute RPO without synchronous commit (which adds latency). Option C is wrong because Azure Backup has typical RPO of 24 hours for daily backups. Option D is wrong because geo-redundant storage does not provide application-consistent recovery.

Answer

Configure SQL Server Always On Availability Groups with synchronous commit to a secondary VM in another region.

Answer

Use Azure Backup with daily backups and geo-restore.

Answer

Store database files on geo-redundant storage (GRS) and enable auto-failover.

Question 9

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?

Accepted Answer

Create an auto-failover group with a secondary replica in West US.. Option C is correct because SQL Managed Instance supports automatic failover groups with a readable secondary in a paired region. Option A is wrong because geo-restore takes up to 12 hours. Option B is wrong because log shipping is not supported for Managed Instance. Option D is wrong because Always On availability groups require manual failover configuration.

Answer

Configure log shipping to a secondary instance in West US.

Answer

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

Answer

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

Question 10

You have a SQL Server on Azure VM that is part of a failover cluster instance (FCI). The cluster nodes are in an availability set. You need to ensure that the database can tolerate a complete Azure region failure. What should you add to the current architecture?

Accepted Answer

Deploy a second FCI in a different Azure region and configure SQL Server log shipping or availability group between the FCIs.. Option A is correct because adding a second FCI in another region and configuring asynchronous replication between them provides cross-region DR. Option B is wrong because adding more nodes in the same region does not protect against region failure. Option C is wrong because geo-redundant backup does not provide continuous replication. Option D is wrong because active geo-replication is not supported for SQL Server on Azure VM.

Answer

Add another node to the existing FCI in a different availability zone.

Answer

Configure geo-redundant backup storage for the SQL Server VMs.

Answer

Create an Azure SQL Database with active geo-replication and migrate the database.

Question 11

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?

Accepted Answer

7 days. Option C is correct because point-in-time restore retention can be set from 1 to 35 days. To restore to any point within 7 days, you need at least 7 days retention. Option A (1 day) is insufficient. Option B (3 days) is also insufficient. Option D (14 days) is more than needed.

Answer

1 day

Answer

14 days

Answer

3 days

Question 12

You are designing a disaster recovery plan for an Azure SQL Database that supports an e-commerce application. The application requires an RPO of 15 seconds and an RTO of 1 hour during a regional outage. Which solution should you recommend?

Accepted Answer

Deploy active geo-replication to a secondary region and automate failover. Option C is correct because active geo-replication allows you to create a readable secondary in another region with an RPO of 5 seconds and manual failover, which can meet the RTO if automated via scripts. Failover groups have a default RPO of 5 seconds but an RTO of 1 hour; however, active geo-replication with a manual failover script can achieve the required RTO. Zone redundancy does not protect against regional outage. Backup restore has higher RPO.

Answer

Create a failover group with automatic failover policy

Answer

Use long-term backup retention and restore in another region

Answer

Configure zone-redundant availability for the database

Question 13

Your company has a policy that requires all Azure SQL Databases to be recoverable to a point in time within the last 5 minutes in the event of a user error. What should you configure?

Accepted Answer

Configure point-in-time restore (PITR) with a retention period of at least 5 minutes. Option B is correct because point-in-time restore (PITR) can restore a database to any point within the retention period, which for most tiers is up to 35 days. The default retention is 7 days, but you can configure it to allow recovery to 5 minutes ago. Option A is for long-term retention. Option C is for regional DR. Option D is for availability within a region.

Answer

Enable zone-redundant configuration

Answer

Set up active geo-replication to a secondary region

Answer

Enable long-term backup retention (LTR)

Question 14

You need to create a disaster recovery plan for an Azure SQL Database that has an RPO of 1 hour and an RTO of 12 hours. Which solution should you use?

Accepted Answer

Geo-restore of automated backups.. Option B is correct because geo-restore of automated backups can achieve RPO of 1 hour (backup frequency) and RTO of 12 hours (restore time). Option A is wrong because active geo-replication has lower RPO/RTO. Option C is wrong because failover groups have lower RTO. Option D is wrong because zone-redundancy does not protect against regional failure.

Answer

Failover group with automatic failover.

Answer

Active geo-replication.

Answer

Zone-redundant configuration.

Question 15

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?

Accepted Answer

Initiate a planned failover from the primary to the secondary.. Option B is correct because a planned failover (with data synchronization) ensures minimal data loss by syncing data before switching. Option A is incorrect because an unplanned failover may lose transactions not yet replicated. Option C is incorrect because you need to failover, not delete the secondary. Option D is incorrect because creating a new secondary does not failover.

Answer

Initiate an unplanned failover from the primary to the secondary.

Answer

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

Answer

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