Question

Difficulty: HardCreate and Configure Virtual Machines

An administrator is designing a virtual machine deployment strategy in Azure to support a high-performance, multi-tier application. You need to map each architectural requirement to the correct Azure Virtual Machine configuration or feature. Match each requirement on the left to its corresponding configuration or feature on the right.

  • Provision stateless web servers with zero storage cost for the operating system disk by utilizing the virtual machine's local cache or temporary storage.Ephemeral OS disk configured with the Local diff disk setting
  • Host a database workload that requires adjusting storage throughput up to 2000 MB/s2000\text{ MB/s} and 160000 IOPS160000\text{ IOPS} dynamically without rebooting the virtual machine.Ultra Disk storage capability enabled in the virtual machine additional settings
  • Locate application and database virtual machines within the same physical hardware cluster to achieve the lowest possible network latency between the tiers.Proximity Placement Group association
  • Install and configure a web server service immediately after the virtual machine is provisioned, without opening inbound management ports in the Network Security Group.Custom Script Extension deployment using outbound agent communication

Answer

Stateless web servers with zero OS disk storage cost match with Ephemeral OS disk configured with the Local diff disk setting. Database workload requiring dynamic storage adjustment without reboot matches with Ultra Disk storage capability enabled in the virtual machine additional settings. Locating VMs in the same physical hardware cluster to minimize latency matches with Proximity Placement Group association. Installing and configuring a web server service immediately after provisioning without inbound ports matches with Custom Script Extension deployment using outbound agent communication.
The correct pairings align each workload characteristic to its corresponding Azure design solution. 1. Ephemeral OS disks are hosted on the VM's local SSD cache/temp disk, incurring zero storage fees. 2. Ultra Disks support dynamic performance adjustment (up to 160000 IOPS160000\text{ IOPS} and 2000 MB/s2000\text{ MB/s}) without rebooting, provided the VM has the Ultra SSD capability enabled. 3. Proximity Placement Groups physically cluster VMs together to minimize latency. 4. Custom Script Extensions run via the VM agent, using outbound communication to avoid inbound NSG requirements.

Step-by-Step Solution

1
Analyze the stateless server requirement with zero storage cost.
Identify that Ephemeral OS disks run on the VM's local SSD cache or temp disk, charging zero storage fees and offering lower latency.
Standard managed disks incur storage costs, whereas Ephemeral OS disks utilize existing VM local resources.
2
Analyze the storage throughput and IOPS scaling requirement without reboot.
Identify that Ultra Disk is the only Azure disk type that allows dynamic adjustment of IOPS and throughput without requiring a VM restart or disk detachment, provided the VM's Ultra SSD capability is enabled.
Premium and Standard SSDs require the VM to be deallocated or the disk to be detached to change sizes/performance tiers in most scenarios.
3
Analyze the requirement for physical co-location to reduce latency.
Identify that Proximity Placement Groups (PPGs) force VMs to be deployed in the same physical datacenter/hardware cluster.
Availability Zones spread VMs out to increase resilience, which can increase latency. PPGs do the opposite by grouping them close together.
4
Analyze the requirement for automatic configuration post-deployment without inbound management ports.
Identify that the Custom Script Extension runs locally via the guest VM agent. The VM agent communicates outbound to retrieve the script from Azure Storage, bypassing the need for inbound NSG rules.
Using remote management tools like WinRM or SSH would require open inbound ports (like TCP 59865986 or 2222), whereas extensions execute internally via the local VM Agent.

Key Concept

Azure Virtual Machine deployment configurations, including Ephemeral OS disks, Ultra Disks, Proximity Placement Groups, and VM Extensions.
Estimated Time:2m 30s
Rate this question