Containers
CoreAzure Container Instances
Direct container-group execution without orchestrator management.
Key points
- Runs one or more containers as a container group without managing an orchestrator.
- Configures CPU, memory, environment, restart policy, networking, and volumes at deployment.
- Fits simple isolated or short-lived execution better than revision-oriented application operations.
Best-known use cases
- Run an on-demand batch container.
- Launch a simple isolated service with fixed resources.
What candidates often confuse it with
- ACI vs Container Apps: direct container-group execution vs managed app revisions, ingress, replicas, and autoscaling.
- ACI vs ACR: runtime vs image repository.
Key takeaway
Use ACI for straightforward container-group execution that does not require an application revision and autoscale model.
Related services
- Azure Container Registry
- Azure Container Apps
Relevant exam tasks
- D3.3.S1 — Create and manage an Azure Container Registry
- D3.3.S2 — Provision a container by using Azure Container Instances
- D3.3.S3 — Provision a container by using Azure Container Apps
- D3.3.S4 — Manage sizing and scaling for containers, including Azure Container Instances and Azure Container Apps