Cross-zone load balancing in AWS - Time & Space Complexity

Time Complexity: Cross-zone load balancing

O(n)

Understanding Time Complexity

When using cross-zone load balancing, requests are distributed across multiple zones. We want to understand how the number of requests affects the work done by the load balancer.

How does the load balancer's effort grow as more requests come in?

Scenario Under Consideration

Analyze the time complexity of request distribution with cross-zone load balancing enabled.

// Enable cross-zone load balancing on a Network Load Balancer
aws elbv2 modify-load-balancer-attributes \
  --load-balancer-arn arn:aws:elasticloadbalancing:region:account-id:loadbalancer/net/my-load-balancer/50dc6c495c0c9188 \
  --attributes Key=load_balancing.cross_zone.enabled,Value=true

// Incoming requests are distributed evenly across all registered targets in all zones
// Each request triggers a routing decision by the load balancer
    

This setup evenly spreads incoming requests across all targets in every zone, balancing the load.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Routing each incoming request to a target in any zone.
• How many times: Once per incoming request.

How Execution Grows With Input

Each new request causes the load balancer to pick a target across zones. More requests mean more routing decisions.

Input Size (n)	Approx. Api Calls/Operations
10	10 routing decisions
100	100 routing decisions
1000	1000 routing decisions

Pattern observation: The number of routing operations grows directly with the number of requests.

Final Time Complexity

Time Complexity: O(n)

This means the load balancer's work grows linearly with the number of incoming requests.

Common Mistake

[X] Wrong: "Cross-zone load balancing reduces the number of routing decisions the load balancer makes."

[OK] Correct: The load balancer still routes every request; cross-zone balancing only changes how targets are chosen, not how many routing operations happen.

Interview Connect

Understanding how load balancers handle requests helps you design systems that scale well. This skill shows you can think about how cloud services behave as demand grows.

Self-Check

"What if cross-zone load balancing was disabled? How would the time complexity of routing requests change?"

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