AZ-900 Describe Azure architecture and services Practice Question

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 Container Instances

  Why it's wrong here

  Azure Container Instances (ACI) is a PaaS offering that runs a single container or a simple container group directly on Azure infrastructure. It provides no orchestration layer, cluster management, or Kubernetes control plane, so you cannot define deployments, services, or autoscaling policies across nodes. ACI is ideal for short-lived, isolated workloads or with Service Fabric, but it is not a managed Kubernetes environment, which requires cluster-level lifecycle management and API access.

• ✓

  Azure Kubernetes Service

  Why this is correct

  Azure Kubernetes Service (AKS) is the only option that is literally a managed Kubernetes environment. Azure provisions and operates the Kubernetes control plane (API server, etcd, scheduler) for free, while the user manages and pays for worker nodes, networking, and workloads. AKS provides direct access to the Kubernetes API, supports native `kubectl` commands, and integrates with Azure AD, Azure Policy, and Azure Monitor, making it a true managed Kubernetes service that significantly reduces cluster management complexity compared to self-managed Kubernetes.

• ✗

  Azure Container Apps

  Why it's wrong here

  Azure Container Apps is a serverless containers platform that abstracts Kubernetes to the point where you never interact with pods, nodes, or the Kubernetes API, even though it runs on AKS underneath. It gives you event-driven autoscaling, service-to-service discovery, and revision-based deployments, but all Kubernetes resources are hidden behind a simplified REST API. Because the user cannot manage or inherently see the Kubernetes environment, it fails to qualify as a managed Kubernetes service, which by definition exposes the Kubernetes control plane and cluster resources to the user.

• ✗

  Azure App Service

  Why it's wrong here

  Azure App Service is a fully managed PaaS platform designed for hosting web applications, REST APIs, and mobile backends, not for container orchestration. It can run containers by using Web App for Containers, but that feature abstracts away the hosting environment entirely and does not expose Kubernetes primitives like pods, services, or deployments. There is no Kubernetes API or control plane, and it uses its own architecture for scaling and load balancing, so it is fundamentally different from a managed Kubernetes environment and cannot be used to manage Kubernetes clusters.