A logistics company is designing an Azure compute virtualization solution for its fleet management platform. The platform has two main requirements:
1. A core telemetry ingestion engine that runs continuously, requires consistent performance, must achieve a availability SLA, and requires memory-optimized virtual machines.
2. A daily route-optimization analysis job that runs for approximately hours, is tolerant to interruptions, and should be implemented with the lowest possible cost.
Which two compute configurations should you include in the design?
- Azure Reserved Virtual Machines using Esv5-series VMs distributed across multiple Availability Zones for the telemetry ingestion engineAnswer
- Azure Spot Virtual Machines using Fsv2-series VMs for the route-optimization analysis jobAnswer
- CAzure Spot Virtual Machines using Esv5-series VMs for the core telemetry ingestion engine
- DPay-as-you-go Esv5-series VMs deployed within a single Availability Zone for the telemetry ingestion engine
- EAn Azure Functions Consumption plan to execute the route-optimization analysis job
Answer
The correct configurations are to use Azure Reserved Virtual Machines using Esv5-series VMs distributed across multiple Availability Zones for the telemetry ingestion engine, and Azure Spot Virtual Machines using Fsv2-series VMs for the route-optimization analysis job.
The correct configurations combine Azure Reserved Virtual Machines using Esv5-series VMs distributed across multiple Availability Zones for the telemetry ingestion engine with Azure Spot Virtual Machines using Fsv2-series VMs for the route-optimization analysis job. The telemetry engine is a continuous, steady-state workload requiring a memory-optimized series and a high SLA (), which is achieved by deploying across multiple Availability Zones. Reserved instances reduce cost for this continuous running resource. The route-optimization job runs for a short duration and can tolerate interruptions, making Spot VMs the most cost-effective option.
Step-by-Step Solution
Key Concept
Selecting Azure VM series, purchasing models, and redundancy strategies based on SLA, duration, performance, and cost constraints.