A healthtech company hosts a telemedicine platform on Azure virtual machines (VMs) in the … — Microsoft Azure Solutions Architect (AZ-305)

A healthtech company hosts a telemedicine platform on Azure virtual machines (VMs) in the East US region and is designing a disaster recovery (DR) solution to the West US region. The platform consists of a web tier, an application tier, and a database tier. The workload profiles and metrics are as follows:

- Web and Application Tiers: Four VMs (two web, two app) using Standard SSDs, with a maximum write churn of $2\text{ MB/s}$ per VM.
- Database Tier: Two VMs running SQL Server on Windows Server using Premium SSD (P30) disks. Each database VM has one log disk with a continuous write churn of $26\text{ MB/s}$ and one data disk with a write churn of $6\text{ MB/s}$ .

Your disaster recovery design must satisfy the following business requirements:
- A Recovery Point Objective (RPO) of $4\text{ hours}$ for the web and application tiers.
- An RPO of $10\text{ seconds}$ for the database tier.
- A Recovery Time Objective (RTO) of $1\text{ hour}$ for the entire platform.

Which disaster recovery architecture should you design to meet these requirements?

Replicate the web and application tier VMs to the target region using Azure Site Recovery. Replicate the database tier by configuring SQL Server Always On availability groups with asynchronous commit to database replicas in the target region.Cevap
B
Replicate all virtual machines, including the database tier, to the target region using Azure Site Recovery with default replication configurations.
C
Replicate all virtual machines to the target region using Azure Site Recovery, configuring the database VMs to use the High Churn replication policy tier.
D
Configure Azure Backup to perform hourly application-consistent backups of all virtual machines, replicating the backups to a Geo-Redundant Storage vault in the target region.

Cevap

Replicate the web and application tier VMs to the target region using Azure Site Recovery. Replicate the database tier by configuring SQL Server Always On availability groups with asynchronous commit to database replicas in the target region.

The correct design uses Azure Site Recovery to replicate the low-churn web and application tiers, and SQL Server Always On availability groups with asynchronous commit to replicate the database tier. This avoids ASR's disk write churn limit, which maxes out at

20\text{ MB/s}

per Premium SSD even when using the High Churn tier, and satisfies the database tier's strict

10\text{-second}

RPO requirement.

Adım Adım Çözüm

Analyze the database write churn rates against Azure Site Recovery limits.

The database log disk experiences

26\text{ MB/s}

of write churn. Standard Azure Site Recovery (ASR) supports up to

10\text{ MB/s}

per Premium SSD disk, and the High Churn policy tier supports up to

20\text{ MB/s}

per Premium SSD disk. Thus, the database's write churn exceeds ASR capacity thresholds.

To verify if ASR can support the write-heavy database workload.

Evaluate the Recovery Point Objective (RPO) requirements.

The web and application tiers require a

4\text{-hour}

RPO, which is easily achievable by ASR. The database tier requires a

10\text{-second}

RPO, which cannot be guaranteed by ASR replication intervals.

To determine if ASR replication intervals are sufficient for the database data loss threshold.

Select replication mechanisms for each tier to construct the design.

Use ASR for the web and application tiers because it meets the

4\text{-hour}

RPO and

1\text{-hour}

RTO. Use SQL Server Always On availability groups with asynchronous commit for the database tier to support both the high write churn and the

10\text{-second}

RPO.

To combine ASR and native database replication into a unified, compliant disaster recovery strategy.

Anahtar Kavram

Azure Site Recovery churn limits and database-native replication integration

Tahmini Süre:2m 30s

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular

Bu konudan daha fazla soru