Examkin

Question

Difficulty: HardConfigure VMs for High Availability

VeloTransit Solutions has two virtual machines named VM-AppSource1 and VM-AppSource2 deployed in the South Central US region. Currently, both virtual machines are configured as standalone instances with no high availability options selected.

A new corporate compliance policy requires that these virtual machines be configured to guarantee a minimum virtual machine uptime SLA of 99.95% against localized hardware failures.

You need to configure the virtual machines to meet the compliance policy while preserving their existing data and configurations.

Which action should you perform?

  1. A
    Create a new Availability Set. In the Azure portal, navigate to the properties of VM-AppSource1 and VM-AppSource2, change the Availability Set setting to the new Availability Set, and restart the virtual machines.
  2. B
    Create a new Availability Set. Configure the Availability Set to span across multiple Availability Zones in the South Central US region, and redeploy VM-AppSource1 and VM-AppSource2 into the Availability Set.
  3. Delete VM-AppSource1 and VM-AppSource2 while preserving their OS disks. Create a new Availability Set, and then recreate the virtual machines from the preserved OS disks, assigning them to the new Availability Set.Answer
  4. D
    Create a Proximity Placement Group. Associate VM-AppSource1 and VM-AppSource2 with the Proximity Placement Group to automatically assign them to a system-managed Availability Set.

Answer

Delete VM-AppSource1 and VM-AppSource2 while preserving their OS disks. Create a new Availability Set, and then recreate the virtual machines from the preserved OS disks, assigning them to the new Availability Set.
The correct action is to delete the virtual machines while preserving their OS disks, create a new Availability Set, and recreate the VMs using those disks. Azure virtual machines cannot be added to an Availability Set once they are deployed. Deleting only the VM resource leaves the managed OS disk intact, which can then be used as the source for recreating the VM. Specifying the Availability Set during this recreation process allows the configuration to take effect, satisfying the 99.95% SLA requirement.

Step-by-Step Solution

1
Determine the high availability requirements to meet the 99.95% SLA.
Identify that placing the virtual machines into an Availability Set is required to guarantee a 99.95% SLA for multi-instance VM deployments.
An Availability Set distributes VMs across multiple physical hardware nodes (fault and update domains) to prevent concurrent downtime from localized failures.
2
Assess whether existing running VMs can be directly placed into an Availability Set.
Acknowledge that Azure does not allow associating an existing standalone VM with an Availability Set; the configuration must be specified at VM creation.
The association with an Availability Set must be defined during the initial provisioning phase of the virtual machine resource.
3
Formulate a redeployment strategy that preserves existing data.
Decide to delete the existing virtual machine resources while ensuring that the underlying managed OS disks are preserved (not deleted).
Preserving the OS disks ensures that all installed software, configuration settings, and data remain intact for the new VMs.
4
Recreate the virtual machines and associate them with the new Availability Set.
Create a new Availability Set, and then provision new virtual machines using the preserved OS disks, assigning them to the newly created Availability Set.
This achieves the desired high availability status and compliance SLA while maintaining the data and state of the original VMs.

Key Concept

You cannot add an existing Azure Virtual Machine to an Availability Set after creation. The VM must be recreated from its preserved OS disk and assigned to the Availability Set during provisioning.
Rate this question

Topics

Configure VMs for High Availability

More questions from this topic