DP-900 Practice Question: Identify considerations for relational data on Azure

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Hyperscale

  Why it's wrong here

  Hyperscale is a service tier designed for very large databases that need massive storage capacity and high throughput, using a distributed architecture that separates compute, storage, and log. However, it is a provisioned compute tier: you are billed by the hour for a fixed number of vCores and the tier does not support automatic pausing or per-second metering of compute. For a customer-facing app with variable demand, it would keep compute running 24/7, leading to unnecessary cost when usage is low.

  When this WOULD be correct

  A company has a database exceeding 4 TB, requires fast scaling for high concurrency workloads, and needs read scale-out with multiple readable replicas. Hyperscale would be correct for such large-scale, high-performance requirements.

• ✓

  Serverless

  Why this is correct

  The Serverless compute tier for Azure SQL Database dynamically scales compute resources between a minimum and maximum vCore range and automatically pauses an idle database—typically after one hour of inactivity—while billing only for the vCores consumed per second. This model is ideal for intermittent, variable workloads where demand fluctuates unpredictably, as it eliminates the cost of maintaining idle capacity. Unlike the other provisioned tiers, it does not charge for compute when paused, only for storage.

• ✗

  Provisioned (General Purpose)

  Why it's wrong here

  The Provisioned (General Purpose) tier is a traditional, fixed-compute option for Azure SQL Database that offers predictable performance and is billed by the hour, independent of actual utilization. It lacks the ability to automatically scale compute up or down in response to demand and cannot be paused during periods of inactivity. Because the customer-facing application experiences variable usage peaks and valleys, this tier would incur consistent costs even when the app is idle, making it less cost-effective than a serverless compute model.

  When this WOULD be correct

  A company needs predictable performance for a production database with consistent workloads, requires manual scaling control, and does not need the ability to pause; they want a balance of compute and storage at a lower cost than Business Critical.

• ✗

  Business Critical

  Why it's wrong here

  Business Critical is a provisioned tier built for mission-critical workloads requiring high availability (multiple replicas), low-latency writes, and in-memory OLTP, but it comes with a premium hourly cost and fixed compute resources. It does not auto-scale compute based on demand nor does it pause when inactive, so for a workload that is only intermittently used, you would be paying for reserved capacity that may sit idle. Although it delivers high performance, it is an over-engineered and cost-prohibitive choice for a variable, customer-facing web app.

  When this WOULD be correct

  A question where the requirements include the highest resilience to failures, fast failover, and minimal performance impact during maintenance, such as a mission-critical OLTP application with strict SLA requirements for availability and latency.

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.

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