Hyperscale Named Replica for DR

Exhibit

{
  "properties": {
    "databases": [
      {
        "name": "SalesDB",
        "readScale": "Enabled",
        "readReplicaCount": 2
      }
    ]
  }
}

Refer to the exhibit. You are reviewing the configuration of an Azure SQL Database hyperscale service tier. The database 'SalesDB' has read scale enabled with 2 read replicas. You need to ensure that if the primary region fails, the database can be failed over to a secondary region with minimal data loss and that the read replicas in the secondary region are also available. What should you configure?

Quick Answer

The correct configuration is to create a named replica in a secondary region and configure it as a geo-secondary. Named replicas in Azure SQL Database Hyperscale serve dual roles: they provide read scale-out and can be promoted to primary during a regional outage, enabling disaster recovery with minimal data loss. This works because Hyperscale’s architecture distributes log and page servers across regions, allowing the named replica to maintain near-synchronous replication. On the DP-300 exam, this tests your understanding of how Hyperscale differs from standard tiers—active geo-replication and failover groups are not supported, making named replicas the only built-in cross-region DR mechanism. A common trap is selecting zone redundancy (in-region HA only) or misapplying geo-replication from non-Hyperscale scenarios. Memory tip: Think “Named Replica = Geo + Scale” — it’s both a read replica and your failover target for Hyperscale disaster recovery.

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

✓

Create a named replica in a secondary region and configure it as a geo-secondary.

For Azure SQL Database Hyperscale, named replicas can be created in a secondary region. These replicas provide both read scale-out and can be promoted to primary during a regional failover, ensuring minimal data loss. Option A is incorrect because zone redundancy provides high availability within a single region, not disaster recovery across regions. Option C is incorrect because active geo-replication is not supported for Hyperscale; named replicas serve the geo-replication purpose. Option D is incorrect because failover groups are not supported for Hyperscale; named replicas are the mechanism for cross-region failover and read scaling.

Answer analysis

Option-by-option breakdown

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

✗
Configure zone redundancy on the Hyperscale database.
Why it's wrong here
Zone redundancy protects against zonal failures, not regional.
✓
Create a named replica in a secondary region and configure it as a geo-secondary.
Why this is correct
Named replicas can be created in a secondary region and promoted during failover, providing DR and read scalability.
✗
Enable active geo-replication to a secondary server in a different region.
Why it's wrong here
Active geo-replication is not supported for Hyperscale; named replicas are the equivalent.
✗
Create a failover group with a secondary Hyperscale database in another region.
Why it's wrong here
Failover groups for Hyperscale use named replicas; traditional failover groups are not supported.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on DP-300

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. Your company uses Azure SQL Database Hyperscale tier for a large OLTP workload. You need to implement a disaster recovery solution that provides a readable secondary in a different Azure region with an RPO of less than 5 seconds and automatic failover. What should you configure?

medium

A.Create an auto-failover group with a secondary in the paired region.
B.Enable geo-redundant backup storage and use geo-restore.
C.Configure active geo-replication to a secondary server in another region.
✓ D.Create a named replica in the target region and configure application failover logic.

Why D: Hyperscale supports named replicas that can be created in a different region and can be used for failover. Option A is wrong because Hyperscale does not support auto-failover groups. Option B is wrong because Hyperscale does not support active geo-replication. Option C is wrong because geo-restore does not provide a readable secondary.

Last reviewed: Jun 21, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

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.