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 Database (single database)

  Why it's wrong here

  Azure SQL Database (single database) is a PaaS service, but it has significant compatibility gaps compared to an on-premises SQL Server instance. It does not support SQL Server Agent jobs or cross-database queries using three-part names, which are likely required by the financial company's workload. Additionally, the single database model lacks an instance boundary, so features that rely on an instance (such as SQL Agent) are unavailable. Therefore, it is not a suitable target for this 2 TB migration.

  When this WOULD be correct

  A company needs a fully managed PaaS database for a new application with no cross-database dependencies or agent jobs, and wants the lowest cost and simplest management for a single database workload.

• ✓

  Azure SQL Managed Instance

  Why this is correct

  Azure SQL Managed Instance is a fully managed PaaS service that provides near-total compatibility with the on-premises SQL Server engine, including support for SQL Server Agent jobs and cross-database queries using three-part names. It also offers automatic backups, patching, and high availability, so the 2 TB database can be migrated with only minimal application and code changes. For a financial company looking to move off an on-premises SQL Server while preserving existing features, Managed Instance is the correct choice.

• ✗

  Azure SQL Database elastic pool

  Why it's wrong here

  An elastic pool is a shared-resource model for multiple Azure SQL databases, not a separate SQL Server instance, so it inherits the same limitations as a single database. It does not support SQL Server Agent jobs or cross-database queries that rely on three-part names (e.g., database.schema.table), and it is not designed to host one large 2 TB database with instance-level features. Because the company needs the functionality of an on-premises SQL Server instance, an elastic pool cannot provide the required compatibility.

  When this WOULD be correct

  A company needs to manage multiple databases with varying and unpredictable usage patterns, and wants to optimize cost by sharing resources among them, without requiring cross-database queries or SQL Agent jobs.

• ✗

  SQL Server on Azure Virtual Machine

  Why it's wrong here

  SQL Server on Azure Virtual Machine is an IaaS offering where you retain full control over the VM and SQL Server, but you also remain responsible for managing the operating system, SQL Server patching, backups, and high availability. This option requires the most ongoing administrative effort and does not deliver the fully managed PaaS experience that the question specifies. Although it can run SQL Server Agent and cross-database queries, it is not a managed service, so it is not the best fit for this migration scenario.

  When this WOULD be correct

  A company needs full control over the SQL Server instance, including custom configurations, third-party agents, or specific OS-level dependencies, and is willing to manage the underlying infrastructure.

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

Go deeper

Related to this question