โ† 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. What is the purpose of Kubernetes Horizontal Pod Autoscaler (HPA) in AKS?

    Answer: Automatically scale the number of pod replicas based on CPU/memory or custom metrics

    HPA monitors pod metrics and automatically adjusts the replica count to meet desired resource utilization, scaling pods out under load and in when idle.

  2. Which Azure Container Registry feature replicates images to multiple Azure regions for low-latency pulls by geographically distributed clusters?

    Answer: Geo-Replication

    ACR Geo-Replication creates registry replicas in chosen regions, allowing clusters to pull images from the nearest replica for faster pulls and resilience.

  3. Which App Service plan is required to use Private Endpoints for inbound traffic isolation to an Azure Web App?

    Answer: Premium v2 or higher

    Private Endpoints for inbound connectivity to App Service require the Premium v2/v3 plan or higher to attach a private endpoint to the web app.

  4. What is an Azure App Service Environment (ASE)?

    Answer: A fully isolated, dedicated App Service deployment within your VNet for compliance and high-scale workloads

    An ASE is a single-tenant deployment of Azure App Service injected directly into a customer's VNet, providing complete network isolation and dedicated compute.

  5. Which KEDA (Kubernetes Event-Driven Autoscaling) scaler is used in Azure Container Apps to scale based on Azure Storage Queue depth?

    Answer: Azure Storage Queue scaler

    KEDA's Azure Storage Queue scaler triggers pod/container scaling based on the number of messages in an Azure Storage Queue.

  6. What is the purpose of AKS 'namespaces' in a multi-team Kubernetes environment?

    Answer: Provide logical isolation between teams or workloads within a single cluster

    Kubernetes namespaces divide a cluster into virtual sub-clusters, enabling resource isolation, RBAC scoping, and quota management per team or workload.