Soru

Zorluk: OrtaDesign Relational Database HA and DR

An organization is migrating a legacy on-premises application to Azure. The database tier has the following requirements:
- Must support native SQL Server Agent jobs and cross-database queries.
- Must provide a disaster recovery (DR) solution to a secondary Azure region with a Recovery Time Objective (RTO) of 15 minutes.
- Must automatically route both read-write and read-only traffic to the active database replicas without requiring modifications to the application connection strings during a failover.

Which database deployment and disaster recovery strategy should you recommend?

  1. A
    Deploy Azure SQL Database (Single Database) in a primary region, configure active geo-replication to a secondary region, and configure an auto-failover group. Use the read-write and read-only listener endpoints in the application connection strings.
  2. Deploy Azure SQL Managed Instance in a primary region, configure an auto-failover group with a secondary Managed Instance in a paired region, and configure the application to use the read-write and read-only listener endpoints.Cevap
  3. C
    Deploy Azure SQL Managed Instance in a primary region, configure active geo-replication to a secondary Managed Instance, and update the DNS records manually to redirect traffic to the secondary instance during a failover event.
  4. D
    Deploy SQL Server on Azure Virtual Machines using Standard HDD disks for transaction log files, and configure SQL Server Always On availability groups across two Azure regions with automatic failover.

Cevap

Deploy Azure SQL Managed Instance in a primary region, configure an auto-failover group with a secondary Managed Instance in a paired region, and configure the application to use the read-write and read-only listener endpoints.
The correct strategy is to deploy Azure SQL Managed Instance and configure an auto-failover group. Azure SQL Managed Instance supports the required legacy on-premises SQL Server features (SQL Server Agent and cross-database queries). The auto-failover group provides automatic failover capabilities to a secondary region within the RTO target, and offers read-write and read-only listener endpoints that transparently route application traffic without requiring connection string modifications.

Adım Adım Çözüm

1
Analyze the database compatibility requirements.
The application requires cross-database queries and SQL Server Agent jobs, which rules out Azure SQL Database (Single Database) and indicates that Azure SQL Managed Instance is the appropriate managed service.
Azure SQL Managed Instance offers near 100% compatibility with the on-premises SQL Server database engine, including SQL Agent and cross-database queries.
2
Evaluate the disaster recovery and traffic routing requirements.
The solution requires automatic routing of read-write and read-only traffic to a secondary region during a failover without updating application connection strings.
Auto-failover groups for Azure SQL Managed Instance provide a read-write listener and a read-only listener that remain constant regardless of which region is active.
3
Verify storage and performance best practices.
Ensure premium storage is used for database logs to prevent performance degradation, which makes options utilizing Standard HDD invalid.
Database transaction logs require high throughput and low latency, which Standard HDD cannot provide.

Anahtar Kavram

Azure SQL Managed Instance auto-failover groups support automatic redirection of read-write and read-only traffic via listeners while maintaining on-premises SQL Server feature compatibility.
Bu soruyu puanla