AZ-305 ยท High availability design
Zone redundancy, geo-replication and failover groups for relational data
Zone-redundant Azure SQL Database, active geo-replication vs failover groups (listener endpoints, automatic failover), SQL Managed Instance failover groups, flexible server HA.
Key points
- Zone-redundant SQL Database: vCore tiers and Premium; not Basic or Standard.
- Active geo-replication: per database, asynchronous, up to four readable secondaries; endpoint changes after failover.
- Failover groups: fail over together; fixed listeners <fog-name>.database.windows.net (read-write), <fog-name>.secondary.database.windows.net (read-only).
- Policy: customer managed (recommended) or Microsoft managed (1+ hour grace period).
Source: https://learn.microsoft.com/en-us/azure/azure-sql/database/failover-group-sql-db?view=azuresql
Practice questions
A failover group is named fog-orders. Which server name should a read-write application use in its connection string?
- fog-orders.secondary.database.windows.net
- fog-orders.database.windows.net
- The current primary server's own name
- The geo-secondary server's own name
Show answer
Answer: B. fog-orders.database.windows.net
The read-write listener is <fog-name>.database.windows.net, a CNAME that always points to the current primary. The .secondary. form is the read-only listener; the physical server names change role after a failover, so hard-coding either of them breaks the app.
Which statements about active geo-replication and failover groups in Azure SQL Database are correct?
- Active geo-replication is configured per database
- A primary can have up to four geo-secondaries
- After a geo-replication failover the app's endpoint changes
- A failover group's secondary may be in the primary's region
- Geo-replication commits each transaction on both sides synchronously
Show answer
Answer: A. Active geo-replication is configured per database, B. A primary can have up to four geo-secondaries, C. After a geo-replication failover the app's endpoint changes
Active geo-replication is configured per database, supports up to four geo-secondaries per primary, and after a failover the connection endpoint changes because the new primary sits on another logical server. A failover group's secondary server cannot be in the same region as the primary, and geo-replication is asynchronous, not synchronous.
Every Azure SQL Database service tier, including Basic and Standard (DTU), can be configured as zone redundant.
Show answer
Answer: False
False. Zone redundancy is available for General Purpose, Business Critical and Hyperscale in the vCore model and only for Premium in the DTU model. Basic and Standard databases must change tier to become zone redundant.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
