A logistics company is designing a disaster recovery solution for an application database. The database is currently hosted on Azure SQL Managed Instance. The solution must meet the following requirements:
- Support automatic failover to a secondary region.
- Provide a single connection endpoint for read-write traffic and a separate endpoint that automatically routes read-only reporting queries to the secondary region.
- Keep the Recovery Point Objective (RPO) under 5 seconds.
- Ensure all replication traffic between the primary and secondary instances remains within a private network boundary.
Which solution should you recommend?
- An Azure SQL Managed Instance Failover Group deployed across peered virtual networks, utilizing the read-only listener endpoint for reporting.Answer
- BActive geo-replication configured for the Azure SQL Managed Instance, utilizing the secondary replica's direct endpoint with public IP routing for reporting.
- CAn Azure SQL Database Elastic Pool with active geo-replication, using public service endpoints to route read-only queries to the secondary region.
- DSQL Server Always On Availability Groups deployed on Azure Virtual Machines using Standard HDD drives for transaction logs, with read-only routing configured.
Answer
An Azure SQL Managed Instance Failover Group deployed across peered virtual networks, utilizing the read-only listener endpoint for reporting.
The correct solution uses an Azure SQL Managed Instance Failover Group configured across peered virtual networks. Failover Groups support automatic failover, meet the low RPO, and provide two distinct listener endpoints (read-write and read-only). The read-only endpoint automatically routes reporting traffic to the secondary instance, while virtual network peering ensures that all replication traffic remains secure and private.
Step-by-Step Solution
Key Concept
Azure SQL Managed Instance Failover Groups