Bird
0
0

You configured cross-zone load balancing on your Network Load Balancer but notice traffic is still uneven across zones. What is the most likely cause?

medium📝 Debug Q14 of 15
AWS - Elastic Load Balancing
You configured cross-zone load balancing on your Network Load Balancer but notice traffic is still uneven across zones. What is the most likely cause?
AYou forgot to register targets in all Availability Zones.
BCross-zone load balancing is not supported on Network Load Balancers.
CCross-zone load balancing requires manual DNS updates.
DYou must enable cross-zone load balancing on each target instance.
Step-by-Step Solution
Solution:
  1. Step 1: Recall cross-zone load balancing support on Network Load Balancers

    Network Load Balancers support cross-zone load balancing, but it must be enabled and targets must be registered in all zones.
  2. Step 2: Identify why traffic is uneven

    If targets are missing in some zones, traffic cannot be balanced evenly despite cross-zone load balancing being enabled.
  3. Final Answer:

    You forgot to register targets in all Availability Zones. -> Option A
  4. Quick Check:

    Targets missing in zones = uneven traffic [OK]
Quick Trick: Ensure targets exist in all zones for balancing [OK]
Common Mistakes:
  • Thinking cross-zone load balancing is unsupported on NLB
  • Believing DNS updates are needed
  • Assuming enabling on targets is required

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes