Azure offers several ways to run containers without managing virtual machines. Two are in scope for this exam: Azure Container Instances (ACI), for running containers quickly and simply, and Azure Container Apps, for running microservices and web apps with automatic scaling, revisions and managed ingress. Neither requires you to operate a Kubernetes cluster yourself. The skill tested is picking the right service and configuring its key settings: container groups and restart policies for ACI, and revisions, ingress and scale rules for Container Apps. ACI starts a container in seconds and bills per second for the vCPU and memory it uses. The unit of deployment is a container group: one or more containers scheduled on the same host that share a lifecycle, a local network (they reach each other on localhost), an optional public IP address with a DNS name label, and mounted volumes such as an Azure file share. It is similar to a Kubernetes pod. Multi-container groups are supported for Linux containers and are usually deployed from a YAML file or an Azure Resource Manager (ARM) template, for example an app container plus a logging sidecar. A container group can also be deployed into a virtual network subnet for private access. A quick single container looks like this:
Keep reading for free
Create a free StudyToCert account to read the rest of this lesson: 7 more sections, 7 key terms, a real-world example, an exam tip and self-check questions. Every lesson, lab and practice test is free with an account.