Study guide — AI-200

Implement container application hosting

• Build, store, version, and manage container images by using Azure Container Registry
  Ver resumen

  Azure Container Registry stores images by repository, tag and manifest; pulling by digest pins the version. Use unique tags for deployments and lock deployed images with az acr repository update. Re-pushing a tag leaves orphaned manifests: remove them by digest, with acr purge or with a retention policy. az acr import copies images between registries without Docker.

  About registries, repositories, images, and artifacts ↗Image tag best practices ↗

• Build and run images by using Azure Container Registry Tasks
  Ver resumen

  ACR Tasks builds images in the cloud: az acr build runs a quick task without local Docker and pushes the image unless you pass --no-push. az acr task create supports commit, base image (stable tag) and UTC cron timer triggers. Multi-step tasks are defined in YAML with build, push and cmd steps, and reach other resources through managed identities.

  Automate container builds with Azure Container Registry tasks ↗YAML reference for Azure Container Registry (ACR) Tasks ↗

• Deploy containers to Azure App Service, including configuring App Service to supply environment variables and secrets
  Ver resumen

  App Service runs custom containers that pull their image from Azure Container Registry, ideally with a managed identity (AcrPull plus acrUseManagedIdentityCreds). App settings reach the container as environment variables (WEBSITES_PORT when it doesn't listen on 80; __ instead of colons on Linux), and secrets resolve through @Microsoft.KeyVault references using the app's identity.

  Configure a custom container - Azure App Service ↗Use Key Vault references as app settings - Azure App Service ↗

Implement container-orchestrated solutions

• Deploy applications to Azure Container Apps, including environment configuration and revision management
  Ver resumen

  In Azure Container Apps every change under properties.template (image, suffix, scale rules) creates an immutable revision, while secrets, ingress and traffic splitting are application-scope changes. Single mode switches traffic with zero downtime once the new revision is ready; multiple mode adds traffic weights, labels with their own URL and blue-green releases. The environment is the secure boundary for networking and logs.

  Update and deploy changes in Azure Container Apps ↗Traffic splitting in Azure Container Apps ↗

• Implement event-driven scaling by using Kubernetes Event‑driven Autoscaling (KEDA) in Container Apps
  Ver resumen

  Azure Container Apps scales with KEDA: HTTP and TCP rules use concurrent requests or connections, and custom rules copy the type and metadata of a KEDA scaler. Authentication uses secrets (triggerParameter and secretRef) or a managed identity through the identity property. Without ingress or a custom rule the app scales to zero and never restarts; event-driven jobs start one execution per event.

  Scaling in Azure Container Apps ↗Scaling Deployments, StatefulSets & Custom Resources | KEDA ↗

• Deploy and manage applications to Azure Kubernetes Service (AKS) by using manifest files
  Ver resumen

  On AKS, az aks get-credentials configures kubectl and kubectl apply -f creates the objects in a manifest. A Deployment creates a revision only when .spec.template changes; maxSurge and maxUnavailable shape rolling updates, Recreate avoids running two versions at once and kubectl rollout undo rolls back. Services pick pods by selector, a Deployment selector is immutable, and readiness, startup and liveness probes do different jobs.

  Deploy an Azure Kubernetes Service (AKS) Cluster using Azure CLI ↗Deployments | Kubernetes ↗

• Monitor and troubleshoot solutions on AKS and Container Apps by inspecting logs, events, and end-to-end connectivity
  Ver resumen

  In Azure Container Apps, log streaming (az containerapp logs show with --type console or system) shows stdout/stderr and service messages live, while Log Analytics stores ContainerAppConsoleLogs_CL, ContainerAppSystemLogs_CL and, when enabled, ContainerAppHTTPLogs. In AKS you diagnose with kubectl describe, get events, logs --previous, debug and EndpointSlices.

  Troubleshooting in Azure Container Apps ↗Use Kubernetes events for troubleshooting - Azure Kubernetes Service ↗