A company manages several on-premises Microsoft SQL Server databases. You need to migrate the databases to Microsoft Azure by using a backup process of Microsoft SQL Server. Which data technology…

Question

Options

• AAzure SQL Database single database
• BAzure SQL Data Warehouse
• CAzure Cosmos DB
• DAzure SQL Database Managed Instance
• EHDInsight Spark cluster

• D
  95% (20)
• E
  5% (1)

Explanation

Azure SQL Database Managed Instance (D) is the correct choice because it provides near-100% compatibility with on-premises SQL Server, including native backup/restore support - meaning you can use .bak files directly to migrate databases with minimal changes.

Why the distractors fail:

• A (Single Database): Azure SQL Database lacks full SQL Server compatibility and does not support native SQL Server backup/restore natively for migrations; it requires tools like DMS or BACPAC exports.
• B (Azure SQL Data Warehouse / Synapse): This is an analytics/OLAP platform optimized for data warehousing, not a drop-in replacement for OLTP SQL Server workloads.
• C (Azure Cosmos DB): A NoSQL, globally distributed database - completely different data model from SQL Server; no SQL Server backup compatibility whatsoever.
• E (HDInsight Spark): A big data/distributed compute platform built on Hadoop/Spark - unrelated to SQL Server migration scenarios.

Memory tip: Think "Managed Instance = Managed Migration" - the word Managed signals it's designed to manage the full SQL Server engine in the cloud, making it the only option that lets you lift-and-shift a traditional SQL Server backup (.bak) directly into Azure.

No community discussion yet for this question.