Chapter 4 · Design Infrastructure Solutions·v2.0.0·Updated 6/3/2026·~11 min

What's changed: Deepened AZ-305 Chapter 4 (added comparison tables, scenarios, FAQs, exam traps, deep-dive paragraphs to each section; localized figures to Japanese)

4.1Designing Compute

Key points

Understand compute choices—VMs/VMSS, App Service, Azure Functions, and AKS/ACI/Container Apps. Pick the runtime that fits the workload.

Compute selection is central to infrastructure design. From VMs to serverless, choose by control needs and how managed you want it.

4.1.1Compute options

Diagram of Azure compute choices along a control-vs-managed trade-off: Virtual Machines (IaaS; scale with VMSS) for full control, App Service (PaaS; autoscale/slots) to host web/API easily, Azure Functions (serverless) for event-driven pay-per-use, and for containers: AKS when Kubernetes is needed, ACI for one-off/batch containers, and Container Apps to run serverless microservices. — Compute choices

VM/VMSS: full control down to the OS (IaaS); VMSS autoscales identical VMs.
App Service: PaaS to host web/API easily (autoscale/deployment slots).
Azure Functions: event-driven, pay-per-use serverless.
AKS/ACI/Container Apps: AKS = Kubernetes, ACI = one-off/batch, Container Apps = serverless microservices.

Exam point

Common on AZ-305: full OS control = VM, scale identical VMs = VMSS, easy PaaS for web/API = App Service, event-driven pay-per-use = Functions, Kubernetes = AKS, one-off containers = ACI, serverless containers = Container Apps. Prefer managed (PaaS/serverless) to reduce operational overhead.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.

Get started free Log in