A gaming company is deploying a new online multiplayer game on Azure. The system architecture requires two distinct compute tiers:
1. Matchmaking Service: A production-grade backend service that manages active player sessions and matchmaking. It runs , requires a availability SLA, and must not experience unexpected virtual machine (VM) termination.
2. Telemetry Log Processor: A background worker service that aggregates and processes player telemetry metrics. The processing can be interrupted and resumed later without data loss.
To maximize availability for the Matchmaking Service and minimize costs for the Telemetry Log Processor, which compute configuration should you recommend?
- Deploy the Matchmaking Service instances across multiple Availability Zones using standard Virtual Machines (VMs), and host the Telemetry Log Processor on Azure Spot VMs.Cevap
- BDeploy the Matchmaking Service instances within a single Availability Zone using Azure Spot VMs, and host the Telemetry Log Processor on standard VMs.
- CDeploy the Matchmaking Service instances across multiple Availability Zones using Azure Spot VMs, and host the Telemetry Log Processor on standard VMs.
- DDeploy the Matchmaking Service instances within a single Availability Zone using standard VMs, and host the Telemetry Log Processor on Azure Spot VMs.
Cevap
Deploy the Matchmaking Service instances across multiple Availability Zones using standard Virtual Machines (VMs), and host the Telemetry Log Processor on Azure Spot VMs.
The correct option ensures the production matchmaking service has a high availability SLA by spreading standard VMs across multiple Availability Zones, and optimizes cost by using low-cost Spot VMs for the interruptible telemetry service.
Adım Adım Çözüm
Anahtar Kavram
Selecting Azure VM tiers (Standard vs Spot) and Availability Zone configurations based on SLA and workload characteristics.