AZ-900 Describe Azure architecture and services Practice Question
Which Azure service provides a managed platform for deploying and running microservices as containers without managing the Kubernetes control plane?
⚠ Common exam trap
Test-takers frequently confuse 'managed Kubernetes' (AKS) with 'serverless containers' (Container Apps), assuming that AKS eliminates all control plane management, when in fact AKS still requires you to manage the control plane's lifecycle, whereas Container Apps fully abstracts it away.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Azure Container Apps
Azure Container Apps is a fully managed serverless platform for deploying and running microservices as containers without requiring any management of the underlying Kubernetes control plane. It abstracts away Kubernetes orchestration, providing built-in autoscaling, ingress, and secrets management, making it ideal for event-driven or containerized microservices where operational overhead must be minimized.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Azure Kubernetes Service
Why it's wrong here
Azure Kubernetes Service (AKS) gives you full control over a Kubernetes cluster, exposing the control plane, node pools, networking, and cluster upgrades for you to manage. While AKS can host microservices, it requires significant operational overhead for cluster monitoring, patching, and scaling, which contradicts a serverless abstraction. Azure Container Apps, in contrast, runs on top of Kubernetes but hides all the cluster components, allowing you to focus solely on deploying and scaling containers without ever seeing the underlying infrastructure. Thus AKS is not the correct choice when the goal is to avoid Kubernetes management entirely.
- ✓
Azure Container Apps
Why this is correct
Azure Container Apps is a serverless container service built on Kubernetes that abstracts away the cluster's control plane, nodes, and maintenance. It provides built-in support for event-driven scaling via KEDA, service-to-service communication, and revision-based versioning, enabling you to deploy microservices and long-running processes without ever managing Kubernetes. This makes it the ideal choice when you need a fully managed platform for microservices orchestration with granular scaling and ingress rules, far beyond what simple container instances or web hosting can offer.
- ✗
Azure Container Instances
Why it's wrong here
Azure Container Instances (ACI) lets you run a single container or a small container group in seconds, but it does not provide orchestration features like service discovery, rolling updates, or auto-scaling based on queue length or HTTP rules. ACI is meant for simple isolated workloads, batch jobs, or quick dev/test scenarios, not for building a resilient microservices platform. If the scenario requires managing multiple interacting services with traffic splitting and dynamic scaling, ACI's lack of application-level orchestration makes it the wrong fit.
- ✗
Azure App Service
Why it's wrong here
Azure App Service is a fully managed web hosting platform designed primarily for application code (ASP.NET, Java, Node.js, Python, etc.) rather than for container-based microservices. Although it supports containers through Web App for Containers, it still treats each app as a web application and lacks the native container orchestration, service discovery, and event-driven scaling capabilities that Azure Container Apps provides. Therefore, App Service would be chosen when the focus is on hosting web apps and APIs, not for abstracted Kubernetes-style microservices.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
Learn chapter
Azure Regions and Geographies
Key term
Container
A container is a lightweight, standalone software package that includes everything needed to run an application, such as code, runtime, system tools, and libraries.
Key term
Serverless
Serverless is a cloud computing model where the cloud provider manages the servers, and you only pay for the actual compute time your code uses, without having to worry about provisioning or maintaining infrastructure.
About these practice questions
One of 981 original AZ-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-900 exam.