Courseiva
Describe Azure architecture and servicesmediumMultiple ChoiceObjective-mapped

AZ-900 Describe Azure architecture and services Practice Question

A company is designing a disaster recovery solution for a multi-tier application hosted in Azure. They need to ensure that if an entire Azure region becomes unavailable, the application can fail over to another region. The application uses Azure SQL Database. Which Azure feature should they use to replicate the database across regions?

⚠ Common exam trap

Watch out — candidates often confuse geo-replication (which only replicates data) with failover groups (which provide automated failover and connection management), leading them to choose Option A because they think replication alone is sufficient for disaster recovery.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

B) Azure SQL Database automatic failover groups

Azure SQL Database automatic failover groups (Option B) are the correct choice because they provide automated, orchestrated failover of a group of databases across regions, ensuring the entire multi-tier application can fail over when an Azure region becomes unavailable. Unlike geo-replication, which only replicates data, failover groups manage the entire logical server and its databases, including updating the connection string endpoint to the secondary region, which is essential for application continuity.

Answer analysis

Option-by-option breakdown

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

  • A) Azure SQL Database geo-replication

    Why it's wrong here

    Geo-replication creates an asynchronous readable secondary in another Azure region, but it requires manual failover: an administrator must initiate the failover and then update connection strings or point applications to the secondary. There is no automatic listener or transparent redirection, and failover is not instantaneous, so the database becomes unavailable during the manual transition. Automatic failover groups, which build on geo-replication, add the automatic and transparent failover capability that pure geo-replication lacks.

    When this WOULD be correct

    This option would be correct if the question asked for a feature to replicate a single Azure SQL Database to a secondary region for read-only access or to enable manual failover, without requiring automatic failover or coordinated failover of multiple databases.

  • B) Azure SQL Database automatic failover groups

    Why this is correct

    Automatic failover groups are the correct DR mechanism for Azure SQL Database because they provide automatic, transparent failover to a secondary replica in a paired region. They maintain a readable secondary, manage replication at the database or elastic pool level, and expose a listener endpoint so applications can reconnect without manual intervention or connection string changes. This directly satisfies the requirement for automatic failover in a multi-tier disaster recovery solution.

  • C) Azure Traffic Manager

    Why it's wrong here

    Traffic Manager is a DNS-based traffic routing service that distributes incoming connections to healthy endpoints across regions, but it does not replicate, synchronize, or fail over database data. It has no visibility into the read/write state of an Azure SQL Database and cannot guarantee database consistency or availability during a region outage. In a multi-tier DR design, Traffic Manager can route web-tier requests but is not an alternative to a SQL-native replication and failover mechanism.

    When this WOULD be correct

    A company needs to distribute incoming web traffic across multiple Azure regions for high availability and low latency, without requiring database replication. The question would specify that the application is stateless and only needs DNS-level routing to healthy endpoints.

  • D) Azure Site Recovery

    Why it's wrong here

    Azure Site Recovery is designed to orchestrate replication and failover for infrastructure-as-a-service workloads, specifically Azure VMs and on-premises or cloud-based physical/virtual machines. It cannot replicate an Azure SQL Database, since a managed PaaS database does not run on a VM that Site Recovery controls, and it lacks the database-aware replication and consistency features that SQL Database requires. Therefore, while Site Recovery supports multi-tier VM-based DR, it cannot serve as the database failover component.

    When this WOULD be correct

    A company runs a multi-tier application on Azure VMs and needs to replicate the entire application (including VMs, networking, and storage) to another region for disaster recovery. Azure Site Recovery would be the correct choice to orchestrate failover of the VM-based workloads.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-900 exam frequently reuses these exact scenarios with slightly different constraints.

B) Azure SQL Database automatic failover groupsCorrect answer

Why this is correct

Automatic failover groups are the correct DR mechanism for Azure SQL Database because they provide automatic, transparent failover to a secondary replica in a paired region. They maintain a readable secondary, manage replication at the database or elastic pool level, and expose a listener endpoint so applications can reconnect without manual intervention or connection string changes. This directly satisfies the requirement for automatic failover in a multi-tier disaster recovery solution.

A) Azure SQL Database geo-replicationWrong answer — click to see why

Why this is wrong here

Azure SQL Database geo-replication provides asynchronous replication at the database level but does not include automatic failover orchestration. The question requires automatic failover for a multi-tier application, which is provided by failover groups, not geo-replication alone.

★ When this WOULD be the correct answer

This option would be correct if the question asked for a feature to replicate a single Azure SQL Database to a secondary region for read-only access or to enable manual failover, without requiring automatic failover or coordinated failover of multiple databases.

Why candidates choose this

Candidates may confuse geo-replication with failover groups because both involve cross-region replication, and geo-replication is a prerequisite for failover groups. They might assume geo-replication alone provides automatic failover, which it does not.

C) Azure Traffic ManagerWrong answer — click to see why

Why this is wrong here

Azure Traffic Manager is a DNS-based traffic load balancer that distributes traffic across endpoints, but it does not replicate or synchronize database data. For database replication across regions, a database-level feature like geo-replication or failover groups is required.

★ When this WOULD be the correct answer

A company needs to distribute incoming web traffic across multiple Azure regions for high availability and low latency, without requiring database replication. The question would specify that the application is stateless and only needs DNS-level routing to healthy endpoints.

Why candidates choose this

Candidates may confuse Traffic Manager's regional failover capability with database replication, thinking that routing traffic to another region automatically handles database failover, without understanding that database data must be replicated separately.

D) Azure Site RecoveryWrong answer — click to see why

Why this is wrong here

Azure Site Recovery orchestrates replication and failover of IaaS VMs and physical servers, not Azure SQL Database. For database-level replication across regions, Azure SQL Database's built-in geo-replication or failover groups are required.

★ When this WOULD be the correct answer

A company runs a multi-tier application on Azure VMs and needs to replicate the entire application (including VMs, networking, and storage) to another region for disaster recovery. Azure Site Recovery would be the correct choice to orchestrate failover of the VM-based workloads.

Why candidates choose this

Candidates may confuse Azure Site Recovery as a general disaster recovery solution that covers all Azure resources, including databases, not realizing that Azure SQL Database has its own native replication features that are separate from Site Recovery.

Analysis generated from the official AZ-900blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

About these practice questions

Courseiva writes every AZ-900 question from scratch — 981 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This AZ-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-900 exam.