DP-900 Practice Question: Identify considerations for relational data on Azure
A company uses Azure SQL Database for a sales application. They need to replicate the database to a secondary region for disaster recovery. The secondary should be readable for reporting purposes and data should be synchronized within seconds. Which feature should they use?
⚠ Common exam trap
Many candidates confuse Auto-failover groups with Active Geo-Replication, assuming the group feature provides faster synchronization, when in fact both use the same asynchronous replication and the key difference is that Auto-failover groups add automatic failover and endpoint management, not lower latency.
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 a readable secondary replica in a different Azure region, with data synchronized within seconds via asynchronous replication. This meets the requirement for both disaster recovery and read-only reporting access, as the secondary can be queried directly without impacting the primary database.
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 asynchronously replicates committed transactions from the primary Azure SQL database to a readable secondary in a different region, keeping the copy continuously synchronized with a lag usually measured in seconds. This provides a warm, readable target that can serve reporting workloads without impacting the primary, and because Azure manages the replication process, administrative overhead remains minimal. It also supports manual failover for disaster recovery, but for a persistent reporting secondary it is the simplest and most direct fit.
- ✗
Auto-failover groups
Why it's wrong here
Auto-failover groups layer automatic failover and a listener endpoint on top of geo-replication, enabling an application to switch to a secondary with a single connection string when a regional outage occurs. While the secondary in a failover group is readable and could technically serve reporting, the primary value of this feature is policy-driven, automatic failover—not read-scale out. For a requirement that only asks for a continuous readable copy for reporting, Active Geo-Replication already delivers that capability, so adding a failover group introduces unnecessary configuration and failover-policy management without solving any new problem.
- ✗
Point-in-time restore
Why it's wrong here
Point-in-time restore is a backup and recovery capability that reconstructs a database from automated backups to any moment within the configured retention period, but it is not a continuous replication mechanism. To use it for reporting you would have to schedule recurring restores, each creating a separate snapshot database that is not kept in sync with the live production database. Therefore it can never serve as the always-updated, readable secondary the scenario requires—it is meant for recovering from corruption, user error, or accidental data loss, not for workload isolation.
- ✗
Long-term retention
Why it's wrong here
Long-term retention stores full and differential backups plus transaction log backups for years in Azure storage for compliance, archival, or regulatory purposes, and those backups are not directly accessible as live, readable database copies. To make an LTR backup useful you would need to perform an explicit restore operation, and even then the restored database is a point-in-time snapshot, not a continuously updated replica. The feature is fundamentally about durability of backup history, not real-time secondary access, so it cannot satisfy a reporting workload that needs current data.
Go deeper
Related to this question
Learn chapter
Data Roles and Core Concepts
Key term
Data
Data is raw, unprocessed information, like numbers, words, or measurements, that can be stored, processed, and analyzed by computers.
Key term
Azure SQL Database
Azure SQL Database is a fully managed relational database-as-a-service (DBaaS) in Microsoft Azure, based on the SQL Server engine, that handles scaling, backups, patching, and high availability automatically.
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 →
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.