DP-900 Practice Question: Identify considerations for relational data on Azure
A company is migrating a 2-TB on-premises SQL Server database to Azure. The database uses SQL Server Agent jobs for scheduled maintenance, relies on linked servers to query data from another SQL Server instance, and requires cross-database queries within the same instance. The company wants a fully managed PaaS service that minimizes application code changes and provides automatic backups and patching. Which Azure SQL service should they choose?
⚠ Common exam trap
A common mix-up: candidates confuse Azure SQL Database (which is database-level PaaS) with Azure SQL Managed Instance (which is instance-level PaaS), overlooking that linked servers, Agent jobs, and cross-database queries require instance-scoped functionality not available in Azure SQL Database.
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
✓
Azure SQL Managed Instance
Azure SQL Managed Instance is the correct choice because it provides near 100% compatibility with on-premises SQL Server, including support for SQL Server Agent jobs, linked servers, and cross-database queries within the same instance. As a fully managed PaaS service, it offers automatic backups, patching, and high availability while minimizing application code changes, unlike Azure SQL Database which lacks instance-scoped features.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Azure SQL Database (Single Database)
Why it's wrong here
Azure SQL Database as a single database also lacks SQL Server Agent and linked servers, and its elastic query features are limited compared to true cross-database queries. This forces application changes to handle scheduling and external data connections, and it does not provide instance-level scope for jobs or maintenance tasks. Therefore, it is unsuitable for a simple lift-and-shift migration of a 2 TB database with existing dependencies.
When this WOULD be correct
A company needs a fully managed PaaS service for a new application with a single database under 100 GB, no dependency on SQL Server Agent, linked servers, or cross-database queries, and wants minimal management overhead.
- ✗
Azure SQL Database (Elastic Pool)
Why it's wrong here
Azure SQL Database in an Elastic Pool shares the same core limitations as a single database: it does not support SQL Server Agent, linked servers, or cross-database queries that span the same instance. Migrating the workload would require rewriting job scheduling and dependency logic, and the pool's shared eCPU and DTU resources can also introduce noisy-neighbor performance variability that is not present on a dedicated instance.
When this WOULD be correct
A company needs to manage multiple databases with varying and unpredictable usage patterns, seeking cost-effective resource sharing and automatic scaling, without requiring instance-level features like Agent jobs or linked servers.
- ✓
Azure SQL Managed Instance
Why this is correct
Azure SQL Managed Instance is the recommended destination for a 2 TB on-premises SQL Server database because it provides near-100% T-SQL surface compatibility, including SQL Server Agent, linked servers, Service Broker, and cross-database queries. Unlike Azure SQL Database, it supports instance-scoped features without requiring application changes, and it also handles backups, patching, and high availability automatically as a fully managed PaaS service.
- ✗
SQL Server on Azure Virtual Machine
Why it's wrong here
SQL Server on Azure Virtual Machines is an IaaS offering that does include SQL Server Agent and linked servers, so it could technically run the same code. However, you are responsible for installing and managing the operating system, SQL Server software, backups, patching, and high availability, which contradicts a fully managed solution. It also requires more administrative overhead and does not provide the same automated maintenance as Azure SQL Managed Instance.
When this WOULD be correct
This option would be correct if the company requires full control over the operating system, needs to install custom software or third-party tools, or must run a version of SQL Server not available in Azure SQL Managed Instance (e.g., older versions like SQL Server 2008).
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The DP-900 exam frequently reuses these exact scenarios with slightly different constraints.
✓Azure SQL Managed InstanceCorrect answer▾
Why this is correct
Azure SQL Managed Instance is the recommended destination for a 2 TB on-premises SQL Server database because it provides near-100% T-SQL surface compatibility, including SQL Server Agent, linked servers, Service Broker, and cross-database queries. Unlike Azure SQL Database, it supports instance-scoped features without requiring application changes, and it also handles backups, patching, and high availability automatically as a fully managed PaaS service.
✗Azure SQL Database (Single Database)Wrong answer — click to see why▾
Why this is wrong here
Azure SQL Database (Single Database) does not support SQL Server Agent jobs, linked servers, or cross-database queries, which are required by the company's migration.
★ When this WOULD be the correct answer
A company needs a fully managed PaaS service for a new application with a single database under 100 GB, no dependency on SQL Server Agent, linked servers, or cross-database queries, and wants minimal management overhead.
Why candidates choose this
Candidates may think 'Single Database' is the simplest PaaS option and assume it can handle all SQL Server features, overlooking its limitations with agent jobs and cross-database functionality.
✗Azure SQL Database (Elastic Pool)Wrong answer — click to see why▾
Why this is wrong here
Azure SQL Database (Elastic Pool) does not support SQL Server Agent jobs, linked servers, or cross-database queries, which are required by the company's workload.
★ When this WOULD be the correct answer
A company needs to manage multiple databases with varying and unpredictable usage patterns, seeking cost-effective resource sharing and automatic scaling, without requiring instance-level features like Agent jobs or linked servers.
Why candidates choose this
Candidates may think Elastic Pools are suitable for any multi-database scenario due to their cost savings and management simplicity, overlooking the specific instance-level feature requirements in the question.
✗SQL Server on Azure Virtual MachineWrong answer — click to see why▾
Why this is wrong here
SQL Server on Azure Virtual Machine is an IaaS service, not fully managed PaaS. It requires manual patching, backup management, and does not minimize application code changes as much as Azure SQL Managed Instance, which offers higher compatibility with SQL Server Agent jobs, linked servers, and cross-database queries.
★ When this WOULD be the correct answer
This option would be correct if the company requires full control over the operating system, needs to install custom software or third-party tools, or must run a version of SQL Server not available in Azure SQL Managed Instance (e.g., older versions like SQL Server 2008).
Why candidates choose this
Candidates may think that running SQL Server on a VM is the simplest lift-and-shift migration, overlooking that Azure SQL Managed Instance provides higher compatibility with on-premises features while being fully managed.
Analysis generated from the official DP-900blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
Learn chapter
Data Roles and Core Concepts
Key term
Azure SQL Database
Azure SQL Database is a fully managed relational database-as-a-service (DBaaS) in Microsoft Azure, based on the SQL Server engine, that handles scaling, backups, patching, and high availability automatically.
Key term
SQL Managed Instance
SQL Managed Instance is a cloud database service from Azure that gives you most of the features of a full SQL Server instance without you having to manage the underlying hardware or software patches.
About these practice questions
This DP-900 question is part of Courseiva's 820-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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.