Microsoft Certified: Azure Administrator AssociateDeploy and manage Azure compute resourcesHard
A company is deploying a new application that consists of a web frontend and a backend API. Both components are containerized. The company wants to deploy these containers together, ensuring they share a network and can communicate via localhost, and that their lifecycle is managed as a single unit. Which Azure Container Instances (ACI) deployment model should be used?
- AMulti-container group
- BInit container
- CSidecar container
- DSingle container instance
Show answer & explanationAnswer & explanation
Correct answer: A. Multi-container group
A multi-container group in ACI allows multiple containers to be deployed together on the same host machine, sharing a network namespace, storage volume, and lifecycle, which is ideal for scenarios like a web frontend and a backend API that need to communicate via localhost.
Why the other options are wrong
- B. An init container is a specialized container that runs to completion before the main application containers start, typically for setup tasks, not for running alongside the main application.
- C. A sidecar container is a pattern where a utility container runs alongside a main application container, often sharing resources, but 'multi-container group' is the general ACI deployment model that supports this pattern.
- D. A single container instance runs only one container and cannot host both the frontend and backend together with shared resources.
ACI Multi-Container Group
An Azure Container Instances deployment model where multiple containers are deployed together on the same host, sharing resources like IP address, port space, and storage volumes. They are managed as a single unit.
- Containers share a network namespace (communicate via localhost)
- Containers share storage volumes
- Managed as a single resource group (container group)
- Ideal for co-located applications like sidecar patterns
Memory trick: Group Containers for Shared Life.