An energy exploration company is designing the Azure compute virtualization infrastructure for a seismic modeling platform. The platform consists of two primary workloads:
* Database Engine: A stateful, steady-state data store containing sensitive telemetry data. It must run on physical hardware isolated at the host level to meet compliance requirements. It requires a high memory-to-vCPU ratio and must maintain an uptime SLA of 99.99%.
* Simulation Pipeline: A massive batch-oriented parallel simulation runner. The pipeline is stateless, highly fault-tolerant, can resume from checkpoints, and must run at the lowest possible cost.
Which two compute virtualization configurations should you recommend to meet these requirements? (Select two.)
- Deploy the Database Engine on Azure Dedicated Hosts using Esv5-series virtual machines allocated across multiple Availability Zones.Answer
- Deploy the Simulation Pipeline on Azure Spot Virtual Machines using Dsv5-series instances.Answer
- CDeploy the Database Engine on Azure Spot Virtual Machines using Esv5-series instances with an eviction policy set to Deallocate.
- DDeploy the Database Engine on Azure Dedicated Hosts using Fsv2-series virtual machines allocated within a single fault domain.
Answer
Deploy the Database Engine on Azure Dedicated Hosts using Esv5-series virtual machines allocated across multiple Availability Zones, and deploy the Simulation Pipeline on Azure Spot Virtual Machines using Dsv5-series instances.
Deploying the Database Engine on Azure Dedicated Hosts with Esv5-series VMs across multiple Availability Zones guarantees host-level isolation, provides the required memory-to-vCPU ratio, and satisfies the 99.99% availability SLA. Deploying the Simulation Pipeline on Azure Spot VMs using Dsv5-series instances satisfies the requirement for the lowest cost compute, since the workload is stateless and capable of handling capacity eviction.
Step-by-Step Solution
Key Concept
Selecting and configuring Azure compute virtualization components (Dedicated Hosts, Spot VMs, and VM series) to meet physical isolation, high availability SLA, hardware-profile, and cost constraints.