DP-900 Practice Question: Identify considerations for relational data on Azure
A SaaS company hosts a multi-tenant application. Each tenant has a separate Azure SQL Database. The databases are small (1-3 GB) and their workloads vary significantly over time, with some tenants active during business hours and others at night. The company wants to maximize resource utilization and minimize costs by pooling compute resources across tenants while maintaining predictable performance per database. Which Azure SQL Database deployment option should they choose?
⚠ Common exam trap
It's easy for candidates to choose Single Database (Option A) thinking it offers the best isolation, but they overlook the cost and resource utilization benefits of Elastic Pool for variable, non-overlapping workloads across many small databases.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Azure SQL Database Elastic Pool
Azure SQL Database Elastic Pool is the correct choice because it allows multiple databases (tenants) to share a fixed pool of compute and storage resources, enabling cost efficiency through resource pooling while providing predictable performance via per-database resource limits (min/max DTU or vCore). This matches the scenario of small databases with variable, non-overlapping workloads across tenants.
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
With Azure SQL Database Single Database, each tenant database is provisioned with a fixed service tier and compute size, so you pay for dedicated resources even when a tenant is idle. For many small SaaS tenants with intermittent demand, you must size every database to handle its own peak load, leaving most reserved capacity unused. This model has no mechanism for one tenant’s burst to consume another tenant’s idle capacity, making it far more expensive than an elastic pool that shares a resource set among all tenant databases.
When this WOULD be correct
A question where each tenant requires guaranteed, isolated performance with no resource sharing, such as a financial application with strict compliance requiring separate performance tiers per database.
- ✓
Azure SQL Database Elastic Pool
Why this is correct
An elastic pool allows multiple databases to share a pool of resources. Databases automatically use resources as needed, maximizing utilization and lowering cost while providing predictable performance per database via settings like min and max vCores.
- ✗
Azure SQL Managed Instance
Why it's wrong here
Azure SQL Managed Instance provides near-full SQL Server engine compatibility and is designed for lift-and-shift migrations of existing applications, not for pooling compute across small, variable-workload databases. It fails here because each managed instance has a fixed set of resources (vCores and storage) that cannot be elastically shared among multiple tenant databases; you would need to over-provision for peak loads per instance. It is tempting because it offers high compatibility and built-in high availability, which would be correct if the company needed to migrate an on-premises SQL Server application with minimal changes, rather than optimising cost through resource pooling.
When this WOULD be correct
A company needs to migrate an existing on-premises SQL Server application to Azure with minimal changes, requiring high compatibility with SQL Server features like SQL Agent, CLR, or cross-database queries, and does not need to pool resources across databases.
- ✗
SQL Server on Azure Virtual Machine
Why it's wrong here
SQL Server on Azure Virtual Machine is a lift-and-shift IaaS option where you manage the operating system, SQL Server installation, patching, high availability, and licensing. You cannot use Azure SQL Database elastic pools with it; instead, you would need to manually build resource-sharing mechanisms, such as a cluster of VMs and SQL Server Availability Groups, and still each VM has a fixed number of vCPUs and memory that must be over-provisioned for peak. The administrative burden and lack of native elastic resource sharing across tenant databases makes this unsuitable for a multi-tenant SaaS cost-optimization goal.
When this WOULD be correct
This option is correct when the question specifies a need for full SQL Server instance-level control, custom OS configurations, or legacy application compatibility that cannot be met by PaaS offerings, such as requiring SQL Server Agent jobs, CLR integration, or specific Windows features.
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.
✓Azure SQL Database Elastic PoolCorrect answer▾
Why this is correct
An elastic pool allows multiple databases to share a pool of resources. Databases automatically use resources as needed, maximizing utilization and lowering cost while providing predictable performance per database via settings like min and max vCores.
✗Azure SQL Database Single DatabaseWrong answer — click to see why▾
Why this is wrong here
Single Database does not allow pooling compute resources across tenants; each database is isolated with its own DTU/vCore allocation, leading to underutilization and higher costs for variable, small workloads.
★ When this WOULD be the correct answer
A question where each tenant requires guaranteed, isolated performance with no resource sharing, such as a financial application with strict compliance requiring separate performance tiers per database.
Why candidates choose this
Candidates may think 'separate database' means Single Database is the natural choice, overlooking Elastic Pool's ability to share resources across multiple databases for cost efficiency.
✗Azure SQL Managed InstanceWrong answer — click to see why▾
Why this is wrong here
Azure SQL Managed Instance provides near 100% SQL Server compatibility and is designed for lift-and-shift migrations, not for pooling compute resources across multiple small databases with variable workloads. It does not offer the elastic pooling capability to share resources among tenants.
★ When this WOULD be the correct answer
A company needs to migrate an existing on-premises SQL Server application to Azure with minimal changes, requiring high compatibility with SQL Server features like SQL Agent, CLR, or cross-database queries, and does not need to pool resources across databases.
Why candidates choose this
Candidates may think Managed Instance is a good middle ground between single databases and VMs, but they overlook that it lacks the elastic pool feature for resource sharing, which is key for multi-tenant cost optimization.
✗SQL Server on Azure Virtual MachineWrong answer — click to see why▾
Why this is wrong here
SQL Server on Azure VM requires manual management of compute resources and does not provide built-in multi-tenant pooling or elastic scaling across databases. It also incurs higher operational overhead and cost for small, variable workloads compared to an elastic pool.
★ When this WOULD be the correct answer
This option is correct when the question specifies a need for full SQL Server instance-level control, custom OS configurations, or legacy application compatibility that cannot be met by PaaS offerings, such as requiring SQL Server Agent jobs, CLR integration, or specific Windows features.
Why candidates choose this
Candidates may think that running SQL Server on a VM offers maximum flexibility and control, and might assume it can be configured to pool resources across tenants, overlooking the management overhead and lack of built-in elastic pooling features.
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
About these practice questions
Courseiva writes every DP-900 question from scratch — 820 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-900 exam.