DP-900 Practice Question: Identify considerations for relational data on Azure
Which TWO are benefits of using Azure SQL Database elastic pools?
⚠ Common exam trap
It's easy for candidates to confuse elastic pools with single databases, assuming they provide unlimited storage or isolated performance, but the core benefit is cost-effective resource sharing across multiple databases with predictable pricing.
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
✓
Predictable pricing for a group of databases
Azure SQL Database elastic pools provide predictable pricing because you pay for a fixed set of resources (eDTUs or vCores) allocated to the pool, regardless of how many databases use them. This allows you to budget for a group of databases with variable usage patterns without incurring per-database costs, making it cost-effective for workloads with intermittent or unpredictable demand.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Predictable pricing for a group of databases
Why this is correct
An Azure SQL Database elastic pool bills a single fixed price for a shared pool of eDTUs or vCores, regardless of how much each contained database consumes. This makes monthly costs predictable because you pay for the pool capacity, not per-database usage spikes.
- ✓
Resource sharing across multiple databases
Why this is correct
Elastic pools allow multiple databases to consume a common set of compute and storage resources, so one database can use idle capacity from another during its peak load. This sharing maximizes resource utilization and reduces the need to provision each database for its individual maximum demand.
- ✗
Unlimited storage per database
Why it's wrong here
Contrary to a benefit, an elastic pool imposes a maximum size limit per database, which in the DTU purchasing model is typically 1 TB for Standard and Premium tiers. You cannot store unlimited data; the per-database limit is capped even though the pool aggregates storage across all databases.
- ✗
Isolated performance for each database
Why it's wrong here
Because elastic pools are explicitly designed for shared resource usage, they do not provide per-database performance isolation. A burst of activity in one database can consume common CPU or I/O capacity and degrade performance for other databases in the same pool, so isolated performance is not achievable.
- ✗
Support for databases over 1 TB each
Why it's wrong here
Elastic pools are not marketed as a way to support databases larger than 1 TB; in fact, the standard per-database maximum size for DTU-based elastic pools is 1 TB. The tooling for larger single databases is the Single Database or Managed Instance service, not a typical benefit you'd associate with pooling.
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.