An online gaming company runs its matchmaking database on a single database in Azure SQL Database. You are designing a disaster recovery and high availability solution that replicates database updates to a secondary Azure region. The solution must support automatic failover to the secondary region if the primary region experiences a prolonged outage, without requiring connection string updates in the gaming clients. Additionally, the secondary replica must handle read-heavy analytics queries to offload the primary database. Which database configuration should you recommend?
- AConfigure active geo-replication for the matchmaking database, and configure the analytics clients to connect directly to the secondary server endpoint.
- BDeploy the matchmaking database in a zone-redundant Elastic Pool, and configure active geo-replication to replicate to the secondary region.
- Configure a failover group containing the matchmaking database, and configure the analytics clients to connect using the read-only listener endpoint.Answer
- DConfigure active geo-replication and set up an Azure Traffic Manager profile to route database connection traffic to the primary or secondary database endpoints.
Answer
Configure a failover group containing the matchmaking database, and configure the analytics clients to connect using the read-only listener endpoint.
Configuring a failover group meets all requirements. Failover groups provide automatic failover capabilities with predefined grace periods and expose two DNS listener endpoints: a read-write listener and a read-only listener. The read-only listener automatically routes traffic (such as analytics queries) to the secondary database replica, and client connection strings do not need to be updated during or after a failover.
Step-by-Step Solution
Key Concept
Azure SQL Database failover groups provide automatic cross-region failover and read-only listener endpoints that simplify client connection management.
Estimated Time:1m 30s