An online multiplayer gaming platform is designing the compute infrastructure on Azure. The architecture must support two workloads: | Workload | Type | Scaling Requirement | Eviction Tolerance | CPU-to-Memory Ratio | |---|---|---|---|---| | Workload 1 (Session Hosting) | Stateless | Dynamic scaling

For Workload 1, deploy a Virtual Machine Scale Set using Azure Spot VMs with a Dsv5-series VM size.; For Workload 2, deploy Azure Virtual Machines using an Esv5-series VM size.

An online multiplayer gaming platform is designing the compute infrastructure on Azure. Th… — Microsoft Azure Solutions Architect (AZ-305)

An online multiplayer gaming platform is designing the compute infrastructure on Azure. The architecture must support two workloads:

Workload	Type	Scaling Requirement	Eviction Tolerance	CPU-to-Memory Ratio
Workload 1 (Session Hosting)	Stateless	Dynamic scaling	Can tolerate unexpected evictions	At least $1:4$ (e.g., $\ge 4\text{ GB}$ per vCPU)
Workload 2 (Matchmaking Engine)	Stateful	Steady-state	Cannot tolerate unexpected evictions	At least $1:8$ (e.g., $\ge 8\text{ GB}$ per vCPU)

Which two configuration options should you select to meet these requirements?

For Workload 1, deploy a Virtual Machine Scale Set using Azure Spot VMs with a Dsv5-series VM size.Cevap
For Workload 2, deploy Azure Virtual Machines using an Esv5-series VM size.Cevap
C
For Workload 2, deploy Azure Spot VMs using an Esv5-series VM size.
D
For Workload 2, deploy Azure Virtual Machines within a single availability zone using an Availability Set to provide zone-redundant high availability.

Cevap

Deploy a Virtual Machine Scale Set using Azure Spot VMs with a Dsv5-series size for Workload 1, and deploy Azure Virtual Machines using an Esv5-series size for Workload 2.

Deploying the session hosting layer on a Virtual Machine Scale Set using Azure Spot VMs of the Dsv5-series meets the requirements of cost savings, eviction tolerance, and the

1:4

CPU-to-memory ratio. Deploying the matchmaking database on standard Azure Virtual Machines of the Esv5-series satisfies the steady-state SLA requirement (no unexpected evictions) and the

1:8

memory-optimized ratio.

Adım Adım Çözüm

Analyze the requirements for Workload 1 (Session Hosting).

Workload 1 requires dynamic scaling, can tolerate unexpected evictions to minimize cost, and needs a

1:4

vCPU-to-memory ratio.

This points to using Azure Spot VMs within a Virtual Machine Scale Set, utilizing a Dsv5-series VM size which matches the memory-to-vCPU ratio.

Analyze the requirements for Workload 2 (Matchmaking Engine).

Workload 2 requires steady-state execution (no unexpected evictions), and needs a

1:8

vCPU-to-memory ratio.

This rules out Spot VMs (which can be evicted) and points to standard Azure Virtual Machines using a memory-optimized VM series like Esv5.

Evaluate the architectural high availability option.

The option suggesting the use of Availability Sets within a single zone for zone redundancy is incorrect.

Availability Sets only protect against localized hardware failures within a single zone and do not provide cross-zone redundancy.

Anahtar Kavram

Selecting VM sizes based on memory-to-CPU ratios, and choosing between standard VMs and Spot VMs based on workload eviction tolerance and SLA constraints.

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular

Bu konudan daha fazla soru