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 elastic pool

  Why this is correct

  Azure SQL Database elastic pools share a set of eDTUs or vCores across multiple databases, letting a SaaS provider assign per-database minimum and maximum performance limits. This design absorbs unpredictable usage spikes from different tenants without over-provisioning each database, making it the most cost-efficient and operationally simple choice for a large multi-tenant workload.

• ✗

  Azure SQL Database (single database)

  Why it's wrong here

  Deploying one Azure SQL Database per tenant means each database is independently sized with its own DTU or vCore allocation, so you pay for peak capacity on every tenant even when most are idle. Without pooling, you must either over-provision each database to handle bursts or accept throttling, leading to significantly higher costs and more administrative effort for a SaaS environment with many small, spiky tenants.

  When this WOULD be correct

  A question requiring strict tenant isolation, predictable performance, or a fixed pricing model per tenant, such as: 'A financial services company needs separate databases for each client with guaranteed performance and no resource contention.'

• ✗

  Azure SQL Managed Instance

  Why it's wrong here

  Azure SQL Managed Instance offers near-complete SQL Server compatibility and is designed for lift-and-shift migrations of medium-to-large enterprise databases, not for hosting thousands of small multi-tenant databases. Each instance has fixed compute and storage resources with no equivalent of an elastic pool, so scaling tenant workloads requires resizing the entire instance and paying for dedicated capacity that remains largely unused. This makes it far more expensive and less flexible for a SaaS provider's shared, multi-tenant footprint.

  When this WOULD be correct

  A company needs to migrate an existing on-premises SQL Server application to Azure with minimal changes, requiring near 100% compatibility with SQL Server features like SQL Agent, CLR, or cross-database queries, and does not need the multi-tenant resource sharing of elastic pools.

• ✗

  SQL Server on Azure Virtual Machine

  Why it's wrong here

  SQL Server on Azure Virtual Machines is an IaaS offering where you manage the VM, operating system, SQL Server installation, and all patches and backups. Hosting many small tenant databases on a single VM requires manually consolidating workloads and sizing the VM for peak aggregate load, while separate VMs for each tenant would multiply licensing and infrastructure costs. No built-in pooling or per-database scaling exists, so operational overhead and cost typically exceed PaaS alternatives.

  When this WOULD be correct

  This option would be correct for a scenario requiring full control over the SQL Server instance, such as needing custom configurations, legacy application compatibility, or specific OS-level dependencies that are not supported by PaaS offerings.

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