AZ-204 Develop Azure compute solutions Practice Question
Your company is migrating a monolithic application to Azure. The application consists of several components that need to be deployed and scaled independently. You need to design a container orchestration solution. Which TWO services should you consider?
⚠ Common exam trap
Candidates often confuse Azure Container Instances (ACI) with a full orchestration solution, but ACI lacks the multi-container scaling and service discovery features required for independent component deployment, while Azure Kubernetes Service (AKS) is the correct choice for full control over Kubernetes, and Container Apps offers a managed abstraction layer.
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 (B) is correct because it provides a serverless container orchestration platform that allows you to deploy and scale microservices independently without managing the underlying Kubernetes infrastructure. It supports event-driven scaling, revision management, and split traffic routing, making it ideal for migrating monolithic applications to a microservices architecture with minimal operational overhead.
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) provides a fast and simple way to run a single container in Azure without managing virtual machines or higher-level orchestration. However, it lacks built-in features for service discovery, load balancing, and scaling across multiple containers, which are essential for orchestrating a complex, multi-service application migration. It is best suited for isolated, short-lived tasks or burstable workloads rather than a complete application platform.
- ✓
Azure Container Apps
Why this is correct
Azure Container Apps is an excellent choice for migrating monolithic applications to a microservices architecture, offering a serverless platform for running containerized applications. It provides built-in capabilities for HTTP/HTTPS ingress, event-driven scaling, and Dapr integration, simplifying the deployment and management of microservices without the operational overhead of a full Kubernetes cluster. Its focus on independent scaling and revision management makes it ideal for modern application patterns.
- ✗
Azure Batch
Why it's wrong here
Azure Batch is designed specifically for running large-scale parallel and high-performance computing (HPC) workloads, such as financial modeling, image rendering, or data analysis. It manages a pool of compute nodes and schedules jobs to run on them, but it is not intended for hosting long-running, continuously available web applications or microservices that require persistent orchestration, load balancing, and service discovery. Its purpose is distinct from general application hosting.
- ✗
Azure Service Fabric
Why it's wrong here
Azure Service Fabric is a distributed systems platform for packaging, deploying, and managing scalable and reliable microservices and containers. While it offers robust orchestration capabilities, it is generally more complex to manage and has a steeper learning curve compared to modern Kubernetes-based solutions for new containerized applications. Its strength lies in building highly available, stateful services, but it is less commonly chosen for typical stateless container migrations today.
- ✓
Azure Kubernetes Service (AKS)
Why this is correct
Azure Kubernetes Service (AKS) is a fully managed Kubernetes offering that provides the industry-standard platform for deploying, managing, and scaling containerized applications. It offers unparalleled flexibility and control over your container orchestration environment, making it suitable for complex microservice architectures with specific networking, storage, or advanced deployment requirements. AKS is a robust choice for enterprises needing full Kubernetes capabilities without managing the control plane.
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
About these practice questions
Courseiva writes every AZ-204 question from scratch — 881 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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-204 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-204 exam.