Courseiva

Active Geo-Replication in Azure SQL Database

A global e-commerce company uses Azure SQL Database for its order management system. They need to ensure high availability with the ability to fail over to an Azure region in a different continent in case of a regional outage. They also want to use the secondary database for read-intensive reporting without affecting the primary's performance. Which Azure SQL Database feature should they enable?

Quick Answer

Active geo-replication is the correct choice because it provides high availability for Azure SQL Database by creating readable secondary replicas in a different Azure region, even on another continent, and supports manual failover during a regional outage while allowing the secondary to handle read-intensive reporting without impacting the primary’s performance. This feature directly addresses the need for cross-continent disaster recovery and read-scale workloads, as the secondary database is continuously updated asynchronously and can be used for read-only queries. On the DP-900 exam, this scenario tests your understanding of the difference between active geo-replication and failover groups—a common trap is confusing the two, but remember that active geo-replication gives you readable secondaries and manual failover, whereas failover groups add automatic failover and a listener endpoint. For a memory tip, think “active geo-replication = read + manual failover across continents,” and picture a globe with a primary database on one side and a readable copy on the other, ready for reporting without slowing down the main system.

⚠ Common exam trap

Test-takers frequently confuse 'geo-replication' with 'failover groups' or assume that any backup feature (like long-term retention) can serve as a high-availability solution, but only active geo-replication provides a readable secondary in a different continent for both failover and read-scale.

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

✓

Active geo-replication

Active geo-replication is the correct choice because it creates readable secondary replicas of an Azure SQL Database in a different Azure region (including a different continent). It supports manual failover to the secondary region during an outage, and the secondary can be used for read-only query workloads like reporting without impacting the primary database's performance.

Answer analysis

Option-by-option breakdown

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

  • ✓

    Active geo-replication

    Why this is correct

    Active geo-replication creates up to four readable secondaries in any Azure region, satisfying both the cross-continent failover requirement and the reporting-offload requirement. Unlike auto-failover groups, it supports manually initiated failover to any replica and permits read workloads on secondaries, so reporting queries never touch the primary.

  • ✗

    Long-term backup retention

    Why it's wrong here

    Long-term backup retention stores copies for compliance-driven restore windows of up to ten years; it provides no cross-continent failover and no readable secondary replica. It is the right choice when regulation demands point-in-time backups beyond the standard retention period, not for regional disaster recovery or offloading reporting.

  • ✗

    Automatic tuning

    Why it's wrong here

    Automatic tuning applies index and plan corrections to improve query performance on the primary; it creates no secondary replica in another continent and no failover capability. It is the right choice when you want continuous performance regression detection and automatic index creation, not geo-redundant availability or read offload.

  • ✗

    Connection pooling

    Why it's wrong here

    Connection pooling reuses open database connections to reduce handshake overhead; it offers no geo-replication, failover or readable secondary. It is correct when many short-lived client connections exhaust server resources, improving throughput and latency, but it cannot satisfy cross-continent availability or reporting offload requirements.

About these practice questions

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

Same concept, more angles

3 more ways this is tested on DP-900

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 runs a global e-commerce platform on Azure SQL Database. The platform experiences heavy read traffic on product catalog and inventory tables. You need to reduce read latency for users in different geographic regions while keeping write latency low. The solution must be cost-effective and require minimal application changes. Current architecture: a single Azure SQL Database in West US. You have budget for additional Azure resources. What should you implement?

hard
  • ✓ A.Configure Active Geo-Replication to create readable secondaries in regions where users are located.
  • B.Migrate the database to Azure Cosmos DB with multi-region writes.
  • C.Use Azure Traffic Manager to route read requests to the primary database in West US.
  • D.Enable Read Scale-Out on the existing database and configure application to use the read-only endpoint.

Why A: Active Geo-Replication (option A) is correct because it creates readable secondary databases in multiple Azure regions, allowing read queries to be served locally in each user's region while writes continue to the primary, reducing read latency without changing the application's write path. It is cost-effective relative to a full re-platforming and requires minimal application changes—just directing read-only connections to the regional secondary endpoints. Option B does not fit because migrating to Azure Cosmos DB with multi-region writes is a major architectural change and typically more expensive, and it changes the data model and consistency semantics. Option C is wrong because Azure Traffic Manager only routes traffic to endpoints and cannot make a single West US database serve reads faster for users in other regions. Option D is incorrect because Read Scale-Out uses a read-only replica in the same region as the primary, so it does not reduce cross-region read latency for geographically distributed users.

Variation 2. A multinational e-commerce company uses Azure SQL Database for its order processing system. They need to ensure that if an entire Azure region becomes unavailable, the database remains available with minimal data loss and automatic failover. Which feature should they implement?

medium
  • ✓ A.Active geo-replication
  • B.Automatic tuning
  • C.Elastic pools
  • D.Serverless compute

Why A: Active geo-replication (Option A) is correct because it creates readable secondary replicas of an Azure SQL Database in a paired Azure region, enabling automatic failover during a regional outage. This feature provides a recovery point objective (RPO) of as low as 5 seconds and a recovery time objective (RTO) of under 1 hour, ensuring minimal data loss and high availability.

Variation 3. A company uses Azure SQL Database for a customer relationship management (CRM) system. The database is deployed in the East US region. The company has customers worldwide who access the CRM via a web application. Currently, all read and write traffic goes to the primary database in East US, causing high latency for users in Europe and Asia. The company needs to improve read performance for global users while maintaining strong consistency for writes. They also want to minimize cost. Which solution should you recommend?

medium
  • A.Implement Azure Redis Cache to cache frequently accessed data
  • ✓ B.Configure active geo-replication with readable secondary replicas in West Europe and Southeast Asia
  • C.Use Azure SQL Database with geo-redundant storage and enable read-scale
  • D.Create read replicas in the same region and use Azure Traffic Manager to route read traffic

Why B: Option B is correct because active geo-replication lets you create readable secondary replicas in West Europe and Southeast Asia, so global users can read locally while all writes still go to the single primary in East US, preserving strong consistency for writes. This directly reduces read latency for European and Asian users and is a lower-cost fit than a full auto-failover group or premium read-scale configuration. Option A does not address database read latency for globally distributed users and adds cache-invalidation complexity. Option C is incorrect because geo-redundant storage is for backup/DR, not for serving readable replicas, and read-scale requires the Business Critical tier, which increases cost. Option D is wrong because read replicas in the same East US region would not reduce latency for users in Europe and Asia.

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.