Rpo Rto Confusion — Azure Solutions Architect (AZ-305)
You confused recovery point objective (data loss tolerance) with recovery time objective (downtime tolerance). Different requirements, different architectures.
Recovery Time and Recovery Point Are Not Interchangeable
RTO and RPO appear in the same DR scenario and are not interchangeable. RTO is elapsed time from failure to restored service. RPO is the age of the most recent recoverable data point. A scenario specifying RPO = 0 eliminates every asynchronous replication path: RA-GRS carries replication lag and cannot guarantee zero data loss. Active geo-replication with synchronous commit satisfies RPO = 0 for database workloads. Geo-redundant Blob Storage satisfies durability requirements but not a zero-loss RPO. Translate each term before evaluating topology, not after comparing services. The scenario names both terms when both matter.
The Scenario
A healthcare application needs RTO of 4 hours and RPO of 0 (zero data loss). You recommend Azure Site Recovery (ASR) for VM replication with automatic failover. ASR replicates VMs asynchronously with RPO as low as 30 seconds for Azure-to-Azure — but "as low as 30 seconds" is not zero. Zero RPO requires synchronous replication. For Azure SQL, that means Always On Availability Groups with synchronous commit mode to a secondary replica. For VMs, zero RPO is architecturally impossible with ASR — you need application-level synchronous replication (database sync commit, storage-level sync). The exam tests whether you know the difference between "very low RPO" and "zero RPO."
How to Spot It
- •RPO of 0 is a hard constraint that eliminates all asynchronous replication. Azure Site Recovery, geo-redundant storage (GRS), and Azure SQL geo-replication all use asynchronous replication. Only synchronous replication (Azure SQL Always On with synchronous commit, Availability Zones for storage) achieves RPO of 0.
- •Azure paired regions replicate storage asynchronously with GRS (RPO ~15 minutes). Zone-redundant storage (ZRS) replicates synchronously within a region. The exam tests whether you know GRS cannot achieve zero RPO while ZRS can for intra-region scenarios.
- •RTO and RPO are independent axes. Azure Site Recovery gives RTO of minutes but RPO > 0. Azure SQL synchronous replicas give RPO of 0 but require Always On configuration. Design for each constraint separately.
Decision Rules
Which Azure SQL Database tier and zone-redundancy combination satisfies RPO less than 10 minutes and RTO less than 30 minutes at minimum monthly cost, without upgrading to a higher-priced tier whose additional HA properties are unnecessary given the stated numeric targets?
Whether the cross-region RPO ≤ 5 min target is satisfied by a tier upgrade to Business Critical with zone redundancy (intra-region HA only) or by Active Geo-Replication on a General Purpose tier (cross-region near-zero RPO at lower compute cost).
Does an RPO ≤ 5 minutes for a data integration pipeline mandate a continuous streaming architecture, or can a managed incremental CDC pipeline running on sub-5-minute tumbling windows satisfy the constraint within the team's operational capability?
Whether Azure SQL Database General Purpose with zone-redundant deployment satisfies the stated 99.99% availability SLA and RPO ≤ 15 minutes for zone failures—anchored on the fact that GP zone-redundant already achieves the 99.99% SLA and that automated differential backups running every 5–12 minutes satisfy RPO ≤ 15 min, making Business Critical an unjustified cost premium that violates the cost-minimization directive.
Whether pipeline run frequency alone satisfies the stated cross-region RPO, or whether ADLS geo-redundant replication tier plus a secondary-region ADF pipeline recovery configuration must be explicitly provisioned to guarantee data currency and pipeline resumption after a regional outage.
Whether to deploy Azure SQL Database on the Business Critical tier (synchronous zone-redundant local SSD replicas, RPO=0) or the General Purpose tier (remote asynchronous storage replication, RPO>0) paired with Zone-Redundant Blob Storage, given an explicit RPO=0 constraint on the relational tier.
Whether to use synchronous zone-redundant replication at both the relational tier (Business Critical + zone-redundant config) and the blob tier (ZRS), versus selecting near-right options that satisfy availability SLA on paper but use asynchronous replication and therefore cannot guarantee RPO=0.
Whether to deploy Azure SQL Database at the Business Critical tier with zone redundancy enabled (synchronous Always On AG replication across zones, RPO=0) versus General Purpose tier with auto-failover groups (async geo-replication, RPO measured in minutes), combined with whether to use Azure Blob Storage ZRS (synchronous zone replication, RPO=0) versus LRS or GRS (async or single-datacenter, RPO > 0).
Whether the chosen compute tier and redundancy model satisfies the explicit cross-region RPO and RTO targets rather than the within-region zone-level HA guarantee that a zone-redundant App Service plan provides.
When RTO ≤ 15 minutes is stated for IaaS workloads, backup-restore is disqualified regardless of whether backup frequency can satisfy the RPO; continuous replication with orchestrated failover via Azure Site Recovery is the minimum viable tier.
Domain Coverage
Difficulty Breakdown
Related Patterns