DP-300 Plan and implement data platform resources Practice Question
Your company is deploying a multi-tenant application using Azure SQL Database. Each tenant gets its own database. You need to manage resources efficiently while ensuring performance isolation between tenants. The number of tenants fluctuates, and you want to minimize cost. What is the best strategy?
⚠ Common exam trap
Many exam-takers confuse 'performance isolation' with 'dedicated resources' and choose single databases (Option A), not realizing that elastic pools provide isolation via per-database resource caps while sharing a common pool for cost efficiency.
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
✓
Use an elastic pool and add databases as needed
Elastic pools are designed for multi-tenant SaaS scenarios where each tenant has its own database but usage patterns are unpredictable. They provide performance isolation through per-database resource limits (e.g., min/max DTUs or vCores) while sharing a fixed pool of resources, which minimizes cost by allowing idle databases to borrow from others. This matches the requirement of fluctuating tenant counts and cost efficiency.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Deploy each tenant's database as a single database with reserved capacity
Why it's wrong here
A single database with reserved capacity provisions fixed vCores per tenant, so fluctuating tenant counts waste spend and cannot scale elastically. It is tempting because reserved capacity suits stable, predictable single-database workloads, but the stem's requirement for cost minimisation under fluctuating tenants points to elastic pools sharing resources.
- ✗
Use a single Hyperscale database with schema per tenant
Why it's wrong here
Schema-per-tenant in one Hyperscale database shares its compute and storage, so a noisy tenant degrades every other tenant; performance isolation is lost. Hyperscale suits a single very large database needing rapid scale-out, not fluctuating multi-tenant estates where elastic pools isolate workloads per database at lower cost.
- ✗
Use a single Azure SQL Managed Instance with multiple databases
Why it's wrong here
A single managed instance pools all tenant databases onto shared compute, so one tenant's load consumes resources others need, defeating performance isolation. It is tempting because instance-level consolidation reduces licensing and management overhead when isolation is not required.
- ✓
Use an elastic pool and add databases as needed
Why this is correct
Elastic pools share provisioned eDTUs or vCores across databases, so fluctuating tenant counts consume pooled resources rather than per-database minimums. This satisfies cost minimisation while performance isolation is maintained because each tenant retains its own database.
Go deeper
Related to this question
Learn chapter
Optimizing Database Query and Index Performance
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
This DP-300 question is part of Courseiva's 574-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-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.