DP-900 Practice Question: Identify considerations for relational data on Azure
An e-commerce company has 20 SQL Server databases that each range from 10 GB to 50 GB and experience unpredictable usage patterns with occasional spikes in user activity. The company wants to migrate to Azure SQL Database to reduce management overhead and minimize costs by allowing databases to share resources. Which Azure SQL Database deployment option should they choose?
⚠ Common exam trap
Many candidates confuse 'reducing management overhead' with choosing a fully managed option like Managed Instance, but fail to recognize that the key requirement is 'sharing resources to minimize costs,' which is uniquely addressed by elastic pools, not by single databases or instance-level offerings.
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 SQL databases to share a fixed set of resources (eDTUs or vCores), which is ideal for databases with unpredictable usage patterns and occasional spikes. By pooling resources, the company can reduce management overhead and minimize costs compared to provisioning each database individually, as the pool's total resources are shared among all databases, smoothing out peak demands.
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
Why it's wrong here
A single database with provisioned throughput gives each database its own guaranteed allotment of DTUs or vCores, and that allotment is fixed for the size you select. Because the resources are dedicated per database, you must size each one for its maximum expected workload, even if the average utilization is low and spikes are rare. This approach multiplies cost across many databases and does not allow idle capacity from one database to be consumed by a busy sibling on the same logical server, making it far less efficient than an elastic pool for your workload.
When this WOULD be correct
A single database with provisioned throughput is correct when a company has one large database (e.g., >500 GB) with predictable, steady-state usage and requires guaranteed performance isolation without sharing resources with other databases.
- ✓
B: Elastic pool
Why this is correct
An elastic pool allocates a shared set of vCores/eDTUs to multiple Azure SQL databases that reside on the same logical server. Databases can consume extra resources as needed up to a configured per-database cap, while idle databases automatically release unused capacity back to the pool. This shared capacity model is ideal for 20 databases with unpredictable usage because you pay for the aggregate demand of the pool rather than the sum of each database's individual peak, dramatically reducing cost.
- ✗
C: Managed Instance
Why it's wrong here
Managed Instance provides near-100% compatibility with on-premises SQL Server features, but it does not support the elastic pooling of resources across multiple databases. The scenario requires databases to share resources to minimise costs, which only the elastic pool model within a single logical server can achieve. Managed Instance is tempting because it reduces management overhead and offers full instance-scope compatibility, making it correct for lift-and-shift migrations needing high feature parity without resource sharing.
When this WOULD be correct
A company needs to migrate multiple on-premises SQL Server databases to Azure with minimal application changes, requiring features like SQL Agent, cross-database queries, and VNet integration, and is willing to pay for dedicated resources rather than sharing.
- ✗
D: SQL Server on Azure VM
Why it's wrong here
SQL Server on Azure VM is an IaaS offering where you have full control over a dedicated Windows/Linux VM and the SQL Server instance installed inside it. You remain responsible for patching the OS and SQL Server, managing licenses, and sizing the VM to handle peak load, which means you either over-provision for bursts or accept throttling during heavy activity. This model does not provide built-in elastic pooling or automatic resource sharing across databases; any sharing would require manual consolidation and still be constrained to the fixed CPU, memory, and disk resources of that one VM.
When this WOULD be correct
A company needs full control over the SQL Server environment, requires custom configurations or third-party software, or must lift-and-shift existing applications with minimal changes, and is willing to manage the VM.
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
An elastic pool allocates a shared set of vCores/eDTUs to multiple Azure SQL databases that reside on the same logical server. Databases can consume extra resources as needed up to a configured per-database cap, while idle databases automatically release unused capacity back to the pool. This shared capacity model is ideal for 20 databases with unpredictable usage because you pay for the aggregate demand of the pool rather than the sum of each database's individual peak, dramatically reducing cost.
✗A: Single database with provisioned throughputWrong answer — click to see why▾
Why this is wrong here
Single database with provisioned throughput does not allow databases to share resources or minimize costs for unpredictable, spiky workloads across multiple databases. Each database is isolated with dedicated resources, leading to over-provisioning and higher costs.
★ When this WOULD be the correct answer
A single database with provisioned throughput is correct when a company has one large database (e.g., >500 GB) with predictable, steady-state usage and requires guaranteed performance isolation without sharing resources with other databases.
Why candidates choose this
Candidates may think 'single database' is simpler and cheaper, but they overlook the requirement for multiple databases to share resources and handle unpredictable spikes cost-effectively.
✗C: Managed InstanceWrong answer — click to see why▾
Why this is wrong here
Azure SQL Managed Instance is designed for lift-and-shift migrations requiring near 100% compatibility with on-premises SQL Server, but it does not support resource sharing across multiple databases via elastic pools, so it would not minimize costs for unpredictable, shared workloads.
★ When this WOULD be the correct answer
A company needs to migrate multiple on-premises SQL Server databases to Azure with minimal application changes, requiring features like SQL Agent, cross-database queries, and VNet integration, and is willing to pay for dedicated resources rather than sharing.
Why candidates choose this
Candidates may confuse Managed Instance as a 'managed' option that reduces overhead, but overlook that it lacks elastic pool support and is more expensive for databases with variable usage that could share resources.
✗D: SQL Server on Azure VMWrong answer — click to see why▾
Why this is wrong here
SQL Server on Azure VM requires manual management of the OS and SQL Server, including patching and backups, which does not reduce management overhead. It also cannot share resources across databases to minimize costs like an elastic pool.
★ When this WOULD be the correct answer
A company needs full control over the SQL Server environment, requires custom configurations or third-party software, or must lift-and-shift existing applications with minimal changes, and is willing to manage the VM.
Why candidates choose this
Candidates may think that migrating to a VM is the simplest lift-and-shift approach, overlooking the management overhead and the lack of resource sharing for cost optimization.
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
This DP-900 question is part of Courseiva's 820-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.