Bird
Raised Fist0
Azurecloud~5 mins

AKS with Azure Load Balancer - Cheat Sheet & Quick Revision

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Recall & Review
beginner
What is AKS in Azure?
AKS stands for Azure Kubernetes Service. It is a managed container orchestration service that simplifies deploying, managing, and scaling containerized applications using Kubernetes.
Click to reveal answer
beginner
What role does Azure Load Balancer play in AKS?
Azure Load Balancer distributes incoming network traffic across multiple pods or nodes in AKS to ensure high availability and reliability of applications.
Click to reveal answer
intermediate
Explain the difference between Basic and Standard Azure Load Balancer in AKS.
Basic Load Balancer supports only a single availability set or virtual machine scale set and has limited features. Standard Load Balancer supports multiple availability zones, better performance, and more features like diagnostics and security.
Click to reveal answer
intermediate
How does AKS use LoadBalancer type services?
In AKS, when a service is defined with type LoadBalancer, Azure automatically provisions an Azure Load Balancer and assigns a public IP to route external traffic to the service pods.
Click to reveal answer
intermediate
What is the request flow when using AKS with Azure Load Balancer?
Client sends request to Azure Load Balancer's public IP → Load Balancer forwards request to healthy AKS nodes → Nodes route request to appropriate pods → Pods respond back through nodes and Load Balancer to client.
Click to reveal answer
What does AKS stand for?
AAzure Key Storage
BAzure Knowledge Suite
CAzure Kernel System
DAzure Kubernetes Service
Which Azure Load Balancer type supports multiple availability zones?
AStandard Load Balancer
BClassic Load Balancer
CBasic Load Balancer
DInternal Load Balancer
In AKS, what happens when you create a service of type LoadBalancer?
AService becomes internal only
BPods are deleted automatically
CAzure provisions a Load Balancer and assigns a public IP
DNo changes occur in Azure infrastructure
What is the main purpose of Azure Load Balancer in AKS?
AStore container images
BDistribute traffic to pods and nodes
CManage Kubernetes clusters
DMonitor application logs
Which component routes traffic from Azure Load Balancer to pods inside AKS nodes?
AKube-proxy
BAzure DNS
CAzure Blob Storage
DAzure Monitor
Describe the end-to-end request flow when a client accesses an application running on AKS with Azure Load Balancer.
Think about how traffic moves from outside the cloud to the container running your app.
You got /5 concepts.
    Explain the differences and benefits of using Standard Azure Load Balancer over Basic in an AKS environment.
    Consider availability, features, and production readiness.
    You got /5 concepts.

      Practice

      (1/5)
      1. What is the primary purpose of using an Azure Load Balancer with AKS (Azure Kubernetes Service)?
      easy
      A. To store data persistently for containers
      B. To distribute incoming network traffic evenly across multiple pods
      C. To build container images automatically
      D. To monitor container resource usage

      Solution

      1. Step 1: Understand AKS and Load Balancer roles

        AKS runs containerized apps, and Azure Load Balancer distributes traffic to these apps.

      2. Step 2: Identify the main function of Load Balancer

        It balances incoming requests across pods to improve availability and scalability.

      3. Final Answer:

        To distribute incoming network traffic evenly across multiple pods -> Option B

      4. Quick Check:

        Load Balancer = traffic distribution [OK]
      Hint: Load Balancer = spreading traffic evenly [OK]
      Common Mistakes:
      • Confusing Load Balancer with storage or monitoring
      • Thinking Load Balancer builds container images
      • Assuming Load Balancer manages pod resources
      2. Which Kubernetes service type should you specify in your AKS deployment YAML to create an Azure Load Balancer automatically?
      easy
      A. LoadBalancer
      B. NodePort
      C. ClusterIP
      D. ExternalName

      Solution

      1. Step 1: Review Kubernetes service types

        ClusterIP exposes service internally, NodePort exposes on node port, LoadBalancer creates cloud LB, ExternalName maps to external DNS.

      2. Step 2: Identify service type for Azure Load Balancer

        Using type: LoadBalancer triggers Azure to provision a Load Balancer automatically.

      3. Final Answer:

        LoadBalancer -> Option A

      4. Quick Check:

        Service type LoadBalancer = Azure LB creation [OK]
      Hint: Use type LoadBalancer to get Azure LB automatically [OK]
      Common Mistakes:
      • Choosing ClusterIP which is internal only
      • Confusing NodePort with automatic LB creation
      • Using ExternalName which is DNS mapping only
      3. Given this Kubernetes service YAML snippet in AKS: 
      apiVersion: v1
