Why load balancing matters in AWS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a load balancer that distributes traffic evenly.

AWS

LoadBalancerName: "MyLoadBalancer"
Listeners:
  - Protocol: HTTP
    LoadBalancerPort: 80
    InstancePort: [1]

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

A80

B22

C443

D8080

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 22 which is for SSH, not HTTP.

The load balancer listens on port 80 to distribute HTTP traffic to instances on the same port.

2fill in blank

medium

Complete the code to specify the health check path for the load balancer.

AWS

HealthCheck:
  Target: "HTTP:[1]/health"
  Interval: 30
  Timeout: 5

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

A22

B80

C443

D8080

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 22 which is for SSH, not HTTP.

The health check uses HTTP on port 80 to verify instance health.

3fill in blank

hard

Fix the error in the listener configuration to allow HTTPS traffic.

AWS

Listeners:
  - Protocol: [1]
    LoadBalancerPort: 443
    InstancePort: 443

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

AHTTP

BFTP

CHTTPS

DSSH

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTP on port 443 causes errors.

HTTPS protocol is required for secure traffic on port 443.

4fill in blank

hard

Fill both blanks to configure a load balancer with cross-zone load balancing enabled and a security group.

AWS

LoadBalancerAttributes:
  CrossZoneLoadBalancing: [1]
SecurityGroups:
  - [2]

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

Atrue

Bfalse

Csg-123abc45

Dsg-678def90

Attempts:

3 left

💡 Hint

Common Mistakes

Setting cross-zone load balancing to false reduces efficiency.

Cross-zone load balancing should be enabled with 'true'. Security group IDs like 'sg-123abc45' control access.

5fill in blank

hard

Fill all three blanks to define a target group with a health check path and protocol.

AWS

TargetGroup:
  Name: "MyTargetGroup"
  Protocol: [1]
  Port: [2]
  HealthCheckPath: "[3]"

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

AHTTP

B80

C/healthcheck

DTCP

Attempts:

3 left

💡 Hint

Common Mistakes

Using TCP protocol without a health check path causes monitoring issues.

The target group uses HTTP on port 80 with a health check path '/healthcheck' to monitor instance health.