Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Azure Kubernetes Service for Microservice Orchestration
Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
A company is migrating a complex microservices-based application to Azure. The application consists of dozens of lightweight, interconnected containerized components across multiple nodes.
The development team requires a managed platform that automatically handles container scheduling, dynamic load balancing, health monitoring with automatic recovery of unhealthy container instances, and zero-downtime rolling updates.
Which Azure service should the company use to orchestrate these containers?
Explanations
Azure Container Registry (ACR)
Azure Container Registry (ACR)
What Azure Container Registry (ACR) is
Azure Container Registry (ACR) is a managed, private Docker registry service based on the open-source Docker Registry 2.0. It is used to store, build, and manage private container images and related artifacts.
Why it doesn't meet the requirement
While ACR is an essential companion service in containerized workflows, it is strictly a storage and artifact repository. It does not execute container workloads, orchestrate multi-container microservice deployments, perform automatic pod scaling, or handle load balancing between active nodes.
Key characteristics and limitations
- Image storage and cataloging: Acts as a centralized catalog for private container images across development lifecycles.
- No compute runtime: Does not provide compute instances or host running container applications.
- Automated builds: Supports task automation for building images upon source code commits, but cannot schedule or run the resulting containers in production.
- Access control: Provides role-based access control and image vulnerability scanning.
This answer would be correct if
The scenario required a secure, centralized cloud repository to store, version, and scan private container images before deploying them to compute environments.
Additional context
In typical enterprise architectures, container images are built and pushed to Azure Container Registry, and an orchestrator like Azure Kubernetes Service (AKS) pulls those images to run and scale the actual application instances.
Azure Virtual Machines (VMs)
Azure Virtual Machines (VMs)
What Azure Virtual Machines are
Azure Virtual Machines (VMs) represent an Infrastructure as a Service (IaaS) compute offering that provides fully customizable, virtualized hardware environments running individual guest operating systems.
Why it doesn't meet the requirement
Deploying bare virtual machines shifts the entire burden of container orchestration and cluster management onto the development and operations teams. Virtual machines alone do not provide native container orchestration features such as automatic desired-state configuration, container-level self-healing, or dynamic microservice load balancing.
Key characteristics and limitations
- Heavyweight overhead: Each virtual machine requires its own dedicated operating system kernel, virtual memory, and storage, consuming significantly more compute resources than lightweight containers.
- Manual management overhead: The customer is responsible for installing, configuring, patching, and maintaining the OS, container runtime, and networking add-ons.
- Slower startup times: Virtual machines take minutes to boot and initialize compared to the near-instantaneous startup times of containers.
- Limited native orchestration: Requires manual setup of third-party cluster tools on unmanaged compute instances to coordinate multiple microservices.
This answer would be correct if
The application required direct, low-level access to the operating system kernel, custom OS configurations, or legacy software that cannot run within standardized container environments.
Additional context
While virtual machines often act as the underlying infrastructure nodes that host Kubernetes clusters, using standalone VMs requires manual configuration rather than utilizing a fully managed container orchestrator.
Azure Functions
Azure Functions
What Azure Functions is
Azure Functions is a serverless Function-as-a-Service (FaaS) compute solution that enables developers to run individual pieces of code or small tasks in response to events or triggers without managing infrastructure.
Why it doesn't meet the requirement
Azure Functions is designed for short-lived, event-driven compute tasks rather than orchestrating complex, multi-tiered microservice container clusters. It does not provide the comprehensive container orchestration controls—such as multi-node cluster configuration, custom container-level network topology, or sidecar routing—required for an interconnected microservices architecture.
Key characteristics and limitations
- Event-driven execution: Runs modular code automatically in response to HTTP requests, database modifications, queue messages, or timers.
- Ephemeral lifecycle: Optimized for short-duration tasks that spin up, execute, and terminate quickly.
- Abstracted runtime: Focuses on individual code blocks rather than full containerized application coordination and node cluster administration.
- Limited orchestration depth: Lacks native Kubernetes-style cluster scheduling, service mesh management, and pod health reconciliation.
This answer would be correct if
The scenario required running lightweight, decoupled, on-demand code execution triggered by events (such as processing queue messages or database triggers) with zero server maintenance.
Additional context
While Azure Functions can be packaged inside container images for deployment portability, it remains an event-driven serverless compute tool rather than a comprehensive container orchestration platform.
Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
What Azure Kubernetes Service (AKS) is
Azure Kubernetes Service (AKS) is a fully managed Kubernetes container orchestration platform in Azure designed to simplify deploying, scaling, and managing containerized applications.
How it meets the requirements
AKS provides complete container orchestration capabilities that directly solve the operational challenges described in the scenario:
- Automated scaling: Dynamically adjusts microservice container instances based on CPU, memory utilization, or incoming traffic demands.
- Self-healing and health management: Continuously monitors container health to maintain the configured desired state. If a container instance fails or becomes unhealthy, the orchestrator automatically provisions a replacement instance.
- Load balancing and service abstraction: Automatically routes network traffic across multiple container instances and nodes while masking complex IP and port configurations.
- Zero-downtime upgrades: Coordinates rolling application updates and rollbacks across the cluster without interrupting user access.
Key advantages and capabilities
- Elastic provisioning: Easily scales worker nodes and container pods to adapt to changing workload sizes.
- High resource efficiency: Runs multiple isolated containers across shared compute nodes without the overhead of running multiple guest operating systems.
- Portability: Enables consistent application execution across local development machines, testing environments, and production cloud infrastructure.
- Enterprise integration: Integrates seamlessly with Azure networking, identity management via Microsoft Entra ID, and container image registries.
Why this is optimal
Managing dozens of interconnected containers individually becomes impractical at scale. AKS abstracts the underlying infrastructure complexity and automates critical lifecycle management tasks, making it the premier choice for production-grade microservices.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 688 practice questions across all 3 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Functions Serverless Event-Driven Compute
Compare compute types, including containers, virtual machines, and functions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Functions
Compare compute types, including containers, virtual machines, and functions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Virtual Machines IaaS Full Control
Compare compute types, including containers, virtual machines, and functions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Functions vs Virtual Machines vs Containers
Compare compute types, including containers, virtual machines, and functions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Serverless Computing
Describe serverless
IntermediateAZ-400 Designing and Implementing Microsoft DevOps Solutions Exam
GitHub Branch Protection Rules and SAML SSO
Design and implement permissions and roles in GitHub
Last updated Validated