Examkin

Question

Difficulty: HardDesign Relational Database HA and DR

A multinational financial services organization is designing a disaster recovery and high availability solution for its core ledger application. The application will be deployed across two Azure regions: East US (primary) and West US (secondary).

The database layer consists of an Azure SQL Managed Instance deployment in each region. The design must meet the following requirements:
- Support automatic failover to the secondary region if the primary region experiences an outage.
- Provide a connection configuration that automatically routes read-write operations to the active primary instance and read-only reporting queries to the secondary instance.
- Ensure that replication and database traffic between the primary and secondary instances does not traverse the public internet and uses private IP addresses.

Which two actions should you include in the design to meet these requirements?

  1. Create a failover group between the primary and secondary SQL Managed Instances, and configure the application connection strings to use the failover group's read-write and read-only listener endpoints.Answer
  2. Configure global virtual network peering between the virtual networks hosting the primary and secondary SQL Managed Instances to facilitate private database replication.Answer
  3. C
    Configure active geo-replication for each user database on the primary SQL Managed Instance, and configure the application connection strings to use the failover partner attribute.
  4. D
    Deploy an Azure Traffic Manager profile using priority routing to direct database connection requests to the public endpoints of the primary and secondary SQL Managed Instances.

Answer

Create a failover group between the SQL Managed Instances to handle automatic failover and listener routing, and configure global virtual network peering between their virtual networks to allow private database replication traffic.
To design a disaster recovery and high availability solution for Azure SQL Managed Instance that supports automatic failover and read-scale routing, you must use a failover group. The failover group provides two distinct listener endpoints (one for read-write and one for read-only traffic) that automatically adjust during failover. Furthermore, SQL Managed Instance replication requires direct network routing between instances over a private connection, which is achieved by setting up global virtual network peering between the primary and secondary virtual networks.

Step-by-Step Solution

1
Analyze database type and cross-region requirements.
The workload uses Azure SQL Managed Instance. Cross-region disaster recovery for SQL Managed Instance requires failover groups; active geo-replication is not supported on SQL Managed Instance.
Choosing the correct Azure-native replication technology ensures compatibility with the chosen database offering.
2
Address private routing requirements.
Global virtual network peering is designed between the virtual networks containing the SQL Managed Instances in East US and West US.
Failover groups for SQL Managed Instance require private network connectivity (IP routing) between the instances, which global virtual network peering provides securely over the Microsoft backbone.
3
Address routing of read-write and read-only traffic.
Configure connection strings using the failover group's read-write and read-only listener endpoints.
This provides distinct connection endpoints for each workload type, decoupling the client from the physical server names and automatically handling failover routing.

Key Concept

Azure SQL Managed Instance Failover Groups and Network Requirements
Rate this question

Topics

Design Relational Database HA and DR

More questions from this topic