Study guide

8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO

Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Orientation

1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide

2 Chapter 2: Logging, Monitoring & Diagnostics Design

2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design

3 Chapter 3: Authentication & Authorization Design

3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design

4 Chapter 4: Governance, Compliance & Identity Governance Design

4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design

5 Chapter 5: Relational Data Storage Design

5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design

6 Chapter 6: Semi-Structured & Unstructured Data Storage Design

6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design

7 Chapter 7: Data Integration & Analytics Design

7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design

8 Chapter 8: Backup & Disaster Recovery Design

8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design

9 Chapter 9: High Availability Design

9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design

10 Chapter 10: Compute Solution Design

10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)

11 Chapter 11: Application Architecture Design

11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)

12 Chapter 12: Migration Design

12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)

13 Chapter 13: Network Solution Design

13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design

14 Chapter 14: Final Review, Exam Strategy & Career Path

14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path

8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO

Key Takeaways Explain This Topic AI

RTO is the maximum acceptable time to restore service; RPO is the maximum acceptable data loss measured in time -- both must be verified independently against a proposed architecture.

Geo-restore from geo-redundant backups has a documented RPO of up to one hour, which fails tight (sub-hour) RPO requirements even though it is the cheapest DR option.

Auto-failover groups and active geo-replication typically deliver seconds-level RPO with minutes-level failover, matching mission-critical and Tier 1 requirements.

Realistic RPO equals the backup or replication interval plus worst-case lag -- never assume a shorter loss window than the configured interval allows.

When a scenario says 'minimize cost,' choose the cheapest architecture that still clears the stated RTO/RPO bar rather than the most resilient option available.

Last updated: July 2026

Why This Topic Anchors the Entire Business Continuity Domain

Every other section in this chapter -- Azure Site Recovery, Azure Backup for compute, database backup/recovery, and unstructured data protection -- exists to satisfy a recovery objective . AZ-305's "Design business continuity solutions" domain (15-20% of the exam) is built around one official skill: "Recommend a recovery solution for Azure and hybrid workloads that meets recovery objectives." If you cannot translate a business requirement ("we can tolerate 15 minutes of data loss") into the right architecture, you will misread nearly every scenario question in this domain. Expect the exam to give you a paragraph of numbers and ask which service or configuration satisfies them -- and to include at least one distractor that meets one objective but silently violates the other.

Core Definitions

RTO (Recovery Time Objective) -- the maximum acceptable elapsed time between an outage and the application being fully usable again. RTO covers detection, decision-making, failover execution, DNS/traffic redirection, and application warm-up -- not just "how long the restore job takes."

RPO (Recovery Point Objective) -- the maximum acceptable amount of data loss , measured as a span of time (e.g., "RPO of 15 minutes" means you can lose at most the last 15 minutes of writes).

MTD (Maximum Tolerable Downtime) -- the outer boundary the business can survive before an outage becomes existential; RTO is always designed to be comfortably inside MTD.

SLA vs. RTO/RPO -- an SLA is a contractual uptime percentage (e.g., 99.99%); RTO/RPO are the engineering targets that make that SLA achievable during an actual disaster, not the same measurement.

A frequent exam trap: RPO is not simply "how often we take a backup." RPO is the worst-case data loss if disaster strikes at the least convenient moment -- immediately before the next scheduled backup or replication cycle completes. A database with hourly log backups has an RPO of up to one hour, not "the backups happen every hour so we're fine."

Mapping Objectives to Architecture Patterns

Tier Typical RTO Typical RPO Architecture pattern Representative Azure services

Mission-critical Seconds to a few minutes Near-zero (seconds) Active-active, multi-region Cosmos DB multi-region writes, Azure Front Door active-active, zone-redundant SQL Business Critical

Tier 1 (critical) Minutes, under 1 hour Under 15 minutes Active-passive, automated failover Azure SQL auto-failover groups, Availability Zones, Azure Site Recovery (Azure-to-Azure)

Tier 2 (important) 1-4 hours About 1 hour Warm standby, orchestrated failover Azure Site Recovery (hybrid), geo-redundant storage replication

Tier 3 (standard) Many hours to a day Up to 24 hours Backup and restore (cold) Azure Backup daily policy, geo-restore

Worked Example: Reading the Numbers Correctly

A retailer's order-processing database must meet RTO 1 hour, RPO 15 minutes . Two options are on the table:

Geo-restore from geo-redundant automated backups. Microsoft's documented RPO for geo-restore is up to one hour because backup replication to the paired region can lag. This fails the 15-minute RPO requirement even though it's inexpensive and simple.

Auto-failover groups with active geo-replication. Typical replication lag is seconds, and failover (manual or automatic) typically completes within minutes. This meets both the RTO and RPO targets.

The exam rewards candidates who check both numbers independently -- a solution that nails RTO but blows the RPO budget (or vice versa) is still wrong.

Another worked calculation: a VM workload backs up every 4 hours with Azure Backup's enhanced policy. If disruption occurs 3 hours 59 minutes into the backup interval, the realistic RPO is just under 4 hours , not "4 backups a day so RPO is 6 hours" or any other guess disconnected from the interval length. Always set RPO targets equal to or tighter than the chosen backup/replication interval, never looser.

Common Decision Traps

Treating RTO as only the technical restore time and ignoring detection/decision/DNS propagation time, which can dominate the real-world number.

Assuming any "geo-redundant" label automatically satisfies a strict RPO -- geo-redundant storage replication (used by geo-restore) has a much looser RPO than geo-redundant replication features like auto-failover groups or Cosmos DB multi-region writes.

Forgetting that tighter RTO/RPO always costs more (multi-region compute, synchronous-like replication, higher-tier SKUs) -- a scenario that emphasizes "minimize cost" is a signal to pick the loosest architecture that still meets the stated numbers, not the fanciest one.

Confusing "backup frequency" with "RPO" -- frequency is an input to RPO, not the RPO itself; you must add worst-case lag.

Quick Reference Table for Exam Recall

If the scenario says... Read it as...

"No more than 5 minutes of data can be lost" RPO ≤ 5 minutes -- rules out anything with hourly-or-looser replication

"The application must be back within 30 minutes" RTO ≤ 30 minutes -- rules out manual, multi-step DR runbooks

"Minimize cost while meeting a 4-hour RTO" Choose the cheapest pattern that clears the bar, e.g., ASR over active-active

"Zero data loss is required" Only synchronous replication within a region (e.g., zone-redundant storage/SQL) can promise this; cross-region always has some lag