Question

Difficulty: Very hardConfigure VMs for High Availability

A logistics company, Zenith Freight Services, is migrating a multi-tier workload to the Sweden Central region. The deployment must adhere to the following strict requirements:

- The database layer (22 virtual machines) requires a VM-level compute uptime SLA of at least 99.99%99.99\%.
- The application layer (33 virtual machines) requires protection against localized hardware failures and updates within a single datacenter, while ensuring network latency between the instances is minimized.
- The web layer (22 existing standalone virtual machines: WebVM-Prod1 and WebVM-Prod2) must be integrated into a configuration that guarantees a 99.95%99.95\% compute SLA.

Which configuration strategy should the administrator implement to meet all requirements?

  1. Deploy the database VMs across multiple Availability Zones, deploy the application VMs in an Availability Set, and delete the existing web VMs, recreating them from their OS disks within a new Availability Set.Answer
  2. B
    Deploy the database VMs in an Availability Set, deploy the application VMs across multiple Availability Zones, and add the existing web VMs directly to the application Availability Set.
  3. C
    Deploy the database VMs across multiple Availability Zones, deploy the application VMs in an Availability Set that spans multiple Availability Zones, and enable the high availability setting on the existing web VMs' configuration properties.
  4. D
    Deploy both the database and application VMs in a Proximity Placement Group, and attach the existing web VMs to a new Availability Zone by updating their zone assignments in the Azure portal.

Answer

Deploy the database VMs across multiple Availability Zones, deploy the application VMs in an Availability Set, and delete the existing web VMs, recreating them from their OS disks within a new Availability Set.
Deploying the database VMs across multiple Availability Zones meets the 99.99%99.99\% SLA constraint. Placing the application VMs in an Availability Set ensures hardware redundancy (fault/update domains) while maintaining low latency. Deleting the existing web VMs and recreating them from their OS disks in a new Availability Set is the only valid method to transition running standalone VMs into an Availability Set to obtain the 99.95%99.95\% SLA.

Step-by-Step Solution

1
Analyze database high availability requirements.
Database VMs must be deployed across multiple Availability Zones to achieve the required 99.99%99.99\% compute SLA.
Azure offers a 99.99%99.99\% uptime SLA for VMs only when two or more instances are deployed across two or more Availability Zones in the same region.
2
Analyze application tier requirements.
Deploy the application VMs in an Availability Set within a single datacenter.
An Availability Set guarantees a 99.95%99.95\% SLA and distributes the VMs across multiple physical fault and update domains inside one datacenter, keeping inter-VM latency to a minimum.
3
Evaluate integration strategy for existing web VMs.
Plan to delete the existing web VMs and recreate them using their existing OS disks within a new Availability Set.
Azure does not support adding existing standalone VMs to an Availability Set. Recreation is required to change their high availability configuration.

Key Concept

High Availability Configuration and SLAs (Availability Sets vs. Availability Zones)
Rate this question