Courseiva

DP-300 Practice Question: Plan and configure a high availability and disaster recovery environment

You have an Azure SQL Database configured with a failover group that includes a secondary in another region. The primary region experiences a complete outage. You initiate a forced failover. After the outage is resolved, you want to bring the original primary back as a secondary without data loss. What should you do?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Remove the original primary from the failover group, drop the database, and recreate it as a new secondary

After a forced failover, the original primary is in a failed state. To bring it back as a secondary without data loss, you must remove it from the failover group, drop the original database, and then add a new secondary database (which will be seeded from the current primary). This is the only method that ensures no data loss. Option A is incorrect because there is no 'az sql db failover-group re-sync' command. Option B is incorrect because active geo-replication is not required; failover groups automatically handle replication. Option C is incorrect because restoring from backup would not reflect changes made after the failover, resulting in data loss.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Use the 'az sql db failover-group re-sync' command to re-synchronize

    Why it's wrong here

    There is no such command; you must remove and recreate the secondary.

  • Configure replication from the new primary to the old primary using active geo-replication

    Why it's wrong here

    Active geo-replication is separate from failover groups; mixing both is not supported.

  • Restore the original primary from backup and re-add it to the failover group

    Why it's wrong here

    Restoring from backup will lose transactions that occurred after the failover, unless point-in-time is used, but it's not the standard procedure.

  • Remove the original primary from the failover group, drop the database, and recreate it as a new secondary

    Why this is correct

    This is the recommended approach to rejoin a failed primary after a forced failover.

Visual reference

Client Recursive Resolver Root DNS (13 root servers) TLD DNS (.com, .org, …) Authoritative example.com query IP addr answer

About these practice questions

This DP-300 question is part of Courseiva's 906-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This DP-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-300 exam.