Plan and configure a high availability and disaster recovery environment →mediumMultiple ChoiceObjective-mapped
DP-300 Practice Question: Plan and configure a high availability and disaster recovery environment
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?
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 from the current primary to the original primary.
After an automatic failover, the secondary region becomes the primary. To restore the original primary and re-establish the failover relationship, you must perform a planned failover (also called a graceful failover) from the current primary (the former secondary) to the original primary. This switches roles back without data loss. Option A is incorrect because deleting and recreating the failover group is unnecessary and disruptive. Option B is incorrect because you cannot add the original primary as a new secondary if it is already part of the failover group—it must be removed first. Option D is incorrect because removing and re-adding the original primary would break the geo-replication and is not the correct procedure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Delete the failover group and recreate it with the original primary as the primary.
Why it's wrong here
This would cause downtime and data loss; planned failover is the correct approach.
- ✗
Add the original primary as a new secondary to the current primary.
Why it's wrong here
The original primary is still part of the failover group as a secondary; you don't add it again.
- ✓
Initiate a planned failover from the current primary to the original primary.
Why this is correct
Planned failover switches roles gracefully, making the original primary the primary again.
- ✗
Remove the original primary from the failover group and re-add it.
Why it's wrong here
Removing and re-adding the original primary instance necessitates a full data re-seeding operation, which is inefficient and unnecessary when the instance is intact after a temporary outage. The objective is to re-establish the failover relationship and bring the original primary back online efficiently, typically via a planned failover or failback. This option is tempting as a complete reset, and would be correct if the original primary was corrupted or permanently removed, requiring a new instance to be added and fully seeded as a secondary replica.
Go deeper
Related to this question
Learn chapter
Overview of Azure Data Platform Options
Key term
Azure SQL Managed Instance
Azure SQL Managed Instance is a fully managed cloud database service that gives you nearly all the features of Microsoft SQL Server on your own server, without you having to manage the hardware or operating system.
About these practice questions
Courseiva writes every DP-300 question from scratch — 906 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
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.