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

  Why this is correct

  Azure SQL Database is a PaaS service that handles patching, supports elastic query for cross-database queries, and allows collation settings on a per-database level. It does not include SQL Agent or linked servers, which are not required here.

• ✗

  Azure SQL Managed Instance

  Why it's wrong here

  Azure SQL Managed Instance is a PaaS implementation that provides near-full SQL Server instance compatibility, including SQL Agent and linked servers. However, it deploys into a dedicated virtual network, requires a larger resource footprint, and comes with a higher price point. Since the customer only needs database-level elastic queries and per-database collation—not instance-scoped features—this option adds unnecessary administrative and cost overhead compared to Azure SQL Database.

  When this WOULD be correct

  A company needs to migrate an on-premises database to Azure with minimal changes, requires instance-scoped features such as SQL Agent jobs, linked servers, or cross-database transactions, and has databases up to 8 TB. They also want automated patching and backups, but need higher compatibility with on-premises SQL Server.

• ✗

  SQL Server on Azure Virtual Machine

  Why it's wrong here

  SQL Server on Azure Virtual Machine offers IaaS, granting full control over the OS and SQL Server configuration, but the customer assumes all management duties, such as applying patches, managing backups, and setting up high availability. This directly contradicts the goal of minimizing management overhead, and the VM must be continuously sized and paid for regardless of workload. For a simple single-database migration with no instance-level requirements, this is a heavy, operationally expensive choice.

  When this WOULD be correct

  A question requiring full control over the operating system, need to install custom software, or need for instance-level features like SQL Agent jobs, linked servers, or legacy dependencies that are not supported in PaaS offerings.

• ✗

  Azure Synapse SQL pool

  Why it's wrong here

  Azure Synapse Analytics SQL pool is a distributed, massively parallel processing (MPP) analytics engine designed for large-scale data warehousing and complex analytical queries, not for general-purpose online transaction processing (OLTP). Its columnar storage and separate architecture do not support the same elastic cross-database queries or per-database collation semantics as Azure SQL Database. Choosing Synapse would force a major application rewrite and still fail to deliver the needed relational transaction behavior.

  When this WOULD be correct

  A company needs to run complex analytical queries on petabyte-scale data, integrating with big data and machine learning pipelines, and requires massive parallel processing (MPP) architecture. They do not need transactional consistency or fine-grained collation control.

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