Courseiva

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

An e-commerce application uses Azure SQL Database. During flash sales, the database experiences high CPU usage and query timeouts. The team needs a solution that can handle sudden increases in demand without downtime. Which scaling option should they choose?

⚠ Common exam trap

Candidates often confuse 'scaling for demand spikes' with 'scaling for read-heavy workloads' or 'managing multiple databases,' leading candidates to incorrectly choose Read scale-out or Elastic Pool instead of the compute-scalable Hyperscale tier.

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

Hyperscale service tier

The Hyperscale service tier is designed for high-performance, rapidly growing workloads that require instant scalability. It separates compute from storage, allowing compute nodes to be added or scaled up in seconds without downtime, making it ideal for handling sudden spikes in demand like flash sales.

Answer analysis

Option-by-option breakdown

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

  • Read scale-out

    Why it's wrong here

    Read scale-out is specifically designed to offload read-only workloads by routing reporting or analytical queries to a read-only replica via ApplicationIntent=ReadOnly. In a write-heavy e-commerce transaction surge, those replicas do not process INSERT, UPDATE, or DELETE statements and cannot increase the primary replica's compute capacity or transaction throughput, so it would not address the demand spike.

  • Hyperscale service tier

    Why this is correct

    The Hyperscale service tier is built on a distributed architecture with separate compute nodes and page servers, allowing compute to be scaled up to 100 vCores in seconds with no downtime. Because e-commerce demand spikes are often sudden and unpredictable, Hyperscale lets you add compute power—and optionally additional read replicas—dynamically without re-provisioning storage, making it the only listed option that directly and rapidly increases write-transaction capacity.

  • Elastic Pool

    Why it's wrong here

    Elastic Pools are a cost-management and resource-sharing feature for multiple Azure SQL databases that share a fixed set of eDTUs or vCores. A single database in a pool is limited by both its per-database max and the pool's aggregate size, so it cannot elastically burst beyond those boundaries to absorb a sudden workload spike; the pool is for consolidating stable workloads, not for scaling one database quickly.

  • Geo-replication

    Why it's wrong here

    Geo-replication maintains asynchronous readable secondary replicas in a different Azure region primarily for disaster recovery and business continuity. A secondary replica is read-only and does not share the primary replica's transaction log or compute resources, so enabling geo-replication adds no scale-out or scale-up capacity for the primary's write transactions; it only mitigates regional outage risk.

About these practice questions

This DP-900 question is part of Courseiva's 820-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 →

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.