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) can quickly run a single container or a small group of containers, but it lacks the orchestration features required for microservices. ACI does not provide built-in auto-scaling based on container metrics, service discovery across multiple instances, or rolling deployment strategies. While ACI is excellent for on-demand or event-driven scenarios, it is not a substitute for a managed Kubernetes service when you need a resilient, scalable microservices platform.

  When this WOULD be correct

  A team needs to run a single container or a simple containerized application without complex orchestration, and they want to avoid managing any underlying infrastructure. They do not require scaling or load balancing across multiple containers.

• ✓

  Azure Kubernetes Service

  Why this is correct

  Azure Kubernetes Service (AKS) is the correct choice because it is a managed Kubernetes platform that provides full container orchestration for microservices. It handles deployment, scaling, service discovery, and load balancing across containers automatically, and the control plane is managed by Azure, reducing operational overhead. This makes AKS purpose-built for running a microservices architecture that requires continuous scaling and resilience.

• ✗

  Azure Batch

  Why it's wrong here

  Azure Batch is designed for large-scale parallel and high-performance computing (HPC) jobs that run to completion, such as rendering or data processing workloads. It does not run long-lived, always-on microservices, nor does it provide native service discovery or rolling updates for containerized applications. Batch is a job scheduler, not a container orchestrator, so it is fundamentally misaligned with the needs of a microservices team.

  When this WOULD be correct

  A question asking for a service to run large-scale parallel batch processing jobs (e.g., rendering, financial risk modeling) where you need to schedule and manage a pool of compute nodes, and you are not focused on container orchestration or microservices.

• ✗

  Azure Virtual Machine Scale Sets

  Why it's wrong here

  Azure Virtual Machine Scale Sets (VMSS) provide automatic scaling of virtual machines, but they operate at the infrastructure level, not the container level. To use containers on VMSS, you must manually configure and manage the container runtime, and there is no built-in orchestration for service discovery, rolling updates, or inter-container networking. VMSS would require you to deploy and manage a separate orchestrator like Kubernetes yourself, which is extra overhead compared to using AKS.

  When this WOULD be correct

  A question asking for a service to automatically scale a group of identical VMs based on CPU or memory metrics, with the ability to run custom software (including containers) but where you are responsible for managing the VM OS and container runtime, would make Azure Virtual Machine Scale Sets the correct answer.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-900 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official AZ-900blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Go deeper

Related to this question