← All AZ-300 Flashcard Decks

Azure App Services & Containers Flashcards

6 cards from real AZ-300 practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 6 Azure App Services & Containers flashcards as text
  1. Which Azure App Service feature allows you to run a new version of your app alongside production and swap them with no downtime?

    Answer: Deployment Slots

    Deployment Slots let you stage a new version, warm it up, then swap it into production instantly with no downtime and the ability to roll back.

  2. Which Azure container service provides a fully managed Kubernetes environment without requiring cluster infrastructure management?

    Answer: Azure Kubernetes Service (AKS)

    Azure Kubernetes Service (AKS) manages the Kubernetes control plane and simplifies deployment, scaling, and operations of containerized applications.

  3. What is the purpose of Azure Container Instances (ACI)?

    Answer: Run containers on-demand without managing infrastructure, billed per second

    ACI provides the fastest and simplest way to run a container in Azure — no VMs, no orchestrator — billed by vCPU and memory per second.

  4. Which App Service plan tier is required to use VNet Integration for outbound traffic from an Azure Web App?

    Answer: Standard or higher

    VNet Integration for outbound connectivity requires at least the Standard App Service Plan tier (or Premium for more VNet features).

  5. What is the function of an Azure Container Registry (ACR)?

    Answer: Store, manage, and geo-replicate Docker container images and OCI artifacts

    Azure Container Registry is a private registry for storing and managing Docker images and Helm charts, with built-in geo-replication and security scanning.

  6. Which Azure App Service feature enables automatic scaling of app instances based on HTTP request queue length or CPU percentage?

    Answer: Autoscale

    Azure App Service Autoscale triggers scale-out or scale-in based on metrics like CPU usage or HTTP queue depth, adjusting instance count automatically.