DP-900 Practice Question: Identify considerations for relational data on Azure

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 a fully managed PaaS deployment that provides near 100% surface-area compatibility with on-premises SQL Server, including instance-scoped features such as SQL Agent jobs, Service Broker, Database Mail, and CLR assemblies. It integrates with a customer's virtual network yet offloads patching, backups, and high availability to Azure, making it the ideal choice for a lift-and-shift migration with minimal application changes. Unlike single databases, it supports cross-database queries and the full T-SQL surface needed by legacy workloads.

• ✗

  Azure SQL Database (single database)

  Why it's wrong here

  Azure SQL Database (single database) is built on a logical server architecture that is fundamentally incompatible with instance-level constructs: it does not support SQL Agent jobs, Service Broker, or database mail, and even cross-database queries require elastic query or external libraries. While the service handles infrastructure automatically, migrating an on-premises database here demands re-engineering application features such as scheduled maintenance jobs and asynchronous messaging, which contradicts the goal of a simple migration. The lack of instance scope is the core technical blocker, not the performance or cost of the service.

  When this WOULD be correct

  An exam scenario where a company wants to migrate a single SQL Server database with no dependency on instance-level features like SQL Agent jobs, Service Broker, or cross-database queries, and is willing to refactor application code to use Azure Elastic Jobs or other alternatives.

• ✗

  Azure SQL Database elastic pool

  Why it's wrong here

  An elastic pool is essentially a cost management container for multiple single databases that share a pool of CPU, memory, and IOPS, so it inherits every limitation of the single database model—including the absence of SQL Agent and Service Broker. Its purpose is to absorb usage spikes across databases with variable workloads, not to offer instance-level compatibility. Choosing an elastic pool would still require the same application redesign as Azure SQL Database single, because the pool provides no instance-scoped objects, security principals, or SQL Server Agent infrastructure.

  When this WOULD be correct

  A company needs to manage multiple databases with varying and unpredictable usage patterns, seeking cost-effective resource sharing and simplified management, and does not require instance-level features like SQL Agent or Service Broker.

• ✗

  SQL Server on Azure Virtual Machines

  Why it's wrong here

  While SQL Server on Azure VM supports all these features, it requires the company to manage the virtual machine, operating system, and SQL Server, including patching and backups, which contradicts the desire to minimize management overhead.

  When this WOULD be correct

  A company needs full control over the SQL Server environment, including custom configurations, third-party tools, or specific versions of SQL Server that are not supported in PaaS offerings. They are willing to manage the VM and accept higher administrative overhead.

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.

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?”