Quick Answer
The answer is active geo-replication. This feature is correct because it provides continuous, asynchronous replication of transactions to a readable secondary replica in a paired Azure region, achieving an RPO of 5 seconds and an RTO of 30 seconds when the secondary is used for failover. On the AZ-305 exam, this scenario tests your ability to distinguish between Azure SQL Database disaster recovery options—active geo-replication versus failover groups—where the key differentiator is the granular RPO/RTO requirement versus automated orchestration. A common trap is choosing failover groups, which offer a higher RPO (typically 5–10 minutes) and are better suited for managing multiple databases, not sub-minute recovery. Remember the memory tip: “5 and 30, replicate actively” to link the 5-second RPO and 30-second RTO directly to active geo-replication, not its group-based counterpart.
This AZ-305 practice question tests your understanding of design data storage solutions. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company uses Azure SQL Database for a line-of-business application. They need to implement a disaster recovery solution across Azure regions with RPO of 5 seconds and RTO of 30 seconds. Which feature should they use?
Active geo-replication
Active geo-replication offers fast replication with RPO < 5 seconds and RTO < 30 seconds.
Geo-restore
Why wrong: Geo-restore has RPO of hours, not seconds.
Azure SQL Database zone-redundant configuration
Why wrong: Zone-redundancy protects within a region, not cross-region DR.
Auto-failover groups
Why wrong: Auto-failover groups have RTO of about 1 hour due to DNS changes, not 30 seconds.
Answer choices
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 for Azure SQL Database provides a continuous replication mechanism with an RPO of 5 seconds and an RTO of 30 seconds when using a readable secondary replica in a paired region. It replicates transactions asynchronously but with very low latency, meeting the strict RPO/RTO requirements for cross-region disaster recovery.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
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 offers fast replication with RPO < 5 seconds and RTO < 30 seconds.
Related concept
Read the scenario before looking for a memorised answer.
Geo-restore
Why it's wrong here
Geo-restore has RPO of hours, not seconds.
Azure SQL Database zone-redundant configuration
Why it's wrong here
Zone-redundancy protects within a region, not cross-region DR.
Auto-failover groups
Why it's wrong here
Auto-failover groups have RTO of about 1 hour due to DNS changes, not 30 seconds.
Common exam traps
The trap here is that candidates often confuse auto-failover groups with active geo-replication, assuming the managed failover group provides faster RTO, but in reality, auto-failover groups have a longer RTO (typically 1 hour) due to DNS propagation and health probe intervals, while active geo-replication allows manual failover with sub-minute RTO.
Detailed technical explanation
Active geo-replication uses asynchronous replication at the transaction log level, committing transactions on the primary and then sending log records to the secondary every few seconds, achieving an RPO of 5 seconds. The RTO of 30 seconds is achieved by manually initiating a forced failover to the readable secondary, which promotes it to primary without data loss within that window. In contrast, auto-failover groups add a listener endpoint and health probes, which can delay failover detection and increase RTO beyond 30 seconds.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Design data storage solutions — study guide chapter
Learn the concepts, then practise the questions
Design data storage solutions practice questions
Targeted practice on this topic area only
All AZ-305 questions
999 questions across all exam domains
Microsoft Azure Solutions Architect Expert AZ-305 study guide
Full concept coverage aligned to exam objectives
AZ-305 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise AZ-305 questions linked to Design identity, governance, and monitoring solutions.
Practise AZ-305 questions linked to Design data storage solutions.
Practise AZ-305 questions linked to Design business continuity solutions.
Practise AZ-305 questions linked to Design infrastructure solutions.
Practise AZ-305 questions linked to SAA-C03 VPC.
Practise AZ-305 questions linked to SAA-C03 S3 lifecycle policy questions.
Practise AZ-305 questions linked to SAA-C03 RDS Multi-AZ questions.
Practise AZ-305 questions linked to SAA-C03 IAM policy.
Practise AZ-305 questions linked to SAA-C03 Route 53 failover questions.
Practise AZ-305 questions linked to SAA-C03 CloudFront.
Practise AZ-305 questions linked to SAA-C03 NAT gateway questions.
Practise AZ-305 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Design data storage solutions — This question tests Design data storage solutions — Read the scenario before looking for a memorised answer..
The correct answer is: Active geo-replication — Active geo-replication for Azure SQL Database provides a continuous replication mechanism with an RPO of 5 seconds and an RTO of 30 seconds when using a readable secondary replica in a paired region. It replicates transactions asynchronously but with very low latency, meeting the strict RPO/RTO requirements for cross-region disaster recovery.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
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 →
Last reviewed: Jun 24, 2026
This AZ-305 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 AZ-305 exam.
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.
Sign in to join the discussion.