Question

Difficulty: Very hardConfigure VMs for High Availability

Aetheris Logistics is planning the deployment of a new line-of-business application in the East US 2 region. The architecture consists of three web tier virtual machines (VM-Web-Prod1, VM-Web-Prod2, and VM-Web-Prod3) and two database tier virtual machines (VM-DB-Prod1 and VM-DB-Prod2).

The deployment must satisfy the following requirements:
- The web tier must achieve a service level agreement (SLA) of at least 99.99%99.99\% virtual machine uptime and be resilient against datacenter-wide failures.
- The database tier must be protected against localized hardware failures, such as server rack or power outages, within a single datacenter. The database tier does not require zone-wide redundancy.
- All high availability configurations must be applied during the initial deployment phase.

Which two configuration actions should you perform? (Select two.)

  1. Deploy VM-Web-Prod1, VM-Web-Prod2, and VM-Web-Prod3 across three separate Availability Zones.Answer
  2. Deploy VM-DB-Prod1 and VM-DB-Prod2 in a new Availability Set.Answer
  3. C
    Deploy VM-Web-Prod1, VM-Web-Prod2, and VM-Web-Prod3 across separate Availability Zones and group them inside a single Availability Set.
  4. D
    Deploy VM-DB-Prod1 and VM-DB-Prod2 as standalone virtual machines, and then associate them with a new Availability Set after deployment.

Answer

Deploying the web tier virtual machines across three separate Availability Zones, and deploying the database tier virtual machines in a new Availability Set.
To achieve a 99.99%99.99\% uptime SLA and protect the web tier against datacenter-wide failures, the web VMs must be distributed across separate Availability Zones. To protect the database tier against localized hardware failures (like a rack failure) within a single datacenter without requiring zone redundancy, the database VMs must be deployed in an Availability Set. Both configurations must be specified at the time of virtual machine creation.

Step-by-Step Solution

1
Analyze the high availability and SLA requirements for the web tier VMs (VM-Web-Prod1, VM-Web-Prod2, VM-Web-Prod3).
The web tier requires a 99.99%99.99\% uptime SLA and resilience against datacenter-wide outages.
This requirement determines that Azure Availability Zones must be used, as Availability Zones provide isolation across separate physical datacenters within a region and support the 99.99%99.99\% SLA.
2
Analyze the high availability requirements for the database tier VMs (VM-DB-Prod1, VM-DB-Prod2).
The database tier requires protection against localized hardware failures (such as server rack or power outages) but does not need zone-wide redundancy.
An Availability Set meets this requirement by distributing VMs across multiple physical hardware racks (fault domains) and maintenance groups (update domains) within a single datacenter, providing a 99.95%99.95\% SLA.
3
Evaluate the feasibility of combining Availability Zones and Availability Sets for the web tier.
Determine that placing VMs in both Availability Zones and a single Availability Set is invalid.
Availability Zones and Availability Sets are mutually exclusive configuration options during VM deployment. An Availability Set cannot span across multiple Availability Zones.
4
Evaluate the timing requirements for configuring the Availability Set for the database tier.
Determine that the database VMs must be placed in the Availability Set during creation.
Azure does not support adding an existing, deployed standalone virtual machine to an Availability Set. It must be configured during the VM creation process.

Key Concept

Azure Virtual Machine High Availability configurations, specifically the features, limitations, and mutual exclusivity of Availability Zones and Availability Sets.
Rate this question