How to Guarantee Minimum Resources for a Critical Database in an Elastic Pool
You have an Azure SQL Database that is part of an elastic pool. You notice that the pool's eDTU consumption is consistently high, and some databases are experiencing resource contention. You need to ensure that a critical database always gets a minimum amount of resources. What should you configure?
Quick Answer
The answer is to configure per-database min eDTU for the critical database. This setting guarantees a baseline level of resources by reserving a specific amount of eDTU for that database, even when the elastic pool is under high contention, ensuring it never starves for compute or IO. In contrast, per-database max eDTU only caps usage, and simply increasing the pool’s total DTU does not guarantee any single database gets those resources. On the DP-300 exam, this scenario tests your understanding of resource governance within elastic pools, where the common trap is confusing min (guarantee) with max (limit). A memory tip: think of “min” as a floor that holds up your critical database, while “max” is a ceiling that holds it back.
⚠ Common exam trap
DP-300 often tests the confusion between min and max eDTU settings — candidates see 'minimum amount of resources' and incorrectly pick max eDTU, forgetting that max is a ceiling, not a floor.
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
✓
Configure per-database min eDTU for the critical database
In an Azure SQL elastic pool, per-database min eDTU (or min vCore) guarantees a floor of resources that a specific database can always consume, even when other databases in the pool are competing for resources. Setting a min eDTU on the critical database ensures it is never starved during contention. This directly addresses the requirement that the critical database 'always gets a minimum amount of resources.'
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure per-database max eDTU for the critical database
Why it's wrong here
Per-database max eDTU caps consumption; it sets no floor, so the critical database can still be starved when the pool is contended. It is tempting because it does govern resource allocation within a pool, and would be correct to prevent one database from monopolising shared eDTUs.
- ✗
Increase the eDTU of the elastic pool
Why it's wrong here
Raising pool eDTUs lifts the ceiling for every database collectively, but contention persists because no per-database minimum is enforced. It is tempting because scaling the pool genuinely relieves aggregate pressure when all members are uniformly busy; it would be correct if the pool, rather than one database, needed more total capacity.
- ✗
Move the critical database to a dedicated service tier
Why it's wrong here
A dedicated tier removes the database from the pool entirely, so it no longer shares eDTUs, but the requirement is a guaranteed minimum within the pool, which per-database minimum eDTUs deliver. Dedicated tiers suit workloads needing isolated, predictable compute independent of pool neighbours.
- ✓
Configure per-database min eDTU for the critical database
Why this is correct
Per-database min eDTU guarantees the critical database a reserved floor of resources within the elastic pool, so contention from other databases cannot starve it. This directly satisfies the requirement that the critical database always receives a minimum amount of resources.
Go deeper
Related to this question
Learn chapter
Managing Environment Configurations and Resource Governance
Key term
Azure SQL Performance Tuning
Azure SQL Performance Tuning is the process of optimizing the speed and efficiency of queries and database operations in Microsoft Azure SQL Database or SQL Managed Instance to reduce latency and improve throughput.
About these practice questions
One of 574 original DP-300 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 →
Same concept, more angles
1 more way this is tested on DP-300
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Your organization uses Azure SQL Database with elastic pools. One of the databases in the pool, 'OrdersDB', consistently uses more eDTUs than other databases, causing performance degradation for other databases. You need to isolate the resource usage of 'OrdersDB' to prevent it from affecting others. The solution should minimize cost and administrative overhead. What should you do?
hard- A.Purchase reserved capacity for the pool to reduce costs.
- B.Use Query Store to identify and kill the high-usage queries.
- ✓ C.Move 'OrdersDB' to a higher service tier, such as a standalone database with a higher DTU limit.
- D.Increase the eDTU limit of the elastic pool to accommodate the high usage.
Why C: Moving 'OrdersDB' to a standalone database with a higher DTU limit isolates its resource usage, preventing it from consuming eDTUs from the elastic pool and affecting other databases. This minimizes cost and administrative overhead because you only pay for the resources that 'OrdersDB' needs, and you avoid over-provisioning the entire pool.
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This DP-300 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-300 exam.