AZ-305 Question 144
Single answerYou are designing a microservices-based application that must run multiple containers with both stateful and stateless services. The application requires dynamic scaling based on workload demand and needs a simple way to orchestrate and manage containers. You also want to seamlessly integrate with Azure DevOps pipelines for continuous integration and deployment. Which approach should you recommend?
- A
Deploy each container as a separate Azure Web App for Containers within Azure App Service
- B
Use Azure Kubernetes Service (AKS) with Azure Container Registry to orchestrate the microservices
- C
Use Azure Container Instances for all microservices, with manual script-based scaling
- D
Run the microservices as serverless Azure Functions on a Premium plan
Show answer and explanation
Correct answer: B
Explanation
Azure Kubernetes Service (AKS) is recommended for container-based microservices requiring comprehensive orchestration, automatic scaling, and rolling updates. It integrates seamlessly with Azure DevOps (for CI/CD), Azure Container Registry (for storing and managing container images), and provides native tools for load balancing, monitoring, and secure communication among services. Refer to Microsoft’s AKS documentation (https://docs.microsoft.com/azure/aks) for detailed best practices on deploying and managing container workloads.
- A. Incorrect.
Option 1: Deploying each container as an Azure Web App for Containers can work for simpler scenarios wearing single or limited container form factors. However, complex orchestration, advanced load-balancing, and auto-scaling would require additional custom configurations. It’s not ideal for managing multiple microservices that need sophisticated orchestration across containers.
- B. Correct.
Option 2: Azure Kubernetes Service (AKS) fully manages container orchestration, networking, and autoscaling while integrating directly with Azure Container Registry and Azure DevOps. This makes it an ideal choice for microservices that need automated scaling, rolling updates, and centralized management of container workloads. (Correct)
- C. Incorrect.
Option 3: Azure Container Instances (ACI) is best suited for running ephemeral container tasks or when you need rapid, on-demand container deployments. ACI does not provide robust orchestration or autoscaling across multiple containers, making it less suitable for large-scale microservices solutions.
- D. Incorrect.
Option 4: While Azure Functions (Premium plan) can run containers, it is primarily designed for serverless compute workloads triggered by events. This approach may not meet all the orchestration, scaling, and stateful service requirements for multi-container microservices solutions.