A meteorological modeling company is designing the Azure compute virtualization infrastructure for two distinct workloads:
* Workload 1: A weather simulation model that runs daily. The model requires Message Passing Interface (MPI) support with sub-millisecond node-to-node latency, high CPU performance, and cannot tolerate interruptions during its four-hour execution window.
* Workload 2: A public-facing web API providing real-time weather alerts that requires a minimum availability SLA of 99.99% and must scale automatically to handle sudden traffic spikes.
Which two virtual machine configurations should you recommend to meet the requirements? (Select two.)
- Deploy Workload 1 on HBv3-series virtual machines within a proximity placement group.Answer
- Deploy Workload 2 using Virtual Machine Scale Sets in Flexible orchestration mode spread across multiple Availability Zones.Answer
- CDeploy Workload 1 on Dv5-series Spot virtual machines inside a proximity placement group.
- DDeploy Workload 2 using a Virtual Machine Scale Set in Uniform orchestration mode restricted to a single Availability Zone.
Answer
Deploy Workload 1 on HBv3-series virtual machines within a proximity placement group, and deploy Workload 2 using Virtual Machine Scale Sets in Flexible orchestration mode spread across multiple Availability Zones.
The correct configurations are deploying the weather simulation on HBv3-series virtual machines in a proximity placement group, and deploying the API on Virtual Machine Scale Sets in Flexible orchestration mode across multiple Availability Zones. HBv3-series provides the InfiniBand networking and high compute capacity needed for MPI simulation workloads, and the proximity placement group ensures lowest possible latency by placing VMs physically close. Virtual Machine Scale Sets in Flexible orchestration mode distributed across multiple Availability Zones provide the autoscaling functionality and meet the 99.99% VM SLA requirement.
Step-by-Step Solution
Key Concept
Designing compute virtualization solutions in Azure requires matching VM series capabilities (such as HPC-optimized HBv3-series with InfiniBand for MPI workloads) and architectural patterns (such as multi-zone Virtual Machine Scale Sets in Flexible orchestration mode for high-availability SLAs) to workload constraints.