You are sizing Azure SQL Database HADR for a workload tracked under the WAF Reliability pillar that requires zero data loss in-region, less-than-one-minute RTO across regions, and a low-cost option for non-critical databases that tolerates minutes-to-hours RTO. Which three options match the documented HADR table? (Select 3 answers)
- AZone redundancy provides RTO typically less than 30 seconds and RPO 0 for in-region high availability. Correct
- BFailover groups with customer-managed policy provide RTO typically less than 60 seconds, RPO at or above 0. Correct
- CGeo-restore provides RTO typically minutes or hours and RPO typically minutes or hours dependent on backup size. Correct
- DActive geo-replication provides an RTO of 24 hours and an RPO of 24 hours across every Azure SQL Database tier.
- ESingle-database PITR provides an RTO of less than 5 seconds and an RPO of 0 across any regional outage.
Why A is correct: Correct. Zone redundancy provides RTO typically less than 30 seconds and RPO 0 for in-region high availability is one of the keyed answers. The Azure SQL HADR comparison table lists three tiers: zone redundancy at typically <30s RTO and RPO 0; failover groups (or active geo-replication) at typically <60s RTO and RPO 0+; geo-restore at typically minutes-to-hours for both RTO and RPO.
Why B is correct: Correct. Failover groups with customer-managed policy provide RTO typically less than 60 seconds, RPO at or above 0 is one of the keyed answers. The Azure SQL HADR comparison table lists three tiers: zone redundancy at typically <30s RTO and RPO 0; failover groups (or active geo-replication) at typically <60s RTO and RPO 0+; geo-restore at typically minutes-to-hours for both RTO and RPO.
Why C is correct: Correct. Geo-restore provides RTO typically minutes or hours and RPO typically minutes or hours dependent on backup size is one of the keyed answers. The Azure SQL HADR comparison table lists three tiers: zone redundancy at typically <30s RTO and RPO 0; failover groups (or active geo-replication) at typically <60s RTO and RPO 0+; geo-restore at typically minutes-to-hours for both RTO and RPO.
Why D is wrong: Active geo-replication is a continuous-replication option with sub-60-second RTO targets, not a 24/24 design point.
Why E is wrong: Point-in-time restore is for accidental-deletion recovery, not a region-outage RTO/RPO option in the HADR table.