Question

Difficulty: Very hardCreate and Configure Virtual Machines

You are designing the deployment and storage configuration for four Azure Virtual Machines (VMs) to support different application workloads. Match each workload scenario to its correct VM storage or deployment configuration.

  • A database VM named `VM-DB1` running on a Standard_E16bds_v5 size in East US. You need to configure a new data disk that requires up to 80,00080,000 IOPS and 1,200 MB/s1,200\text{ MB/s} throughput, with the ability to dynamically scale throughput without deallocating the VM.An Ultra Disk configuration with Ultra Disk compatibility enabled on the VM.
  • A stateless web application host named `VM-Web1` that requires extremely fast boot times and zero storage costs for the operating system disk. The OS state does not need to be preserved across VM redeployments.An Ephemeral OS disk stored on the local VM cache or temporary storage.
  • A business-critical application VM named `VM-App1` running on a Standard_M16s size that hosts a write-intensive database log file. The log write operations must consistently achieve sub-millisecond latency.A Premium SSD data disk with Host Caching set to None and Write Accelerator enabled.
  • A development VM named `VM-Dev1` running on a Standard_D8ds_v5 size. The VM will host containerized Hyper-V development environments, requiring UEFI, Secure Boot, and virtual Trusted Platform Module (vTPM) capabilities.A Generation 22 VM configured with Trusted Launch.

Answer

Match VM-DB1 to Ultra Disk configuration, VM-Web1 to Ephemeral OS disk, VM-App1 to Premium SSD with Write Accelerator, and VM-Dev1 to Generation 22 VM with Trusted Launch.
The correct matches align each workload requirement with the specific Azure VM compute and storage features: Ultra Disks for extreme, dynamically scaleable performance; Ephemeral OS disks for stateless, cost-optimized hosting; Write Accelerator on Premium SSDs for sub-millisecond write latency on M-series VMs; and Generation 22 with Trusted Launch for UEFI, Secure Boot, and vTPM security features.

Step-by-Step Solution

1
Analyze the requirements for VM-DB1.
The workload requires up to 80,00080,000 IOPS and 1,200 MB/s1,200\text{ MB/s} throughput with dynamic scaling without deallocation. This profile exceeds standard Premium SSD performance and fits Ultra Disk capabilities. Ultra Disks require enabling compatibility during VM creation.
Ultra Disk is the only disk type that supports both these throughput/IOPS levels on a single disk and dynamic throughput adjustment without VM deallocation.
2
Analyze the requirements for VM-Web1.
The workload is stateless, needs fast boot times, and requires zero storage costs for the OS disk. This points to Ephemeral OS disks.
Ephemeral OS disks use local SSD storage (cache or temp disk) inside the host, avoiding remote Azure Storage costs and offering faster boot and reset speeds.
3
Analyze the requirements for VM-App1.
The VM is Standard_M16s (M-series) and requires sub-millisecond database log write latency. This fits Write Accelerator on Premium SSD.
Write Accelerator is specifically designed for write-intensive database logs on M-series VMs using Premium SSDs, and it requires Host Caching to be set to None.
4
Analyze the requirements for VM-Dev1.
The VM needs nested virtualization (Hyper-V containers), UEFI, Secure Boot, and vTPM. This requires a Generation 22 VM with Trusted Launch.
Trusted Launch provides the foundation for Secure Boot and vTPM, which are prerequisites for configuring advanced security and Hyper-V guest environments on Gen 22 VMs.

Key Concept

Selecting the correct Azure Virtual Machine configuration, disk types, and deployment options based on workload performance, cost, and security requirements.
Rate this question