Cross-zone load balancing in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is cross-zone load balancing in AWS Elastic Load Balancer?

Cross-zone load balancing evenly distributes incoming traffic across all registered targets in all enabled Availability Zones, helping to balance load and improve fault tolerance.

beginner

Why is cross-zone load balancing useful?

It prevents uneven traffic distribution when some zones have more targets than others, ensuring better resource utilization and higher availability.

intermediate

How do you enable cross-zone load balancing on an AWS Application Load Balancer?

Cross-zone load balancing is enabled by default on Application Load Balancers and cannot be disabled.

intermediate

Is cross-zone load balancing enabled by default on Classic Load Balancers?

No, on Classic Load Balancers, cross-zone load balancing is disabled by default and must be enabled manually.

advanced

What is a potential cost implication of enabling cross-zone load balancing on Classic Load Balancers?

Enabling cross-zone load balancing on Classic Load Balancers can increase data transfer costs because traffic may cross Availability Zones.

What does cross-zone load balancing do?

A Distributes traffic evenly across all targets in all zones

B Sends traffic only to targets in the same zone

C Blocks traffic from certain zones

D Routes traffic based on IP address only

Cross-zone load balancing distributes incoming traffic evenly across all registered targets in all enabled Availability Zones.

Is cross-zone load balancing enabled by default on AWS Application Load Balancers?

A No, it is not supported

B Yes, and it cannot be disabled

C Yes, but it can be disabled

D No, it must be enabled manually

Application Load Balancers have cross-zone load balancing enabled by default and it cannot be turned off.

What must you do to enable cross-zone load balancing on a Classic Load Balancer?

A Enable it manually in the load balancer settings

B It is enabled by default, no action needed

C Create a new load balancer

D Use an Application Load Balancer instead

Cross-zone load balancing is disabled by default on Classic Load Balancers and must be enabled manually.

What is a downside of enabling cross-zone load balancing on Classic Load Balancers?

A Reduced fault tolerance

B Slower response times

C Increased data transfer costs between zones

D Limited to one Availability Zone

Cross-zone load balancing can increase data transfer costs because traffic may cross Availability Zones.

Which AWS load balancer type has cross-zone load balancing enabled by default and cannot be disabled?

A Gateway Load Balancer

B Classic Load Balancer

C Network Load Balancer

D Application Load Balancer

Application Load Balancers have cross-zone load balancing enabled by default and it cannot be disabled.

Explain what cross-zone load balancing is and why it is important in AWS.

Think about how traffic is shared among servers in different zones.

Describe the differences in cross-zone load balancing behavior between Classic Load Balancers and Application Load Balancers.

Focus on default settings and manual configuration.

Practice

1. What is the main benefit of enabling cross-zone load balancing in AWS Elastic Load Balancer?

easy

A. It increases the maximum number of connections per target.

B. It automatically scales the number of Availability Zones.

C. It evenly distributes incoming traffic across all registered targets in all enabled Availability Zones.

D. It encrypts all traffic between the load balancer and targets.

Solution

1. Step 1: Understand cross-zone load balancing purpose

   Cross-zone load balancing spreads traffic evenly across targets in all zones, preventing uneven load.

2. Step 2: Compare options to this purpose

   Only It evenly distributes incoming traffic across all registered targets in all enabled Availability Zones. describes this even distribution. Other options describe unrelated features.

3. Final Answer:

   It evenly distributes incoming traffic across all registered targets in all enabled Availability Zones. -> Option C

4. Quick Check:

   Cross-zone load balancing = even traffic spread [OK]

Hint: Cross-zone means traffic spreads evenly across zones [OK]

Common Mistakes:

• Confusing cross-zone with encryption or scaling
• Thinking it increases max connections per target
• Assuming it changes number of zones automatically

2. Which of the following is the correct way to enable cross-zone load balancing in an AWS Application Load Balancer using Terraform?

easy

A. enable_cross_zone_load_balancing = false

B. cross_zone_load_balancing = true

C. cross_zone_enabled = true

D. enable_cross_zone_load_balancing = true

Solution

1. Step 1: Recall Terraform attribute for cross-zone load balancing

   The correct attribute is enable_cross_zone_load_balancing and it must be set to true to enable.

2. Step 2: Match options to correct syntax

   Only enable_cross_zone_load_balancing = true uses the exact attribute name and sets it to true.

3. Final Answer:

   enable_cross_zone_load_balancing = true -> Option D

4. Quick Check:

   Terraform attribute = enable_cross_zone_load_balancing true [OK]

Hint: Look for exact attribute name with true value [OK]

Common Mistakes:

• Using incorrect attribute names like cross_zone_load_balancing
• Setting the value to false instead of true
• Confusing with other unrelated settings

3. Given the following AWS CLI command to enable cross-zone load balancing on a Classic Load Balancer:

aws elb modify-load-balancer-attributes --load-balancer-name my-load-balancer --load-balancer-attributes '{"CrossZoneLoadBalancing":{"Enabled":true}}'

What will be the effect of running this command?

medium

A. Cross-zone load balancing will be disabled for the load balancer.

B. Cross-zone load balancing will be enabled, distributing traffic evenly across zones.

C. The load balancer will be deleted.

D. The command will fail due to syntax error.

Solution

1. Step 1: Analyze the AWS CLI command structure

   The command modifies load balancer attributes, specifically enabling CrossZoneLoadBalancing by setting Enabled to true.

2. Step 2: Understand the effect of enabling CrossZoneLoadBalancing

   Enabling it causes traffic to be evenly distributed across all registered targets in all zones.

3. Final Answer:

   Cross-zone load balancing will be enabled, distributing traffic evenly across zones. -> Option B

4. Quick Check:

   Enable CrossZoneLoadBalancing true = even traffic spread [OK]

Hint: Enabled true means cross-zone load balancing is active [OK]

Common Mistakes:

• Thinking the command disables the feature
• Assuming the load balancer is deleted
• Believing the command syntax is incorrect

4. 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

A. You forgot to register targets in all Availability Zones.

B. Cross-zone load balancing is not supported on Network Load Balancers.

C. Cross-zone load balancing requires manual DNS updates.

D. You must enable cross-zone load balancing on each target instance.

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]

Hint: 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

5. You have an Application Load Balancer spanning three Availability Zones with cross-zone load balancing enabled. One zone has only one healthy target, while the others have three each. How does cross-zone load balancing affect traffic distribution?

hard

A. Traffic is evenly distributed across all targets regardless of zone count.

B. Traffic is evenly distributed across zones, so the zone with one target gets one-third of traffic.

C. Traffic is sent only to zones with the most targets.

D. Traffic is distributed randomly without considering zones or targets.

Solution

1. Step 1: Understand cross-zone load balancing behavior

   With cross-zone load balancing enabled, each load balancer node distributes traffic evenly across all healthy registered targets, regardless of their Availability Zone.

2. Step 2: Apply to given scenario

   Total healthy targets: 1 + 3 + 3 = 7. Each target receives approximately equal traffic (1/7), so the zone with one target gets about 1/7 of total traffic.

3. Final Answer:

   Traffic is evenly distributed across all targets regardless of zone count. -> Option A

4. Quick Check:

   Cross-zone load balancing = even across all targets [OK]

Hint: Cross-zone balances evenly across all targets, ignoring zone boundaries [OK]

Common Mistakes:

• Confusing with default zone-isolated balancing (even per zone)
• Thinking traffic prefers zones with more targets
• Believing distribution ignores target count