How do you choose between Azure compute options: VMs, App Service, AKS, Functions, and Container Apps?
What they are really testing: Whether you match workload to service on the control-versus-management spectrum, rather than defaulting to VMs or AKS for everything. Shows breadth of the Azure platform.
A real interview question
How do you choose between Azure compute options: VMs, App Service, AKS, Functions, and Container Apps?
What most people say
drag me
“I would use VMs since they can run anything, or AKS if it needs containers.”
Defaulting to VMs or AKS ignores the managed options that are usually the better fit. App Service, Functions, and Container Apps remove huge operational burden; reaching for VMs/AKS by reflex means more ops than the workload needs.
The follow-ups they ask next
When would you pick Container Apps over AKS?
When you want to run containers/microservices with autoscaling (including scale-to-zero) but do not need full Kubernetes control and do not want to operate a cluster. AKS is for when you genuinely need Kubernetes primitives and portability.
Why not just default everything to VMs?
VMs put all the operational burden (patching, scaling, availability) on you. Managed PaaS/serverless options remove that for most workloads, so VMs should be a deliberate choice for special needs, not the default.
What the interviewer is listening for
- Maps workload to service on control vs management
- Knows App Service/Functions/Container Apps, not just VMs/AKS
- Defaults toward managed options
What sinks the answer
- Defaults to VMs or AKS for everything
- Unaware of Container Apps/Functions distinctions
- No control-vs-ops reasoning
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“Pick on the control-vs-management spectrum: [VMs (IaaS, full control, you own patching/scaling, for legacy/special needs)], [App Service (PaaS web apps/APIs, managed scaling/TLS/slots, the standard web default)], [AKS (managed Kubernetes for complex microservices/portability, with cluster ops)], [Functions (event-driven, scale-to-zero code)], [Container Apps (serverless containers/microservices, KEDA, no Kubernetes to run)]. Default toward managed.”
Keep going with azure
Foundation
What is Microsoft Entra ID (formerly Azure AD), and how does authentication work in Azure?
Foundation
In Azure, what handles authentication versus authorization?
Foundation
Explain the Azure resource hierarchy: tenant, management group, subscription, resource group.
Junior
How does Azure RBAC work? Explain roles, scopes, and assignments.
Junior
What happens when a user signs in to an Azure/Entra-protected application?
Junior
What is the difference between a service principal and a managed identity, and why prefer managed identities?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free