Examkin

Soru

Zorluk: ZorDesign Relational Database HA and DR

A company is planning to migrate an on-premises enterprise resource planning (ERP) application to Azure. The application's database layer has the following requirements:
- Must support SQL Server Agent jobs and cross-database queries.
- Must achieve a Recovery Point Objective (RPO) of less than 5 seconds and a Recovery Time Objective (RTO) of less than 30 seconds.
- In the event of a regional disaster, database failover to the secondary region must happen automatically.
- Reporting workloads in the secondary region must run on a read-only replica and must automatically route to the active replica's secondary endpoint without application connection string modifications during failover.
- All network traffic between the database replicas must remain isolated from the public internet.

Which database configuration should you recommend?

  1. A
    Deploy two Azure SQL Databases in different regions, group them into Elastic Pools, and set up a failover group between the pools using a private link.
  2. B
    Deploy two SQL Server instances on Azure Virtual Machines in different regions, configure SQL Server Transactional Replication between them, and use Azure Traffic Manager to route client traffic.
  3. Deploy two Azure SQL Managed Instances in different regions, establish virtual network peering between their virtual networks, and configure a failover group. Route database traffic using the failover group's read-write and read-only listener endpoints.Cevap
  4. D
    Deploy two Azure SQL Databases in different regions, configure active geo-replication between them, and use a DNS alias to manually route read-write and read-only traffic during a failover event.

Cevap

Deploy two Azure SQL Managed Instances in different regions, establish virtual network peering between their virtual networks, and configure a failover group. Route database traffic using the failover group's read-write and read-only listener endpoints.
The correct option satisfies all constraints by using Azure SQL Managed Instance, which supports instance-level features such as SQL Server Agent and cross-database queries. By utilizing virtual network peering, the replication traffic remains isolated from the public internet. Failover groups support automatic failover to meet the low RTO and RPO, and they provide read-write and read-only listener endpoints, eliminating the need to update application connection strings during a failover event.

Adım Adım Çözüm

1
Determine database engine compatibility requirements.
The application requires SQL Server Agent and cross-database queries. This rules out Azure SQL Database (Single Database and Elastic Pools) and points to Azure SQL Managed Instance or SQL Server on Azure VMs.
Choosing the correct deployment model is critical to support legacy on-premises SQL Server features.
2
Evaluate high availability and disaster recovery mechanisms.
To meet an RPO of < 5 seconds and an RTO of < 30 seconds with automatic failover and read-only routing that does not require connection string updates, Azure SQL Managed Instance failover groups are the ideal solution. Active geo-replication requires manual failover, which violates the automatic failover constraint.
Failover groups provide read-write and read-only listener endpoints that point dynamically to the current primary and secondary regions.
3
Select the networking topology for data replication.
Configure virtual network (VNet) peering between the VNets of the primary and secondary Azure SQL Managed Instances.
This guarantees that the replication traffic traverses the Microsoft backbone network privately and remains completely isolated from the public internet.

Anahtar Kavram

Relational Database High Availability and Disaster Recovery using Azure SQL Managed Instance Failover Groups
Bu soruyu puanla

Konular

Design Relational Database HA and DR

Bu konudan daha fazla soru