Plan and configure a high availability and disaster recovery environment →hardMultiple ChoiceObjective-mapped
DP-300 Practice Question: Plan and configure a high availability and disaster recovery environment
A manufacturing company uses Azure SQL Database Hyperscale tier for its IoT telemetry data. The database is in West Europe and must be readable in East US for reporting with a maximum lag of 10 seconds. You configure a failover group with East US as the secondary region. After setup, reporting queries in East US show data that is 5 minutes old. What is the most likely cause?
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
✓
The secondary database is configured with 'Geo' secondary type; you need to set it to 'Readable' to minimize lag
The most likely cause is that the secondary database is configured with the default 'Geo' secondary type, which is not readable and uses asynchronous replication with potentially high lag. To minimize lag and make the secondary readable for reporting, you must set the secondary type to 'Readable' (also called 'Named' secondary in some contexts). This ensures the secondary is kept in near-synchronous sync, though still asynchronous. Option A is incorrect because the failover policy does not affect replication lag. Option B is incorrect because the secondary can be made readable by changing the secondary type. Option D is incorrect because Hyperscale does not support synchronous replication, and changing to sync would not address the lag issue.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The failover group has 'Read/Write failover policy' set to 'Automatic' causing the lag
Why it's wrong here
Automatic failover policy does not affect replication lag.
- ✗
The secondary database is not readable; it is only for failover
Why it's wrong here
In a failover group, the secondary is readable by default, though lag may still occur.
- ✓
The secondary database is configured with 'Geo' secondary type; you need to set it to 'Readable' to minimize lag
Why this is correct
Setting the secondary type to 'Readable' ensures the secondary is maintained with lower replication lag.
- ✗
The replication mode is set to 'Async' and should be changed to 'Sync'
Why it's wrong here
SQL Database does not support synchronous replication across regions for Hyperscale.
Go deeper
Related to this question
Learn chapter
Overview of Azure Data Platform Options
Key term
Azure SQL Performance Tuning
Azure SQL Performance Tuning is the process of optimizing the speed and efficiency of queries and database operations in Microsoft Azure SQL Database or SQL Managed Instance to reduce latency and improve throughput.
About these practice questions
One of 906 original DP-300 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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.