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.

• ✗

  A. Azure SQL Database (single database)

  Why it's wrong here

  Azure SQL Database (single database) is a fully managed PaaS offering, but it loses many on-premises SQL Server instance-level capabilities. It does not support SQL Server Agent (only Elastic Jobs with limitations), linked servers, or native cross-database queries, and using it would require rearchitecting the application to use elastic queries or external tables. This contradicts the goal of a simple migration, so it is not the best choice.

  When this WOULD be correct

  A company wants a fully managed PaaS database with minimal management overhead, does not need SQL Server Agent jobs or linked servers, and requires only a single database with automated backups and patching.

• ✓

  B. Azure SQL Managed Instance

  Why this is correct

  Azure SQL Managed Instance is the correct PaaS choice because it provides near-complete compatibility with on-premises SQL Server, including SQL Server Agent jobs, linked servers, Service Broker, and cross-database queries. These instance-scoped features are preserved while Azure automatically handles patching, backups, and high availability, making it a fully managed lift-and-shift target with minimal application changes.

• ✗

  C. SQL Server on Azure Virtual Machines

  Why it's wrong here

  SQL Server on Azure Virtual Machines is an IaaS solution that provides full SQL Server features like Agent and linked servers, but it is not fully managed. The company would be responsible for managing the operating system, SQL Server patching, backups, and configuring high availability, which adds significant administrative overhead. Since the requirement emphasizes a fully managed service, this option is incorrect.

  When this WOULD be correct

  This option would be correct if the company needs full control over the SQL Server environment, requires custom configurations not supported in PaaS (e.g., SQL Server Agent jobs with OS-level dependencies, linked servers to on-premises or non-Azure sources, or cross-database queries that exceed PaaS limitations), or must lift-and-shift existing applications with minimal changes without migrating to a PaaS service.

• ✗

  D. Azure SQL Database elastic pool

  Why it's wrong here

  Azure SQL Database elastic pool is essentially a collection of single databases sharing a common pool of resources. It inherits the same limitations as a single Azure SQL Database: no SQL Server Agent, no linked servers, and no cross-database queries between databases in the pool unless you resort to elastic query with external data sources. It does not offer instance-level compatibility, so it fails to meet the migration requirements.

  When this WOULD be correct

  A company needs to manage multiple databases with varying and unpredictable usage patterns, wants to optimize cost by sharing resources among them, and does not require instance-level features like SQL Agent jobs or linked servers.

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