Question 448 of 820
DP-900 Practice Question: Identify considerations for relational data on Azure
A company is migrating a 3-TB on-premises SQL Server database to Azure. The database heavily uses cross-database queries with three-part names (e.g., db.schema.table) and relies on SQL Server Agent for scheduled maintenance jobs. They want a fully managed PaaS service with automatic backups and patching, while minimizing application code changes. Which Azure SQL service should they choose?
⚠ Common exam trap
Many candidates choose Azure SQL Database (single or elastic pool) because it is the most well-known PaaS option, overlooking that it lacks critical on-premises features like cross-database three-part name queries and SQL Server Agent, which are essential for minimizing code changes in this migration scenario.
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 cross-database queries using three-part names (db.schema.table) and SQL Server Agent for scheduled maintenance jobs. 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 cross-database query support and SQL Agent.
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 Managed Instance
Why this is correct
Azure SQL Managed Instance is the correct choice because it offers near-total parity with on-premises SQL Server, preserving critical features like SQL Server Agent and three-part cross-database queries, which are essential for a seamless lift-and-shift of a 3 TB transactional database. Its instance-level scope allows multiple databases to reside on the same logical server, enabling in-database queries across those databases without application rewrites. Being fully managed, it handles patching, backups, and high availability, making it the ideal target for this migration.
- ✗
Azure SQL Database (single database)
Why it's wrong here
Azure SQL Database (single database) is wrong because it lacks server-level constructs, so three-part names such as Database1.schema.table fail, and SQL Server Agent is absent, which prevents native execution of scheduled jobs and maintenance tasks that the current SQL Server likely uses. Running a 3 TB database with cross-database dependencies would force re-architecting the solution to use elastic query or external data sources, introducing substantial modifications to application code and increasing migration complexity. This makes it unsuitable for a straightforward migration.
When this WOULD be correct
A company needs a fully managed PaaS database for a new application with no cross-database dependencies and no need for SQL Agent. They want automatic backups and patching, and the application uses simple single-database connections.
- ✗
Azure SQL Database (elastic pool)
Why it's wrong here
Azure SQL Database (elastic pool) is wrong because it is merely a cost-optimization layer that groups multiple single databases to share a fixed pool of vCores and storage; it does not change the underlying engine capabilities of Azure SQL Database. Therefore, it inherits the same restrictions as the single database option: no SQL Server Agent and no three-part cross-database queries, meaning the 3 TB database would still need application changes. While elastic pools are useful for scaling many low-activity databases, they do not address the compatibility requirements of this migration, making them an incorrect target.
When this WOULD be correct
A company needs to manage multiple databases with varying and unpredictable usage patterns, wanting to optimize cost by sharing resources among databases while still getting automatic backups and patching. They do not require cross-database queries or SQL Agent.
- ✗
Azure Synapse Analytics dedicated SQL pool
Why it's wrong here
Azure Synapse Analytics dedicated SQL pool is wrong for this transactional workload because it is a distributed, Massively Parallel Processing (MPP) engine designed for analytical queries over large volumes of data, not for OLTP operations with frequent, small transactions. It lacks SQL Server Agent, so scheduled jobs cannot run, and its architecture does not support three-part cross-database queries in the same way, as each database is a separate compute boundary. Performing high-frequency inserts, updates, and deletes would suffer from latency and throughput bottlenecks, so it cannot replace the source SQL Server instance.
When this WOULD be correct
This option would be correct for a question about migrating a large data warehouse (e.g., 10+ TB) for analytics and reporting, where the workload is read-intensive, uses PolyBase for data integration, and does not require cross-database queries or SQL Server Agent. The question would emphasize petabyte-scale data and high concurrency for complex queries.
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 choice because it offers near-total parity with on-premises SQL Server, preserving critical features like SQL Server Agent and three-part cross-database queries, which are essential for a seamless lift-and-shift of a 3 TB transactional database. Its instance-level scope allows multiple databases to reside on the same logical server, enabling in-database queries across those databases without application rewrites. Being fully managed, it handles patching, backups, and high availability, making it the ideal target for this migration.
✗Azure SQL Database (single database)Wrong 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, both of which are required by the scenario.
★ When this WOULD be the correct answer
A company needs a fully managed PaaS database for a new application with no cross-database dependencies and no need for SQL Agent. They want automatic backups and patching, and the application uses simple single-database connections.
Why candidates choose this
Candidates may think 'fully managed PaaS' always means Azure SQL Database, overlooking the specific requirements for cross-database queries and SQL Agent that only Managed Instance supports.
✗Azure SQL Database (elastic pool)Wrong answer — click to see why▾
Why this is wrong here
Azure SQL Database (elastic pool) does not support cross-database queries with three-part names or SQL Server Agent, so it cannot meet the migration requirements without significant application changes.
★ When this WOULD be the correct answer
A company needs to manage multiple databases with varying and unpredictable usage patterns, wanting to optimize cost by sharing resources among databases while still getting automatic backups and patching. They do not require cross-database queries or SQL Agent.
Why candidates choose this
Candidates may think elastic pools are a fully managed PaaS option that can handle multiple databases, but they overlook the lack of support for cross-database queries and SQL Agent, which are critical in this scenario.
✗Azure Synapse Analytics dedicated SQL poolWrong answer — click to see why▾
Why this is wrong here
Azure Synapse Analytics dedicated SQL pool is a massively parallel processing (MPP) data warehouse designed for large-scale analytics, not for OLTP workloads with cross-database queries and SQL Server Agent jobs. It does not support cross-database queries using three-part names or SQL Server Agent, and migrating a 3-TB SQL Server database with those dependencies would require significant application changes.
★ When this WOULD be the correct answer
This option would be correct for a question about migrating a large data warehouse (e.g., 10+ TB) for analytics and reporting, where the workload is read-intensive, uses PolyBase for data integration, and does not require cross-database queries or SQL Server Agent. The question would emphasize petabyte-scale data and high concurrency for complex queries.
Why candidates choose this
Candidates may confuse Azure Synapse Analytics with a general-purpose database service due to its SQL-based interface, or they might think its dedicated SQL pool can handle any large database migration, overlooking its specialized analytics focus and lack of support for cross-database queries and SQL Agent.
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?”
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.