DP-900 Practice Question: Identify considerations for relational data on Azure
A company needs to migrate 10 on-premises SQL Server databases (each 50–200 GB) to Azure. The databases frequently run cross-database queries using three-part names (e.g., DB1.dbo.table) and rely on SQL Server Agent for maintenance tasks. They want to minimize management overhead and share resources across databases to reduce costs. Which Azure SQL deployment option should they choose?
⚠ Common exam trap
It's easy for candidates to choose Azure SQL Database elastic pool (Option A) because they think it supports cross-database queries and SQL Agent, but it actually lacks native three-part name support and SQL Agent, which are only available in Managed Instance.
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 correct because it provides native support for cross-database queries using three-part names (e.g., DB1.dbo.table) and SQL Server Agent for maintenance tasks, which are critical requirements. It also offers a fully managed platform that minimizes management overhead while allowing resource sharing across databases within the instance, reducing costs compared to single databases or VMs.
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 elastic pool
Why it's wrong here
Azure SQL Database elastic pool allows multiple databases to share pooled vCore or DTU resources, but it still runs the single database engine, so it does not natively support cross-database queries with three-part names or SQL Server Agent jobs. Elastic pools are designed to manage workloads with unpredictable, bursty usage patterns, not to preserve on-prem SQL Server compatibility features. While it addresses resource sharing, it fails the requirement of supporting existing cross-database joins and SQL Agent jobs, making it an incorrect choice.
When this WOULD be correct
A company needs to migrate multiple small-to-medium databases with varying usage patterns to Azure, wants to share resources to reduce costs, and does not require cross-database queries or SQL Server Agent. Elastic pool would be the correct choice to maximize resource utilization and minimize management overhead.
- ✓
Azure SQL Managed Instance
Why this is correct
Azure SQL Managed Instance is the correct target for this migration because it supports cross-database queries using three-part naming, SQL Server Agent, and linked servers, just like on-prem SQL Server. It also allows multiple databases (10, ranging from 50–200 GB) to reside in a single instance, sharing resources efficiently while preserving existing database dependencies. As a fully managed PaaS service, it offers automatic patching, backups, and high availability, making it ideal for a lift-and-shift migration with minimal application changes.
- ✗
SQL Server on Azure Virtual Machine
Why it's wrong here
SQL Server on Azure Virtual Machine provides full product compatibility, including all features, but it is an IaaS offering that requires you to manage the OS, patching, backups, and high availability manually. The total data volume (500 GB to 2 TB) would require careful storage and VM sizing, plus ongoing administrative effort, which contradicts the goal of a fully managed cloud service. This option would be chosen only if you needed features not available in Managed Instance, but for this scenario the maintenance burden is unnecessary.
When this WOULD be correct
A company needs full control over the SQL Server environment, including custom configurations, third-party tools, or legacy features not supported in PaaS. They also require OS-level access for specific compliance or performance tuning, and are willing to manage patching and backups.
- ✗
Azure SQL Database single database
Why it's wrong here
Azure SQL Database single database is unsuitable because each database is an isolated unit that does not natively support cross-database queries using three-part names; workarounds like elastic queries or external tables add complexity. With 10 databases of 50–200 GB each, you would manage them separately, losing the ability to maintain existing cross-database joins and SQL Server Agent jobs. This makes it a poor fit for a migration that expects to keep the same database-level functionality and relationships.
When this WOULD be correct
A company needs to migrate individual, independent databases with no cross-database dependencies and minimal management overhead, and they do not require SQL Server Agent or instance-level features.
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 correct target for this migration because it supports cross-database queries using three-part naming, SQL Server Agent, and linked servers, just like on-prem SQL Server. It also allows multiple databases (10, ranging from 50–200 GB) to reside in a single instance, sharing resources efficiently while preserving existing database dependencies. As a fully managed PaaS service, it offers automatic patching, backups, and high availability, making it ideal for a lift-and-shift migration with minimal application changes.
✗Azure SQL Database elastic poolWrong answer — click to see why▾
Why this is wrong here
Azure SQL Database elastic pool does not support cross-database queries using three-part names or SQL Server Agent, both of which are required by the company.
★ When this WOULD be the correct answer
A company needs to migrate multiple small-to-medium databases with varying usage patterns to Azure, wants to share resources to reduce costs, and does not require cross-database queries or SQL Server Agent. Elastic pool would be the correct choice to maximize resource utilization and minimize management overhead.
Why candidates choose this
Candidates see 'share resources' and 'minimize management overhead' and associate elastic pools with cost savings and low management, overlooking the critical requirements for cross-database queries and SQL Server Agent.
✗SQL Server on Azure Virtual MachineWrong answer — click to see why▾
Why this is wrong here
SQL Server on Azure VM requires manual management of OS, SQL Server, and backups, increasing overhead. It does not natively support cross-database queries with three-part names across separate VMs without linked servers, and sharing resources across databases is less efficient than a managed instance.
★ When this WOULD be the correct answer
A company needs full control over the SQL Server environment, including custom configurations, third-party tools, or legacy features not supported in PaaS. They also require OS-level access for specific compliance or performance tuning, and are willing to manage patching and backups.
Why candidates choose this
Candidates may think IaaS offers the most flexibility and familiarity, assuming it can easily handle cross-database queries and agent jobs, while overlooking the management overhead and cost inefficiency for multiple databases.
✗Azure SQL Database single databaseWrong answer — click to see why▾
Why this is wrong here
Azure SQL Database single database does not support cross-database queries using three-part names or SQL Server Agent, which are required by the company's workloads.
★ When this WOULD be the correct answer
A company needs to migrate individual, independent databases with no cross-database dependencies and minimal management overhead, and they do not require SQL Server Agent or instance-level features.
Why candidates choose this
Candidates may think single databases are the simplest and cheapest option, overlooking the need for cross-database queries and agent jobs that require instance-level scope.
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
Azure SQL Services
Key term
Table
A table is a structured collection of data organized into rows and columns, used in databases and spreadsheets to store and manage information efficiently.
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
One of 820 original DP-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.