Examkin

Question

Difficulty: HardConfigure VMs for High Availability

Krypton Labs is planning to deploy a new application in the East US 2 region. The application architecture consists of a web tier with two virtual machines (VM-Web1 and VM-Web2) and a database tier with two virtual machines (VM-Db1 and VM-Db2).

The deployment must satisfy the following requirements:
- The web tier must be protected against datacenter-wide outages.
- The database tier VMs must be located in the same physical datacenter to maintain minimal network latency.
- Traffic must be distributed across the web tier VMs.

Which of the following configurations should you select to meet these requirements?

  1. A
    Deploy VM-Web1 and VM-Web2 across different Availability Zones and associate them with a Basic Load Balancer. Deploy VM-Db1 and VM-Db2 within an Availability Set.
  2. Deploy VM-Web1 and VM-Web2 across different Availability Zones and associate them with a Standard Load Balancer. Deploy VM-Db1 and VM-Db2 within an Availability Set.Answer
  3. C
    Deploy VM-Web1 and VM-Web2 within an Availability Set and associate them with a Standard Load Balancer. Deploy VM-Db1 and VM-Db2 across different Availability Zones.
  4. D
    Deploy VM-Web1, VM-Web2, VM-Db1, and VM-Db2 within a single Availability Set and associate all virtual machines with a Standard Load Balancer.

Answer

Deploy the web tier virtual machines (VM-Web1 and VM-Web2) across different Availability Zones using a Standard Load Balancer, and deploy the database tier virtual machines (VM-Db1 and VM-Db2) within an Availability Set.
Deploying the web tier virtual machines across different Availability Zones protects them from datacenter-wide outages because Availability Zones are physically separate datacenters within an Azure region. Since the web tier virtual machines span different Availability Zones, a Standard Load Balancer must be used, as the Basic SKU does not support zone-spanning configurations. Placing the database tier virtual machines within a single Availability Set keeps them within the same physical datacenter to minimize network latency while protecting them against hardware failures through fault and update domains.

Step-by-Step Solution

1
Analyze the high availability requirements for the web tier.
The web tier requires protection against datacenter-wide outages, which necessitates the use of Availability Zones (physically separate datacenters within a region) rather than Availability Sets (logical groupings within a single datacenter).
Availability Zones offer protection from datacenter-level failures, whereas Availability Sets only protect against localized hardware failures within a single datacenter.
2
Select the correct Load Balancer SKU for the web tier.
A Standard Load Balancer must be chosen to distribute traffic to the web tier VMs across different Availability Zones.
A Basic Load Balancer does not support zone-redundant backend pools or spanning across Availability Zones.
3
Analyze the network latency requirements for the database tier.
The database tier VMs must be in the same datacenter to minimize network latency, which is achieved by deploying them in an Availability Set.
An Availability Set ensures the VMs are kept within the same physical datacenter to avoid cross-zone latency while still providing protection against hardware failures via fault and update domains.

Key Concept

Configuring VMs for high availability involves choosing between Availability Zones for zone-level resilience and Availability Sets for rack-level resilience within a single datacenter, along with matching supporting resources like the Standard Load Balancer SKU.
Estimated Time:2m 0s
Rate this question

Topics

Configure VMs for High Availability

More questions from this topic