Network Load Balancer (NLB) in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the type of load balancer as Network Load Balancer.

AWS

LoadBalancerType: '[1]'

Drag options to blanks, or click blank then click option'

Agateway

Bnetwork

Cclassic

Dapplication

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'application' which is for Application Load Balancer (Layer 7).

Using 'classic' which is an older load balancer type.

The Network Load Balancer type is specified by setting LoadBalancerType to network.

2fill in blank

medium

Complete the code to set the listener protocol for a Network Load Balancer.

AWS

Listeners: [{ Protocol: '[1]', Port: 80, DefaultActions: [...] }]

Drag options to blanks, or click blank then click option'

ATCP

BHTTPS

CHTTP

DUDP

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'HTTP' or 'HTTPS' which are Layer 7 protocols.

Choosing 'UDP' when TCP is more common for NLB listeners.

Network Load Balancers use TCP protocol for listeners to handle Layer 4 traffic.

3fill in blank

hard

Fix the error in the target group protocol for a Network Load Balancer.

AWS

TargetGroupProtocol: '[1]'

Drag options to blanks, or click blank then click option'

AHTTP

BHTTPS

CTCP

DSSL

Attempts:

3 left

💡 Hint

Common Mistakes

Setting target group protocol to HTTP or HTTPS which are for ALB.

Using SSL which is deprecated for NLB target groups.

Network Load Balancer target groups must use TCP protocol to match the NLB's Layer 4 operation.

4fill in blank

hard

Fill both blanks to configure health check protocol and port for a Network Load Balancer target group.

AWS

HealthCheckProtocol: '[1]', HealthCheckPort: '[2]'

Drag options to blanks, or click blank then click option'

ATCP

BHTTP

C80

D443

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTP protocol for health checks which is for ALB.

Setting health check port to 443 without targets listening there.

Network Load Balancer health checks use TCP protocol and typically port 80 for checking target health.

5fill in blank

hard

Fill all three blanks to define a Network Load Balancer with cross-zone load balancing enabled and an Elastic IP allocation.

AWS

LoadBalancerAttributes: [{ Key: '[1]', Value: '[2]' }], Subnets: ['subnet-12345'], IpAddressType: '[3]'

Drag options to blanks, or click blank then click option'

Aload_balancing.cross_zone.enabled

Btrue

Cipv4

Daccess_logs.s3.enabled

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'access_logs.s3.enabled' which is unrelated to cross-zone load balancing.

Setting cross-zone enabled to 'false' disables even traffic distribution.

To enable cross-zone load balancing, set the attribute load_balancing.cross_zone.enabled to true. The IP address type for NLB is usually ipv4.