Question

Difficulty: Very hardReliability, Predictability, and Disaster Recovery

A financial services company is migrating a core transaction processing application to Microsoft Azure. The systems architect must ensure the solution complies with two strict operational requirements:

1. The application must survive the complete outage of a primary Azure region, with a maximum recovery time (RTO) of 44 hours and a maximum data loss (RPO) of 1515 minutes.
2. The application's compute resources must maintain consistent query response times (predictability) during sudden, short-lived spikes in traffic, and automatically scale down capacity to minimize cost when transaction volume decreases.

Which combination of cloud design concepts and capabilities must the architect implement to satisfy these requirements?

  1. Disaster recovery using cross-region replication to meet the recovery objectives, and cloud elasticity to automatically scale compute resources to maintain predictable performance.Answer
  2. B
    High availability using multiple Availability Zones in the primary region to meet the recovery objectives, and cloud scalability to manually adjust resources to maintain predictable performance.
  3. C
    Disaster recovery using Availability Zones distributed across separate geographical regions to meet the recovery objectives, and cloud scalability to dynamically scale resources to maintain predictable performance.
  4. D
    Disaster recovery using cross-region replication to meet the recovery objectives, and cloud scalability using a fixed maximum capacity to ensure predictable performance and cost.

Answer

Disaster recovery using cross-region replication to meet the recovery objectives, and cloud elasticity to automatically scale compute resources to maintain predictable performance.
The correct answer combines disaster recovery via cross-region replication to satisfy the recovery objectives (RTO/RPO) for regional outages, and cloud elasticity to automatically adjust resources to handle traffic spikes and scale down to minimize cost. This directly fulfills both parts of the business requirements.

Step-by-Step Solution

1
Analyze the first requirement regarding surviving a complete primary Azure region outage within specific recovery metrics (44 hours RTO and 1515 minutes RPO).
Determine that local redundancy or single-region high availability (such as Availability Zones) is insufficient for regional outages. A disaster recovery (DR) strategy with cross-region replication is required.
Disaster recovery addresses recovery from catastrophic regional events, whereas High Availability focuses on localized failures within a single region.
2
Analyze the second requirement regarding maintaining consistent performance during traffic surges while minimizing cost during low-demand periods.
Determine that cloud elasticity is required to dynamically scale compute capacity up and down automatically in response to varying workloads.
Elasticity provides the automation needed to scale down resources to optimize costs, distinguishing it from static scaling or manual scaling.
3
Synthesize the requirements to identify the option that correctly pairs disaster recovery (with cross-region replication) and elasticity.
Select the correct combination that matches disaster recovery and elasticity.
Only this option addresses both regional disaster survival and automated cost-efficient performance scaling.

Key Concept

Distinguishing between Disaster Recovery (cross-region resilience) and High Availability (intra-region resilience), and between Elasticity (dynamic auto-scaling) and Scalability (static or manual provisioning).
Estimated Time:2m 0s
Rate this question