Question

Difficulty: MediumDesign Relational Database HA and DR

An insurance firm is designing the disaster recovery architecture for its policy management application. The application uses an Azure SQL Database as its data tier. The disaster recovery solution must meet the following requirements:

* If a regional outage occurs, the database must fail over automatically to a secondary Azure region.
* The application connection strings must remain unchanged after a failover.
* The secondary replica must be used to run read-only reporting workloads, and reporting clients must automatically route to the active secondary database.

Which Azure SQL Database feature should you recommend to meet these requirements?

  1. A
    Active geo-replication
  2. B
    Read-Access Geo-Redundant Storage (RA-GRS)
  3. Failover groupsAnswer
  4. D
    SQL Server Always On availability groups on Azure Virtual Machines

Answer

Failover groups
Failover groups allow you to manage replication, connectivity, and failover of databases to another Azure region. It provides read-write and read-only listener endpoints that point to the primary and secondary databases. If a failover occurs, the endpoints automatically update to point to the new roles, keeping connection strings unchanged. It also supports automatic failover policies.

Step-by-Step Solution

1
Analyze the automatic regional failover and endpoint requirements.
Determined that the solution must support automatic failover and stable, unchanged connection strings for both read-write and read-only traffic across regions.
This rules out basic active geo-replication, which requires manual failover and does not provide unified connection listeners.
2
Compare managed PaaS options against IaaS options to minimize operational overhead.
Ruled out migrating to SQL Server Always On availability groups on Azure VMs, as the application is already on Azure SQL Database and PaaS-native solutions are preferred to minimize administrative effort.
Azure SQL Database has built-in high availability and disaster recovery mechanisms.
3
Select the feature that natively provides automated failover and dual listener endpoints.
Selected Failover groups, which natively offer read-write and read-only listener endpoints to route traffic dynamically to the active primary and secondary databases.
Failover groups meet all requirements for automated failover, stable endpoints, and read-scale routing for Azure SQL Database.

Key Concept

Azure SQL Database Failover groups provide automatic failover and stable read-write/read-only listener endpoints across regions.
Rate this question