Your company runs a mission-critical application on Azure SQL Database in the East US region. You need to ensure automatic failover with zero data loss in case of a regional outage. Which deployment option should you use?
Trap 1: Deploy a General Purpose tier database with geo-replication.
Incorrect. General Purpose tier geo-replication is asynchronous, meaning potential data loss (RPO > 0).
Trap 2: Deploy a Hyperscale tier database with zone redundancy.
Incorrect. Hyperscale tier does not support synchronous replication for auto-failover groups; its geo-replication is asynchronous, and zone redundancy is within-region only.
Trap 3: Deploy a Serverless tier database with active geo-replication.
Incorrect. Serverless tier is not designed for mission-critical workloads and lacks the required availability and replication features.
- A
Deploy a Business Critical tier database and configure an auto-failover group with a readable secondary in a paired region.
Auto-failover groups provide automatic regional failover with a readable secondary, and Business Critical tier uses local SSD with synchronous replication, satisfying the zero-data-loss constraint. The paired-region secondary enables recovery from a full East US outage.
- B
Deploy a General Purpose tier database with geo-replication.
Why it fails: Incorrect. General Purpose tier geo-replication is asynchronous, meaning potential data loss (RPO > 0).
- C
Deploy a Hyperscale tier database with zone redundancy.
Why it fails: Incorrect. Hyperscale tier does not support synchronous replication for auto-failover groups; its geo-replication is asynchronous, and zone redundancy is within-region only.
- D
Deploy a Serverless tier database with active geo-replication.
Why it fails: Incorrect. Serverless tier is not designed for mission-critical workloads and lacks the required availability and replication features.