Question

Difficulty: HardAzure Regions, Availability Zones, and Region Pairs

A company is planning to migrate a legacy financial database to Azure. The architecture must satisfy three key requirements:
1. High availability (HA) that protects the database from a localized power or cooling failure in a single datacenter building.
2. Disaster recovery (DR) that replicates data to a separate geographic region at least 300 miles away to guard against regional disasters, while keeping the data within the same national borders.
3. The database resources must be managed under a Resource Group that was created in a distant region for administrative purposes.

Which deployment strategy should the company choose to meet these requirements?

  1. Deploy the database nodes across multiple Availability Zones in the primary region, configure database replication to the primary region's paired region for disaster recovery, and deploy the database resources in the primary region regardless of the Resource Group's location.Answer
  2. B
    Deploy the database nodes across multiple Availability Zones that span across the primary region and its paired region, configure disaster recovery to use a local Availability Set, and deploy the database in the primary region.
  3. C
    Deploy the database nodes in a single Availability Set to protect against datacenter building outages, configure disaster recovery replication to the paired region, and ensure all database resources are deployed in the same region as the Resource Group to inherit its location.
  4. D
    Deploy the database nodes across multiple regions for low-latency high availability, configure disaster recovery replication within a single Availability Zone in the primary region, and ensure resources are in the same region as the Resource Group.

Answer

Deploy the database nodes across multiple Availability Zones in the primary region, configure database replication to the primary region's paired region for disaster recovery, and deploy the database resources in the primary region regardless of the Resource Group's location.
The correct strategy deploys database nodes across multiple Availability Zones in the primary region to guarantee high availability and resilience against datacenter building failures. It configures replication to the region's paired region, which provides a disaster recovery location at least 300 miles away within the same national border. Finally, it correctly recognizes that Resource Group location does not limit the deployment location of the resources it contains.

Step-by-Step Solution

1
Evaluate the requirement for high availability that protects against a single datacenter building outage.
Identify that Azure Availability Zones (AZs) are required, as each zone consists of one or more datacenters with independent power, cooling, and networking within a single region.
Availability Sets only protect against hardware/rack failures inside a single datacenter, whereas Availability Zones protect against the loss of an entire datacenter building.
2
Evaluate the disaster recovery and data residency requirements.
Identify that the primary region's paired region must be used for disaster recovery replication.
Azure region pairs are situated at least 300 miles apart and reside within the same geography/national boundary (with the exception of Brazil South) to ensure data residency compliance and protection against regional disasters.
3
Evaluate the Resource Group location constraint.
Confirm that resources can be deployed in the primary region even if their parent Resource Group is in a different region.
A Resource Group is a logical metadata container. Its location only dictates where the resource metadata is stored, not where the actual resources must be provisioned.

Key Concept

Understanding the physical and logical boundaries of Azure Regions, Availability Zones, Region Pairs, and Resource Group metadata independence.
Estimated Time:2m 0s
Rate this question