DP-900 Practice Question: Identify considerations for relational data on Azure

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Azure SQL Database with active geo-replication

  Why this is correct

  Active geo-replication continuously replicates committed transactions from the primary Azure SQL Database to a secondary database in a different Azure region. When combined with an auto-failover group, the service automatically promotes that readable secondary if the primary becomes unavailable, providing a defined recovery point objective (typically up to 5 seconds of data loss) and recovery time objective. This design specifically satisfies the requirement for automated regional failover.

• ✗

  Azure SQL Managed Instance with local redundancy

  Why it's wrong here

  Azure SQL Managed Instance with locally redundant storage (LRS) keeps multiple synchronous copies of data within a single data center and a single region, so it protects against local hardware failures but not against a regional outage. Although Azure SQL Managed Instance does support failover groups for geo-replication, the option as stated omits that configuration and instead specifies local redundancy, which has no automatic failover capability to another region. Therefore it fails the stated business continuity requirement.

• ✗

  Azure Database for PostgreSQL with read replicas

  Why it's wrong here

  Read replicas in Azure Database for PostgreSQL are asynchronous, read-only copies of the primary used to offload analytic or reporting traffic, not to provide automatic regional failover. While a replica can be manually promoted to the primary in a failover scenario, that promotion is an explicit operational action and the replica does not accept write operations before promotion. Additionally, asynchronous replication means you may lose recent writes if you are forced to fail over, so this option does not meet an automatic, regional recovery requirement.

• ✗

  Azure SQL Database (single database)

  Why it's wrong here

  A single Azure SQL Database, without a failover group or an explicitly configured geo-replicated secondary, is deployed to one logical server and relies on local high availability (such as availability zones within the same region). That local high availability keeps copies within the same region and does not automatically redirect traffic to another Azure region if the entire region goes down. To get automatic regional failover, you must pair that single database with active geo-replication or add it to an auto-failover group, neither of which is implied by the phrase single database alone.

Go deeper

Related to this question