Bitzu

AZ-305 ยท Compute solution design

Choosing an Azure compute service

Decision flow across Virtual Machines, App Service, Azure Kubernetes Service, Azure Container Apps, Azure Container Instances, Azure Functions and Azure Batch by control, scale and management effort.

Key points

  • VMs (IaaS): full OS control, lift-and-shift, most overhead; App Service: web and API, deployment slots.
  • Functions: event-driven, serverless plans; Batch: large parallel and HPC jobs.
  • AKS: managed Kubernetes with Kubernetes API access; Container Apps: serverless containers, no Kubernetes API.
  • Container Instances: one container group, no orchestration or autoscaling.
  • Mix services per component; all regional (multi-region needs a router).

Source: https://learn.microsoft.com/en-us/azure/architecture/guide/technology-choices/compute-decision-tree

Practice questions

Single choice

Which compute service gives a team direct access to the Kubernetes API and control plane?

  1. Azure Container Apps
  2. Azure Kubernetes Service
  3. Azure Container Instances
  4. Azure App Service
Show answer

Answer: B. Azure Kubernetes Service

Azure Kubernetes Service (AKS) is managed Kubernetes and exposes the Kubernetes API. Azure Container Apps is built on Kubernetes but deliberately hides the Kubernetes API, so it is the tempting wrong answer.

Select all that apply

Which options can run with no instances while idle, so you pay no compute while nothing runs?

  1. Azure Functions on the Flex Consumption plan
  2. Azure Container Apps with minimum replicas set to 0
  3. A Standard tier App Service plan with one instance
  4. An AKS cluster's system node pool
  5. A single Azure virtual machine left running
Show answer

Answer: A. Azure Functions on the Flex Consumption plan, B. Azure Container Apps with minimum replicas set to 0

The Flex Consumption plan of Azure Functions and Azure Container Apps (minimum replicas 0) are serverless and scale to zero. A single VM, a Standard App Service plan and an AKS system node pool all keep at least one billed instance running.

True or false

Azure Container Instances provides built-in autoscaling and full container orchestration.

Show answer

Answer: False

False. Container Instances runs a single container or container group without orchestration and has no built-in autoscaling. For orchestration and scale rules, look at Container Apps or AKS.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More AZ-305 topics in this module