Examkin

Soru

Zorluk: Çok zorDesign Relational Database HA and DR

A logistics company is designing a highly available and disaster-resilient relational database backend for its global fleet-tracking application. The database tier must support cross-database queries and SQL Server Agent jobs to orchestrate daily ETL tasks. The disaster recovery design must meet a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 seconds. All failover operations must occur automatically without requiring client application connection string modifications, and all reporting queries must be dynamically offloaded to a readable secondary replica in the disaster recovery region. To maintain compliance, all database replication traffic must remain isolated from the public internet.

Which two configurations should you include in the disaster recovery design?

  1. Deploy Azure SQL Managed Instance in the primary and secondary regions, configure a failover group, and configure client applications to connect using the failover group's read-write and read-only listener endpoints.Cevap
  2. Configure Global Virtual Network Peering between the virtual networks hosting the primary and secondary Azure SQL Managed Instances to facilitate database replication.Cevap
  3. C
    Deploy Azure SQL Managed Instance in the primary and secondary regions, configure Active Geo-Replication between the databases, and configure the application to connect using the primary server's endpoint.
  4. D
    Deploy Azure SQL Database Business Critical databases in the primary and secondary regions, configure a failover group, and configure the application to connect using the failover group's read-write and read-only listener endpoints.

Cevap

Deploy Azure SQL Managed Instance in a failover group with read-write and read-only listener endpoints, and configure Global Virtual Network Peering between the virtual networks hosting the instances.
The correct architecture uses Azure SQL Managed Instance to support cross-database queries and SQL Server Agent jobs. Configuring a failover group satisfies the requirements for low RTO/RPO, automatic failover, and dynamic read-scale routing using listener endpoints. Establishing Global Virtual Network Peering between the hosting virtual networks ensures that replication traffic remains private and does not traverse the public internet.

Adım Adım Çözüm

1
Analyze database feature requirements
Identify that SQL Server Agent and cross-database queries require Azure SQL Managed Instance rather than Azure SQL Database.
Choosing the correct deployment option ensures legacy compatibility constraints are satisfied.
2
Analyze high availability and disaster recovery requirements
Identify that automatic failover without connection string changes and dynamic read-scale routing require a failover group with listener endpoints.
Failover groups provide read-write and read-only listeners that automatically redirect traffic during failovers.
3
Analyze network isolation requirements
Identify that replication traffic between SQL Managed Instances must flow securely. Global Virtual Network Peering provides direct, private IP connectivity over the Microsoft backbone network.
Replication for SQL Managed Instance failover groups must be configured over a private network connection (VPN or Peering).

Anahtar Kavram

Designing disaster recovery and high availability for Azure SQL Managed Instance using failover groups and Global VNet Peering to meet performance, network isolation, and compatibility requirements.
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

Design Relational Database HA and DR

Bu konudan daha fazla soru