DP-900 Practice Question: Identify considerations for relational data on Azure
A company has 15 SQL Server databases, ranging from 50 GB to 200 GB each. The databases experience unpredictable load spikes during the day. They want to migrate to Azure SQL Database to minimize management overhead and reduce costs by allowing databases to share resources, while ensuring each database can burst to higher performance when needed. Which deployment option should they choose?
⚠ Common exam trap
Many exam-takers confuse SQL Managed Instance's high compatibility with the ability to share resources, but Managed Instance does not support elastic pools and instead allocates dedicated resources per instance, making it unsuitable for cost-efficient resource sharing and bursting across multiple 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
✓
B) Elastic pool
Elastic pools allow multiple databases to share a fixed pool of resources (DTUs or vCores), which reduces costs by pooling unused capacity and enables each database to automatically burst to higher performance when needed. This matches the company's need to minimize management overhead while handling unpredictable load spikes across 15 databases ranging from 50 GB to 200 GB.
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) Single database with Provisioned throughput tier
Why it's wrong here
A single database with the provisioned throughput tier is wrong because each database is allocated a fixed set of dedicated resources (e.g., DTUs or vCores) that cannot be shared with other databases, even when they are idle. For 15 databases with unpredictable load patterns, you would have to provision every database for its own peak demand, resulting in substantial underutilization and higher total cost compared to pooling resources. The isolated resource model does not allow burst traffic in one database to consume spare capacity from other databases, which is exactly the efficiency that elastic pools were designed to deliver.
When this WOULD be correct
A scenario where a single database requires predictable, dedicated performance with no need for resource sharing among multiple databases, and the workload is stable without unpredictable spikes, making a single database with Provisioned throughput tier appropriate.
- ✓
B) Elastic pool
Why this is correct
Elastic pool is correct because it aggregates compute and storage resources across the 15 databases, letting each database automatically consume up to the pool's configured limit during demand spikes. Under the vCore or DTU purchasing models, you pay for the pool's total resource ceiling, not per-database provisioning, which is ideal for workloads like these that are unpredictable but whose peaks do not align across all databases. This shared-resource model keeps costs lower while still guaranteeing a minimum performance level for every database through per-database min/max settings.
- ✗
C) SQL Managed Instance
Why it's wrong here
Incorrect. SQL Managed Instance provides near-100% compatibility with on-premises SQL Server and a fixed set of resources for the entire instance, not per database. It does not offer the resource sharing and burst flexibility of an elastic pool.
When this WOULD be correct
A company needs to migrate multiple SQL Server databases to Azure with minimal application changes, requiring high compatibility with on-premises features like SQL Agent, CLR, or cross-database queries. They have predictable workloads and do not need resource sharing or bursting across databases.
- ✗
D) SQL Server on Azure Virtual Machine
Why it's wrong here
SQL Server on Azure Virtual Machine (IaaS) is wrong for this scenario because it forces you to manage the underlying VM, operating system, SQL Server binaries, patching, and backups yourself, adding significant administrative overhead. You must size each VM to handle the peak load of its individual database, which across 15 databases of 50–200 GB leads to over-provisioning and idle capacity when workloads are bursty. While it offers near-full SQL Server compatibility and OS-level control, it lacks the PaaS-level automatic resource sharing and elastic scaling that an elastic pool provides.
When this WOULD be correct
A company needs full control over the SQL Server environment, including custom configurations, third-party tools, or legacy dependencies that are incompatible with PaaS offerings. They also require OS-level access for specific compliance or performance tuning.
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.
✓B) Elastic poolCorrect answer▾
Why this is correct
Elastic pool is correct because it aggregates compute and storage resources across the 15 databases, letting each database automatically consume up to the pool's configured limit during demand spikes. Under the vCore or DTU purchasing models, you pay for the pool's total resource ceiling, not per-database provisioning, which is ideal for workloads like these that are unpredictable but whose peaks do not align across all databases. This shared-resource model keeps costs lower while still guaranteeing a minimum performance level for every database through per-database min/max settings.
✗A) Single database with Provisioned throughput tierWrong answer — click to see why▾
Why this is wrong here
Single database with Provisioned throughput tier does not allow databases to share resources or enable bursting to higher performance without manual scaling; it isolates each database to its own fixed resources, increasing costs and management overhead.
★ When this WOULD be the correct answer
A scenario where a single database requires predictable, dedicated performance with no need for resource sharing among multiple databases, and the workload is stable without unpredictable spikes, making a single database with Provisioned throughput tier appropriate.
Why candidates choose this
Candidates may think 'Provisioned throughput' implies guaranteed performance for spikes, but they overlook the need for resource sharing and cost efficiency across multiple databases with variable loads.
✗C) SQL Managed InstanceWrong answer — click to see why▾
Why this is wrong here
SQL Managed Instance is designed for lift-and-shift migrations requiring near 100% compatibility with on-premises SQL Server, not for sharing resources across multiple databases with elastic bursting. It does not support elastic pools, so each database would have dedicated resources, increasing cost and management overhead.
★ When this WOULD be the correct answer
A company needs to migrate multiple SQL Server databases to Azure with minimal application changes, requiring high compatibility with on-premises features like SQL Agent, CLR, or cross-database queries. They have predictable workloads and do not need resource sharing or bursting across databases.
Why candidates choose this
Candidates may confuse SQL Managed Instance as a 'managed' option that reduces overhead, but they overlook that it does not support elastic pooling for resource sharing and bursting, which is the key requirement here.
✗D) SQL Server on Azure Virtual MachineWrong answer — click to see why▾
Why this is wrong here
SQL Server on Azure VMs requires manual management of OS, SQL Server, and scaling, which contradicts the goal of minimizing management overhead. It also cannot share resources across databases or provide elastic bursting without manual intervention.
★ 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 dependencies that are incompatible with PaaS offerings. They also require OS-level access for specific compliance or performance tuning.
Why candidates choose this
Candidates may think that running SQL Server on a VM offers more flexibility for unpredictable loads, but they overlook the management overhead and lack of built-in resource sharing and bursting capabilities compared to Elastic Pool.
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.