Migrate SQL Server to Azure SQL MI with Minimal Downtime
Short answer
D Use Azure Database Migration Service to perform an online migration that minimizes downtime and data loss for the 4-TB DB1 database.
Question
You plan to migrate DB1 to an Azure SQL Database managed instance.
What should you use to minimize downtime and data loss during the migration?
Key Takeaways
This question tests knowledge of Azure database migration tools; the main trap is selecting Distributed Availability Groups (A) because it underpins the newer Managed Instance Link, but it is not a direct migration tool you configure standalone for this path.
Azure Database Migration Service (DMS) is the correct tool to migrate a large on-premises SQL Server database to Azure SQL Managed Instance with minimal downtime by using online migration and log streaming.
Common mistake: Choosing Option A (distributed availability groups) because the Managed Instance Link feature uses them internally, but you cannot directly use DAGs to migrate to a managed instance without the Link wrapper.
Expert Analysis
Migration Tool Selection: The scenario requires migrating a 4-TB database to Azure SQL Managed Instance with minimal downtime and data loss. Azure Database Migration Service (DMS) is the designated Azure tool for this task. By performing an online migration, DMS takes a full backup, restores it to the target, and then continuously streams and applies transaction logs. This keeps the target database synchronized until the final cutover, restricting downtime to mere seconds or minutes.
Evaluating Distributed Availability Groups: Option A, distributed availability groups (DAGs), is a tempting distractor because the newer Managed Instance Link feature relies on DAGs under the hood. However, you cannot directly configure a DAG between an on-premises SQL Server and an Azure SQL Managed Instance as a standalone migration method. As one comment points out, the Link feature uses DAGs "indirectly," but since "Managed Instance link" is not an option, DAG is not the correct mechanism to select here.
Unsupported and Inapplicable Options: Option B, database mirroring, is a deprecated feature in modern SQL Server versions and cannot be used to establish a migration path to Azure SQL Managed Instance. Option C, Always On Availability Groups, cannot span directly from an on-premises network to an Azure SQL Managed Instance without the aforementioned DAG wrapper. Therefore, neither B nor C can achieve the required minimal downtime migration.
Database Size Consideration: A comment correctly notes that Azure SQL Managed Instance supports databases up to 8 TB (and even larger on the Business Critical tier), so the 4-TB DB1 database fits well within the supported limits for a DMS online migration. This confirms that size is not a blocking factor for choosing DMS. Ultimately, Option D is the only valid, directly usable migration service that fulfills the requirement to minimize both downtime and data loss.
Official Reference
https://learn.microsoft.com/en-us/azure/dms/dms-overview
This link opens the official vendor documentation in a new tab.
Exam Strategy
When asked to minimize downtime during a database migration to Azure, look for Azure Database Migration Service (DMS) in online mode or the Managed Instance Link. Do not select underlying technologies like Distributed Availability Groups unless the wrapper feature (Link) is explicitly presented as an option, as you cannot configure them directly for this path.
Community Votes
78% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 11 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 11
-
quermi 👍 11D is correct. When you migrate databases to Azure by using Azure Database Migration Service, you can do an offline or an online migration. With an offline migration, application downtime starts when the migration starts. With an online migration, downtime is limited to the time to cut over at the end of migration. We suggest that you test an offline migration to determine whether the downtime is acceptable; if not, do an online migration. https://docs.microsoft.com/en-us/azure/dms/tutorial-sql-server-to-managed-instance
-
matongax 👍 3looks correct . azure SQL Mi support up to 8tb dbs as of today
-
prudhvi900 👍 3yes, its the correct answer!
-
RB66 👍 2I think this is correct since this is managed instance that supports Azure Database Migration Service and Native RESTORE DATABASE FROM URL
-
voodoo_sh 👍 1 Answered DYou could use the Link feature to replicate from SQL Server 2019 to Azure SQL MI, which uses distributed availability groups under the hood, but in the answer we don't have this option and DAG is used indirectly in the Link. So pick Azure DMS (D)
Show 6 more comments
-
kilinjos 👍 1 Answered DThe answer is D but the question is not up-to-date. If there was a Managed Instance link in the options, I would have chosen it.
-
prudhvi900 👍 1it is not the matter of support migration, but need to reduce the downtime?
-
eric0718 👍 1 Answered DAzure Database Migration Service
-
Quinton 👍 1 Answered DD is the correct option
-
ramelas 👍 1yes, you are correct
-
o2091 👍 1is it correct?
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DP-300 Questions
Access 105 questions with complete answers and detailed explanations.
View Full DP-300 Practice Test →