An organization deploys a critical application that uses an Azure SQL Database. You need to design a high availability and disaster recovery (HA/DR) solution for the database to meet the following requirements:
- The database must support automatic failover to a partner region.
- The recovery time objective (RTO) must be less than 1 hour.
- The recovery point objective (RPO) must be less than 10 seconds.
- The application must connect to the database using unified endpoints that automatically route read-write and read-only traffic to the correct replicas without requiring connection string updates after a failover.
Which two configurations should you include in the design?
- An Azure SQL Database failover group containing the primary database and a secondary database on a partner logical serverCevap
- A read-write listener and a read-only listener configured on the failover group for application connectivityCevap
- CActive geo-replication configured between the databases with routing managed by a custom Azure Traffic Manager profile
- DAn Azure SQL Database elastic pool configured with geo-redundant backup storage (GRS) and automated runbooks for failover
Cevap
Configure an Azure SQL Database failover group and use the read-write and read-only listener endpoints for application connection strings.
The correct architecture uses an Azure SQL Database failover group and configurations for read-write and read-only listener endpoints. A failover group provides automatic failover capabilities across regions and exposes unique listener endpoints. These endpoints automatically route read-write traffic to the primary database and read-only traffic to the secondary partner database, ensuring that connection strings do not need to be updated after a failover.
Adım Adım Çözüm
Anahtar Kavram
Azure SQL Database Failover Groups for HA/DR and read-scale routing