Courseiva

DP-900 Practice Question: Describe considerations for working with non-relational data on Azure

Match each Azure SQL Database tier to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Low-cost for small workloads

Balanced performance and cost

High performance and low latency

Highly scalable for large databases

Auto-scaling compute based on demand

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

Basic: For low-cost, small-scale workloads with limited performance needs

Azure SQL Database tiers: Basic (low-cost, small), Standard (mid-range, predictable), Premium (high-performance, mission-critical), Hyperscale (large, scalable). Common confusions: mixing Premium and Basic, or Standard and Hyperscale.

Answer analysis

Option-by-option breakdown

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

  • Basic: For low-cost, small-scale workloads with limited performance needs

    Why this is correct

    Basic Azure SQL Database tier is a DTU-based service tier designed for small databases (up to 2 GB) with light, intermittent workloads. It offers 5 DTUs, restricted performance, and low cost, making it ideal for development, testing, or small applications. It is not meant for high concurrency or heavy I/O, but provides the essential Azure SQL functionality at minimal price.

  • Standard: For mid-range workloads with predictable performance and built-in high availability

    Why this is correct

    Standard is a DTU-based tier for mid-range workloads that require predictable performance, such as line-of-business applications. It offers provisioned DTUs (S0–S12) and built-in high availability with a 99.99% SLA, along with geo-restore and point-in-time restore options. This tier balances cost, storage (up to 1 TB on higher S-levels), and performance for typical production workloads that don't demand low single-digit-millisecond latency.

  • Premium: For high-performance, mission-critical workloads with low latency and high throughput

    Why this is correct

    Premium is a DTU-based tier built for mission-critical workloads that demand low I/O latency, high throughput, and high availability. It uses SSD storage, supports in-memory OLTP, and can include multiple read replicas, yielding higher DTUs (up to 4000) and up to 4 TB storage. This tier is chosen for applications with strict performance and availability SLAs, such as real-time transactional systems.

  • Hyperscale: For extremely large databases and high scalability with rapid provisioning

    Why this is correct

    Hyperscale is a vCore-based service tier designed for very large databases up to 100 TB, with near-instant scaling of compute and storage without downtime. It uses a cloud-native architecture where storage and compute are separated, and you can add/remove replicas quickly for rapid provisioning. This tier suits large BI, ERP, or any workload requiring extreme scalability and performance.

  • Basic: For high-performance, mission-critical workloads with low latency

    Why it's wrong here

    This option misattributes high-performance, mission-critical characteristics to the Basic tier, which is designed for low-cost, small-scale workloads. Basic provides only 5 DTUs and 2 GB storage, so it cannot deliver low latency or high throughput at production scale. Those capabilities are exclusive to the Premium tier, which offers SSD-based storage and far more compute and I/O capacity.

  • Standard: For extremely large databases and high scalability

    Why it's wrong here

    This option confuses Standard with Hyperscale: Standard is limited to a few hundred GB (up to 1 TB on higher S-levels) and scales vertically only by changing DTUs, not by unbounded storage or rapid horizontal scaling. Hyperscale is the tier that supports extremely large databases (up to 100 TB) and fast provisioning of compute replicas. Standard is best for predictable mid-size workloads, not massive scalability.

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 →

How Courseiva writes practice questions · Editorial policy

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.