kind: Service
metadata:
  name: myapp-service
spec:
  type: LoadBalancer
  selector:
    app: myapp
  ports:
  - protocol: TCP
    port: 80
    targetPort: 8080
      What happens when this service is applied?
      medium
      A. An Azure Load Balancer is created and routes port 80 traffic to pods on port 8080
      B. Pods are exposed only inside the cluster on port 8080
      C. Traffic on port 8080 is blocked by default
      D. A NodePort service is created exposing port 80 on all nodes

      Solution

      1. Step 1: Analyze service type and ports

        Service type is LoadBalancer, so Azure LB is created. It listens on port 80 externally and forwards to targetPort 8080 on pods.

      2. Step 2: Understand traffic flow

        External traffic on port 80 hits Azure LB, which routes it to pods' port 8080 matching selector app: myapp.

      3. Final Answer:

        An Azure Load Balancer is created and routes port 80 traffic to pods on port 8080 -> Option A

      4. Quick Check:

        LoadBalancer + port mapping = external traffic routing [OK]
      Hint: LoadBalancer routes external port to pod targetPort [OK]
      Common Mistakes:
      • Thinking pods are exposed only internally
      • Confusing NodePort with LoadBalancer
      • Assuming traffic is blocked without explicit rules
      4. You deployed an AKS service with type: LoadBalancer, but the external IP remains <pending> for a long time. What is the most likely cause?
      medium
      A. The service selector labels do not match any pods
      B. The Kubernetes cluster is not running
      C. The pods are not listening on the targetPort
      D. The Azure Load Balancer quota is exceeded in the subscription

      Solution

      1. Step 1: Understand LoadBalancer IP allocation

        Azure assigns an external IP when provisioning the Load Balancer. If quota is exceeded, IP remains pending.

      2. Step 2: Differentiate causes

        Selector mismatch or pod ports cause traffic issues but do not block IP assignment. Cluster down would prevent service creation.

      3. Final Answer:

        The Azure Load Balancer quota is exceeded in the subscription -> Option D

      4. Quick Check:

        Pending IP often means quota limit reached [OK]
      Hint: Pending IP usually means Azure LB quota exceeded [OK]
      Common Mistakes:
      • Blaming selector mismatch for IP assignment delay
      • Assuming pods not listening blocks IP allocation
      • Thinking cluster down still allows service creation
      5. You want to design a highly available AKS application exposed via Azure Load Balancer that can handle sudden traffic spikes. Which combination of strategies is best?
      hard
      A. Use type: NodePort service and rely on Azure VM scale sets only
      B. Use type: ClusterIP service with manual pod scaling and no health probes
      C. Use type: LoadBalancer service, enable Horizontal Pod Autoscaler, and configure Azure Load Balancer health probes
      D. Use type: ExternalName service pointing to an external DNS

      Solution

      1. Step 1: Choose correct service type for external exposure

        type: LoadBalancer creates Azure LB to distribute traffic externally.

      2. Step 2: Enable autoscaling and health checks

        Horizontal Pod Autoscaler adjusts pod count for traffic spikes; health probes ensure LB routes only to healthy pods.

      3. Step 3: Evaluate other options

        ClusterIP is internal only; NodePort exposes ports but lacks automatic LB; ExternalName is DNS mapping, not load balancing.

      4. Final Answer:

        Use type: LoadBalancer service, enable Horizontal Pod Autoscaler, and configure Azure Load Balancer health probes -> Option C

      5. Quick Check:

        LoadBalancer + autoscale + health probes = high availability [OK]
      Hint: Combine LoadBalancer, autoscaling, and health probes for HA [OK]
      Common Mistakes:
      • Using ClusterIP or ExternalName for external traffic
      • Ignoring autoscaling for traffic spikes
      • Not configuring health probes causing downtime