Failback to Original Primary Using Planned Failover in Azure SQL Geo-Replication

A multinational e-commerce company uses Azure SQL Database active geo-replication to replicate a critical inventory database to a secondary region. During a regional outage, the application automatically fails over to the secondary database. After the primary region recovers, the administrator wants to make the original primary the main database again without losing any data modifications made on the secondary during the outage. What should the administrator do?

Quick Answer

The answer is to initiate a planned failover to switch back to the original primary. This is correct because a planned failover in Azure SQL Database active geo-replication performs a full synchronization between the current primary (the former secondary) and the original primary before swapping roles, ensuring zero data loss even after modifications were made during the outage. On the Microsoft Azure Data Fundamentals DP-900 exam, this concept tests your understanding of active geo-replication’s failover types: unplanned failover may cause data loss, while planned failover is the only way to safely execute a failback to the original primary without losing changes. A common trap is confusing “failover” with “failback” or assuming you must manually copy data; instead, remember that planned failover handles the entire role reversal seamlessly. Memory tip: “Planned equals preserved” — a planned failover preserves all data during the failback process.

⚠ Common exam trap

Many exam-takers confuse a planned failover (graceful, no data loss) with a forced failover (unplanned, potential data loss), leading candidates to incorrectly choose Option B when they need to preserve all modifications made on the secondary during an outage.

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

✓

Initiate a planned failover to switch back to the original primary.

A planned failover (also known as graceful failover) in Azure SQL Database active geo-replication is designed to switch roles between the primary and secondary databases without data loss. After the original primary region recovers, initiating a planned failover synchronizes all data from the current primary (the former secondary) to the original primary, making it the new primary while preserving all modifications made during the outage. This operation ensures zero data loss because it forces a final synchronization before the role swap.

Answer analysis

Option-by-option breakdown

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

✗
Drop the geo-replication relationship, then recreate the secondary from the current primary.
Why it's wrong here
This would discard the secondary's data and restart replication with data loss.
✗
Perform a forced failover to switch back to the original primary.
Why it's wrong here
A forced failover may cause data loss because it does not synchronize pending changes.
✓
Initiate a planned failover to switch back to the original primary.
Why this is correct
A planned failover (graceful failover) synchronizes all data between replicas before switching roles, ensuring zero data loss.
✗
Delete the secondary database and restore the original primary from a backup taken before the outage.
Why it's wrong here
This would lose all transactions that occurred during the outage.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on DP-900

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A company uses Azure SQL Database with active geo-replication for disaster recovery. During a regional outage, the secondary database is promoted. After the primary region recovers, what is the best practice to re-establish geo-replication?

hard

A.Delete the old primary database and create a new geo-replication
B.Add the old primary as a secondary to the new primary
C.Reverse the geo-replication direction automatically
✓ D.Perform a planned failover to make the old primary the primary again

Why D: Performing a planned failover properly fails back to the original primary and re-establishes geo-replication. Option A is wrong because deleting the old primary loses data and is unnecessary. Option B is wrong because while you can add the old primary as a secondary, it is not the best practice; a planned failover is preferred. Option C is wrong because automatic reversal of geo-replication direction is not supported; you must manually reconfigure.

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

This DP-900 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-900 exam.