Examkin

Question

Difficulty: MediumDesign Relational Database HA and DR

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?

  1. An Azure SQL Database failover group containing the primary database and a secondary database on a partner logical serverAnswer
  2. A read-write listener and a read-only listener configured on the failover group for application connectivityAnswer
  3. C
    Active geo-replication configured between the databases with routing managed by a custom Azure Traffic Manager profile
  4. D
    An Azure SQL Database elastic pool configured with geo-redundant backup storage (GRS) and automated runbooks for failover

Answer

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.

Step-by-Step Solution

1
Evaluate the RTO/RPO and automatic failover requirements.
Identify that automatic failover to a secondary region is required with a short RTO (< 1 hour) and RPO (< 10 seconds).
This rules out backup-based recovery and indicates a replicated HA/DR architecture is needed.
2
Determine the configuration that supports automatic failover and read-write/read-only endpoints.
Select Azure SQL Database failover groups rather than standalone active geo-replication.
Failover groups support automatic failover and provide unified listener endpoints that route traffic to primary (read-write) and secondary (read-only) databases automatically.
3
Configure the application connection strings.
Connect applications using the read-write listener for write operations and the read-only listener for read operations.
This ensures the application does not require configuration or connection string changes when a failover occurs.

Key Concept

Azure SQL Database Failover Groups for HA/DR and read-scale routing
Rate this question

Topics

Design Relational Database HA and DR

More questions from this topic