DP-900 Practice Question: Identify considerations for relational data on Azure
A company has 12 SQL Server databases, each about 30 GB. The databases experience unpredictable load spikes during the day. The company wants to migrate to Azure SQL Database to reduce administrative overhead and optimize costs by sharing resources among the databases. Which deployment option should they choose?
⚠ Common exam trap
Test-takers frequently choose Single Database (Option A) thinking it is simpler, but they miss that elastic pools are specifically designed for cost optimization when multiple databases have variable and overlapping load patterns, not for isolated workloads.
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
✓
Elastic pool
Elastic pools are designed to share resources (eDTUs or eVCores) among multiple databases with unpredictable, overlapping load spikes. By pooling resources, the company can optimize costs because databases do not all peak simultaneously, and the pool’s total resource allocation is lower than the sum of individual peak requirements. This reduces administrative overhead by providing a single management point for scaling and monitoring all databases in the pool.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Single database with provisioned DTU
Why it's wrong here
Deploying each of the 12 databases as a single database with provisioned DTUs forces you to choose a DTU tier (e.g., S0, S1) for every database independently, and each database is billed for its guaranteed DTU capacity whether or not it is actively used. If some databases spike, you must provision each for peak load, leading to a total cost that is the sum of all individual DTUs—far higher than a shared pool that only needs capacity for the peak of the combined workload. The lack of resource multiplexing across single databases makes this option wasteful for fluctuating usage patterns.
When this WOULD be correct
A company needs a single database with predictable performance requirements and wants isolated resources without sharing, or when the database size exceeds the elastic pool limits.
- ✓
Elastic pool
Why this is correct
Elastic pools in Azure SQL Database allocate a shared set of eDTUs or vCores across multiple databases, so the 12 ~30 GB databases can collectively use resources without each being provisioned for peak demand. Because workload spikes are typically unsynchronized, the pool absorbs them with a small total compute footprint, and per-database min/max DTU or vCore settings let you control resource sharing. This shared billing makes it the most cost-effective and administratively simple choice for many similarly sized databases.
- ✗
Managed Instance
Why it's wrong here
Azure SQL Managed Instance provides a fully managed SQL Server instance where every database consumes the instance's fixed compute and storage resources; there is no mechanism to pool capacity across separate instances or to elastically borrow unused resources between databases. You would be paying for an entire instance (e.g., at least 8 vCores) to host only 30 GB databases, and you'd have to manually consolidate them into one instance while still sizing for peak aggregate load. Its rich instance-scoped features—like linked servers and SQL Agent—do not justify this over-provisioning for this specific DTU-style workload.
When this WOULD be correct
A company needs to migrate multiple on-premises SQL Server databases with minimal changes, requiring instance-scoped features like SQL Agent, cross-database queries, or Service Broker, and is willing to pay for dedicated resources rather than sharing them.
- ✗
SQL Server on Azure Virtual Machine
Why it's wrong here
SQL Server on Azure Virtual Machines gives you full control over the OS and SQL Server, but it is an IaaS offering where you pay for the VM's compute, storage, and licensing regardless of actual database utilization. You would need to deploy a large VM to handle worst-case concurrent workloads across all 12 databases, and you're responsible for patching, backups, and high availability—none of which provide automatic resource sharing or elastic scaling between databases. This approach is operationally heavy and cost-inefficient when the goal is simply to host small, sporadically used databases.
When this WOULD be correct
A company needs full control over the SQL Server environment, including custom configurations, third-party tools, or legacy applications that require OS-level access. They also have predictable workloads and are willing to manage the underlying infrastructure to minimize costs.
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.
✓Elastic poolCorrect answer▾
Why this is correct
Elastic pools in Azure SQL Database allocate a shared set of eDTUs or vCores across multiple databases, so the 12 ~30 GB databases can collectively use resources without each being provisioned for peak demand. Because workload spikes are typically unsynchronized, the pool absorbs them with a small total compute footprint, and per-database min/max DTU or vCore settings let you control resource sharing. This shared billing makes it the most cost-effective and administratively simple choice for many similarly sized databases.
✗Single database with provisioned DTUWrong answer — click to see why▾
Why this is wrong here
Single database with provisioned DTU does not allow sharing of resources among databases, so it would not optimize costs for unpredictable load spikes across multiple databases.
★ When this WOULD be the correct answer
A company needs a single database with predictable performance requirements and wants isolated resources without sharing, or when the database size exceeds the elastic pool limits.
Why candidates choose this
Candidates may think single database is simpler and still cost-effective, but they overlook the benefit of resource pooling for variable workloads.
✗Managed InstanceWrong answer — click to see why▾
Why this is wrong here
Managed Instance is designed for lift-and-shift migrations requiring full SQL Server instance-level features, not for sharing resources among multiple databases to optimize cost. It does not provide the elastic pooling capability needed for unpredictable load spikes across databases.
★ When this WOULD be the correct answer
A company needs to migrate multiple on-premises SQL Server databases with minimal changes, requiring instance-scoped features like SQL Agent, cross-database queries, or Service Broker, and is willing to pay for dedicated resources rather than sharing them.
Why candidates choose this
Candidates may think Managed Instance offers better compatibility and performance for multiple databases, but overlook that it lacks the cost-efficient resource sharing of elastic pools for variable workloads.
✗SQL Server on Azure Virtual MachineWrong answer — click to see why▾
Why this is wrong here
SQL Server on Azure Virtual Machine requires manual patching, backups, and scaling, which increases administrative overhead. It does not provide resource sharing among databases, as each VM runs its own SQL Server instance, leading to higher costs and less efficient resource utilization compared to an elastic pool.
★ When this WOULD be the correct answer
A company needs full control over the SQL Server environment, including custom configurations, third-party tools, or legacy applications that require OS-level access. They also have predictable workloads and are willing to manage the underlying infrastructure to minimize costs.
Why candidates choose this
Candidates may think that migrating to Azure VMs is the simplest lift-and-shift approach, overlooking the administrative overhead and cost inefficiencies for databases with variable loads.
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
One of 820 original DP-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.