An e-sports tournament platform is designing a disaster recovery and high availability strategy for its matchmaking and player state tracking database layer. The platform has the following requirements:
- The database must support SQL Server Agent jobs and native cross-database queries.
- The primary database must be deployed in the Business Critical tier in East US.
- A secondary replica must be configured in West US to meet a Recovery Time Objective (RTO) of less than seconds and a Recovery Point Objective (RPO) of less than seconds.
- Client applications must automatically reconnect to the active primary replica without manual connection string modifications during a failover.
- Read-only analytics queries must be offloaded to the secondary replica.
- All database replication traffic must travel privately over Microsoft's backbone network without traversing the public internet.
To implement this, the database administration team peers the virtual networks (VNets) in East US and West US, opens ports and in the Network Security Groups (NSGs), deploys the primary Azure SQL Managed Instance, and deploys the secondary Azure SQL Managed Instance. However, when they attempt to establish an auto-failover group, the configuration fails.
Which of the following options identifies the cause of this failure and the correct configuration step to resolve it?
- The secondary managed instance was deployed with a default, distinct DNS zone prefix. You must delete the secondary instance and recreate it while specifying the primary instance as the DNS zone partner to ensure they share the same DNS zone.Cevap
- BAzure SQL Managed Instance does not natively support auto-failover groups across different Azure regions. You must configure active geo-replication instead and deploy an Azure Traffic Manager profile to handle client connection routing.
- CThe Business Critical service tier for Azure SQL Managed Instance does not support auto-failover groups. You must downgrade both the primary and secondary instances to the General Purpose tier to establish a failover group.
- DThe replication group is failing to synchronize because the secondary instance's virtual machine host was provisioned with Standard HDD storage for its transaction log files. You must replace the virtual disks of the secondary instance with Premium SSDs to support the high IOPS replication write load.