Examkin

Soru

Zorluk: ZorDesign Relational Database HA and DR

A healthcare provider requires a business continuity strategy for an electronic health record (EHR) database migrating to Azure. The database workload has the following requirements:

* It must support legacy cross-database queries and execute SQL Server Agent jobs for nightly aggregation tasks.
* It must survive a regional outage with a Recovery Time Objective (RTO) of 11 hour and a Recovery Point Objective (RPO) of 55 seconds.
* Failover to the secondary region (West US) must occur automatically, using a single connection endpoint that redirects write traffic without requiring application configuration updates.
* Read-only analytical queries must be offloaded to the secondary region.

You plan to implement Azure SQL Managed Instances in East US (primary) and West US (secondary).

Which of the following configuration actions must you perform to satisfy these requirements? (Select 22.)

  1. Establish virtual network peering or a VPN connection between the virtual networks of the primary and secondary instances, and configure a failover group.Cevap
  2. Manually recreate and synchronize the required SQL Server Agent jobs on the secondary instance.Cevap
  3. C
    Configure active geo-replication for each user database and route connection traffic to the individual primary instance name.
  4. D
    Provision the databases in Azure SQL Database Elastic Pools and execute the scheduled tasks using Elastic Database Jobs.

Cevap

To meet the requirements, you must establish network connectivity (VNet peering or VPN) between the virtual networks of the primary and secondary instances to configure a failover group, and manually recreate and synchronize the SQL Server Agent jobs on the secondary instance.
Establishing virtual network connectivity via peering or VPN is a mandatory prerequisite for setting up a failover group between two Azure SQL Managed Instances. The failover group provides automatic failover and a read-write listener that redirects traffic without connection string changes. Because system databases (including msdb) are not replicated by the failover group, SQL Server Agent jobs must be manually recreated on the secondary instance to ensure they run after a failover.

Adım Adım Çözüm

1
Determine the relational database deployment tier based on legacy requirements.
Select Azure SQL Managed Instance.
The database requires cross-database queries and SQL Server Agent jobs, which are supported in Managed Instance but not in standard Azure SQL Database offerings.
2
Design the network connectivity required for database replication.
Plan virtual network peering or a VPN connection between the virtual networks in East US and West US.
Failover groups for Azure SQL Managed Instance require bidirectional network communication between the instances.
3
Design the cross-region database failover mechanism.
Configure a failover group containing the user databases.
Failover groups provide automatic failover, meet the RTO/RPO limits, and expose a single read-write listener endpoint to abstract connection changes.
4
Design the synchronization plan for scheduled operations.
Deploy identical SQL Server Agent jobs on the secondary instance.
System databases like msdb are not replicated by the failover group, meaning agent jobs must be manually maintained on the secondary server to run after failover.

Anahtar Kavram

Azure SQL Managed Instance HA/DR design using failover groups, virtual network requirements, and handling non-replicated system metadata like SQL Server Agent jobs.
Bu soruyu puanla

Konular

Design Relational Database HA and DR

Bu konudan daha fazla soru