DP-900 Practice Question: Identify considerations for relational data on Azure
A company is migrating a relational database to Azure SQL Database. They anticipate that the amount of stored data will grow significantly over time, but the compute requirements (CPU and memory) will remain relatively stable. Which purchasing model should they choose to allow independent scaling of storage and compute?
⚠ Common exam trap
Test-takers frequently confuse purchasing models (DTU vs. vCore) with service tiers (Hyperscale) or compute options (Serverless), leading candidates to pick Hyperscale or Serverless when the question specifically asks for a purchasing model that allows independent scaling of storage and compute.
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
✓
vCore-based purchasing model
The vCore-based purchasing model separates compute and storage costs, allowing you to scale storage independently without changing compute resources. This matches the scenario where data grows but compute requirements remain stable, as you can increase storage capacity without upgrading CPU or memory.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
DTU-based purchasing model
Why it's wrong here
The DTU-based model bundles compute, storage, and I/O into a fixed unit called a database transaction unit, so storage cannot be scaled independently. Increasing storage requires moving to a higher service tier or objective, which also increases the bundled compute and I/O resources whether you need them or not. That makes it the wrong choice when storage is the only thing that must scale.
When this WOULD be correct
A company with predictable, stable workloads wants a simple, pre-configured purchasing model that bundles compute and storage at a fixed price, without the need to manage separate resources.
- ✓
vCore-based purchasing model
Why this is correct
The vCore-based purchasing model meters compute and storage separately, so you can scale database storage independently of the number of allocated vCores. For a migration, this means you can increase or decrease storage capacity without purchasing additional compute, giving granular cost control and flexibility that a bundled model cannot provide.
- ✗
Serverless compute tier
Why it's wrong here
The serverless compute tier automatically scales the compute resources up or down and can pause a database during idle periods, but it is not a mechanism for scaling storage on demand. Storage is still provisioned as part of the database, and because the tier is focused on compute elasticity, it does not provide the general-purpose separation of storage billing that the vCore model gives you. The wrongness here is conflating compute auto-scaling with storage independence.
When this WOULD be correct
A correct scenario would be: 'A company has a database with sporadic, unpredictable usage patterns (e.g., occasional bursts of activity) and wants to pay only for compute used, with automatic pause during inactivity. Which purchasing model should they choose?'
- ✗
Hyperscale service tier
Why it's wrong here
Hyperscale is a service tier, not a purchasing model, and although it is built on the vCore architecture, its defining feature is near-instant scaling to massive database sizes through a decoupled storage engine. The question is about the purchasing model that enables independent storage scaling generally; Hyperscale applies that flexibility only to very large workloads and still sits on top of vCore. Choosing it would confuse a service tier with the billing model underneath it.
When this WOULD be correct
A company needs a database that can automatically scale storage up to 100 TB and handle very high transaction rates with fast backup and restore. They expect unpredictable growth in both storage and compute, and they want to offload storage management. In this scenario, Hyperscale would be the correct choice because it provides near-instant scaling of compute and storage without manual intervention.
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.
✓vCore-based purchasing modelCorrect answer▾
Why this is correct
The vCore-based purchasing model meters compute and storage separately, so you can scale database storage independently of the number of allocated vCores. For a migration, this means you can increase or decrease storage capacity without purchasing additional compute, giving granular cost control and flexibility that a bundled model cannot provide.
✗DTU-based purchasing modelWrong answer — click to see why▾
Why this is wrong here
The DTU-based model bundles compute and storage into fixed tiers, so scaling storage requires scaling compute as well, which does not meet the requirement for independent scaling.
★ When this WOULD be the correct answer
A company with predictable, stable workloads wants a simple, pre-configured purchasing model that bundles compute and storage at a fixed price, without the need to manage separate resources.
Why candidates choose this
Candidates may confuse DTU with vCore, thinking DTU also allows separate scaling, or they may recall that DTU is commonly used for Azure SQL Database without understanding its limitations.
✗Serverless compute tierWrong answer — click to see why▾
Why this is wrong here
The serverless compute tier is designed for databases with intermittent, unpredictable usage patterns, not for scenarios where compute requirements remain stable. It does not allow independent scaling of storage and compute; compute scales automatically based on workload, but storage scaling is limited and not independent.
★ When this WOULD be the correct answer
A correct scenario would be: 'A company has a database with sporadic, unpredictable usage patterns (e.g., occasional bursts of activity) and wants to pay only for compute used, with automatic pause during inactivity. Which purchasing model should they choose?'
Why candidates choose this
Candidates may confuse 'serverless' with the ability to scale components independently, or they may think that serverless automatically handles scaling of both compute and storage separately, not realizing that storage scaling is limited and compute scaling is automatic based on demand, not independent.
✗Hyperscale service tierWrong answer — click to see why▾
Why this is wrong here
The Hyperscale service tier is designed for databases that require high scalability in storage and compute, but it does not allow independent scaling of storage and compute; instead, it provides a flexible architecture where compute nodes can be scaled independently, but storage is automatically managed and scales with compute. The question specifically asks for a model that allows independent scaling of storage and compute, which is a feature of the vCore-based model, not Hyperscale.
★ When this WOULD be the correct answer
A company needs a database that can automatically scale storage up to 100 TB and handle very high transaction rates with fast backup and restore. They expect unpredictable growth in both storage and compute, and they want to offload storage management. In this scenario, Hyperscale would be the correct choice because it provides near-instant scaling of compute and storage without manual intervention.
Why candidates choose this
Candidates may confuse Hyperscale's ability to scale compute nodes independently with the vCore model's separate scaling of storage and compute. The term 'Hyperscale' implies extreme scalability, leading them to think it allows independent scaling of storage and compute, but in reality, storage is automatically managed and not independently scalable.
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
Learn chapter
Data Roles and Core Concepts
Key term
Azure SQL Database
Azure SQL Database is a fully managed relational database-as-a-service (DBaaS) in Microsoft Azure, based on the SQL Server engine, that handles scaling, backups, patching, and high availability automatically.
Key term
Relational database
A relational database organizes data into tables with rows and columns, where each table relates to others using unique keys, allowing efficient storage, retrieval, and manipulation of structured information.
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.