Target groups concept in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a target group in AWS Elastic Load Balancing?

A target group is a set of resources, like EC2 instances or IP addresses, that a load balancer directs traffic to. It helps organize and manage where requests go.

beginner

How does a load balancer use target groups?

The load balancer routes incoming traffic to one or more target groups based on rules. Each target group contains targets that receive the traffic.

intermediate

What types of targets can be registered in a target group?

Targets can be EC2 instances, IP addresses, or Lambda functions, depending on the load balancer type and configuration.

intermediate

Why is health checking important in target groups?

Health checks monitor if targets are healthy and able to handle requests. Unhealthy targets are removed from routing until they recover, ensuring reliable service.

advanced

Can a target group be used by multiple load balancers?

No, a target group can only be used by one load balancer at a time. Each load balancer must have its own target groups to route traffic.

What does a target group in AWS primarily contain?

A A list of resources to receive traffic

B Security rules for instances

C User access policies

D Billing information

A target group contains resources like EC2 instances or IP addresses that receive traffic from a load balancer.

Which of the following can NOT be a target in a target group?

A S3 bucket

B EC2 instance

C Lambda function

D IP address

S3 buckets cannot be targets in a target group; targets are compute resources or IPs.

What happens if a target in a target group fails health checks?

A It continues to receive traffic

B It is terminated automatically

C It is removed from routing until healthy

D It is replaced by a new instance

Unhealthy targets are temporarily removed from routing to avoid sending traffic to failing resources.

Can one target group be associated with multiple load balancers?

A Yes

B No

C Only with Classic Load Balancers

D Only with Network Load Balancers

A target group can only be associated with one load balancer at a time.

What is the main benefit of using target groups?

A Monitoring billing costs

B Encrypting data in transit

C Storing user credentials

D Organizing and managing traffic routing

Target groups help organize resources and manage how traffic is routed by load balancers.

Explain what a target group is and how it works with a load balancer in AWS.

Think about how a load balancer decides where to send incoming requests.

Describe the importance of health checks in target groups and what happens when a target is unhealthy.

Consider what happens if a server is down or not responding.

Practice

1. What is the main purpose of a target group in AWS Elastic Load Balancing?

easy

A. To create virtual private clouds

B. To store user data securely

C. To manage DNS records

D. To group servers for load balancing and health checks

Solution

1. Step 1: Understand target group role

   A target group groups servers (targets) to distribute incoming traffic.

2. Step 2: Identify key functions

   It also performs health checks to ensure traffic goes only to healthy servers.

3. Final Answer:

   To group servers for load balancing and health checks -> Option D

4. Quick Check:

   Target groups = server grouping + health checks [OK]

Hint: Target groups organize servers for load balancing [OK]

Common Mistakes:

• Confusing target groups with security groups
• Thinking target groups store data
• Mixing target groups with VPC functions

2. Which of the following is the correct way to specify a target group protocol in AWS CLI?

easy

A. aws elbv2 create-target-group --protocol HTTP

B. aws elbv2 create-target-group --protocol FTP

C. aws elbv2 create-target-group --protocol SMTP

D. aws elbv2 create-target-group --protocol SSH

Solution

1. Step 1: Recall supported protocols for target groups

   AWS target groups support HTTP, HTTPS, TCP, TLS, UDP, and TCP_UDP protocols.

2. Step 2: Identify valid protocol in options

   HTTP is a valid protocol; FTP, SMTP, and SSH are not supported for target groups.

3. Final Answer:

   aws elbv2 create-target-group --protocol HTTP -> Option A

4. Quick Check:

   HTTP is valid protocol for target groups [OK]

Hint: Use HTTP or HTTPS for target group protocol [OK]

Common Mistakes:

• Using unsupported protocols like FTP or SSH
• Confusing target group protocol with security group rules
• Misspelling protocol names

3. Given a target group with 3 registered targets, two healthy and one unhealthy, how will the load balancer route traffic?

medium

A. It sends traffic only to the two healthy targets

B. It sends traffic equally to all three targets

C. It sends traffic only to the unhealthy target

D. It stops sending traffic until all targets are healthy

Solution

1. Step 1: Understand health check impact

   Load balancers route traffic only to targets marked healthy by health checks.

2. Step 2: Apply to given targets

   With two healthy and one unhealthy, traffic goes only to the two healthy targets.

3. Final Answer:

   It sends traffic only to the two healthy targets -> Option A

4. Quick Check:

   Traffic routes only to healthy targets [OK]

Hint: Load balancer skips unhealthy targets [OK]

Common Mistakes:

• Assuming traffic goes to all targets regardless of health
• Thinking traffic stops if any target is unhealthy
• Confusing unhealthy targets with backup targets

4. You created a target group but your load balancer shows no healthy targets. What is the most likely issue?

medium

A. Load balancer is in a different region

B. Security group blocks health check traffic

C. Targets are not registered with the target group

D. Target group protocol is set to FTP

Solution

1. Step 1: Check common causes for no healthy targets

   Targets not registered or security blocking health checks cause no healthy targets.

2. Step 2: Analyze options

   Security group blocking health check traffic prevents health checks from succeeding, causing targets to be unhealthy.

3. Final Answer:

   Security group blocks health check traffic -> Option B

4. Quick Check:

   Blocked health checks cause no healthy targets [OK]

Hint: Check security groups allow health check ports [OK]

Common Mistakes:

• Ignoring security group rules
• Assuming region mismatch causes health check failure
• Using unsupported protocols like FTP

5. You want to route HTTP traffic to two different target groups based on URL path: /images/* to one group and /api/* to another. Which AWS service feature should you use?

hard

A. Elastic IP addresses assigned to each target group

B. Network Load Balancer with static IP routing

C. Application Load Balancer with path-based routing rules

D. Classic Load Balancer with SSL termination

Solution

1. Step 1: Identify routing needs

   Routing based on URL path requires path-based routing rules.

2. Step 2: Match AWS service feature

   Application Load Balancer supports path-based routing to different target groups.

3. Step 3: Exclude incorrect options

   Network Load Balancer does not support path-based routing; Classic Load Balancer lacks this feature; Elastic IPs do not route traffic by path.

4. Final Answer:

   Application Load Balancer with path-based routing rules -> Option C

5. Quick Check:

   Path-based routing = Application Load Balancer [OK]

Hint: Use ALB for URL path routing to target groups [OK]

Common Mistakes:

• Using Network Load Balancer for path routing
• Confusing Classic Load Balancer features
• Thinking Elastic IPs control routing rules