Listener rules and routing in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a listener in AWS Elastic Load Balancer?

A listener is a process that checks for connection requests using a specific protocol and port. It forwards requests to target groups based on rules.

beginner

What do listener rules do in AWS load balancing?

Listener rules define how incoming requests are routed to target groups based on conditions like URL path or host headers.

beginner

Name two common conditions used in listener rules for routing.

Path-based routing (URL path) and host-based routing (domain name) are common conditions to decide where to send traffic.

intermediate

What happens if no listener rule matches an incoming request?

The request is routed to the default target group specified in the listener configuration.

intermediate

Why is the order of listener rules important?

Rules are evaluated in priority order. The first matching rule is applied, so order controls which rule takes effect when multiple match.

What does a listener in AWS Elastic Load Balancer do?

A Checks for connection requests and forwards them based on rules

B Stores data for the load balancer

C Creates virtual machines

D Monitors server CPU usage

A listener waits for connection requests on a port and protocol and forwards them to target groups based on rules.

Which condition can be used in listener rules to route traffic?

A User IP address

B Server CPU load

C URL path

D Database size

Listener rules commonly use URL path or host headers to route traffic.

If no listener rule matches a request, where is the traffic sent?

A To the first target group created

B Dropped immediately

C To a random server

D To the default target group

Requests not matching any rule go to the default target group set in the listener.

How are listener rules evaluated?

A By priority order, first match applies

B Randomly

C Alphabetically by target group name

D By server load

Listener rules have priorities; the first rule that matches the request is used.

What protocol and port does a listener use?

A Always HTTPS on port 443

B Specified by the user, e.g., HTTP on port 80

C FTP on port 21

D SMTP on port 25

Listeners are configured with a protocol and port like HTTP on 80 or HTTPS on 443.

Explain how listener rules control routing in AWS Elastic Load Balancer.

Think about how requests are matched and sent to servers.

Describe what happens when a request arrives at a load balancer listener with multiple rules.

Focus on the order and matching process.

Practice

1. What does a listener rule in AWS Elastic Load Balancer do?

easy

A. It monitors CPU usage of servers.

B. It creates new virtual machines automatically.

C. It stores data permanently for applications.

D. It directs incoming traffic to specific targets based on conditions.

Solution

1. Step 1: Understand listener role

   A listener waits for incoming traffic on a load balancer and applies rules to route it.

2. Step 2: Identify what rules do

   Listener rules check conditions like URL path or host header to send traffic to the right target group.

3. Final Answer:

   It directs incoming traffic to specific targets based on conditions. -> Option D

4. Quick Check:

   Listener rules route traffic [OK]

Hint: Listener rules route traffic based on conditions [OK]

Common Mistakes:

• Confusing listener rules with server creation
• Thinking listener rules store data
• Mixing monitoring with routing

2. Which of the following is the correct way to specify a path pattern condition in an AWS listener rule?

easy

A. Method: 'POST'

B. PathPattern: '/images/*'

C. SourceIP: '192.168.1.1'

D. HostHeader: 'example.com'

Solution

1. Step 1: Identify path pattern syntax

   Path patterns use wildcards like '*' to match URL paths, e.g., '/images/*'.

2. Step 2: Match option to path pattern

   PathPattern: '/images/*' correctly shows a path pattern condition; others show different conditions.

3. Final Answer:

   <code>PathPattern: '/images/*'</code> -> Option B

4. Quick Check:

   Path pattern uses wildcard * [OK]

Hint: Path patterns use '*' wildcard for matching paths [OK]

Common Mistakes:

• Confusing host header with path pattern
• Using IP or method instead of path pattern
• Missing quotes or wrong syntax

3. Given these listener rules with priorities:
1: HostHeader = 'app.example.com' -> TargetGroupA
2: PathPattern = '/api/*' -> TargetGroupB
What happens when a request comes to app.example.com/api/data?

medium

A. Traffic goes to TargetGroupB because path pattern matches better.

B. Traffic is rejected because two rules match.

C. Traffic goes to TargetGroupA because host header rule has higher priority.

D. Traffic goes to a default target group.

Solution

1. Step 1: Check rule priorities

   Rules are checked in order of priority number; lower number means higher priority.

2. Step 2: Evaluate matching rules

   Request matches both host header and path pattern, but host header rule has priority 1.

3. Final Answer:

   Traffic goes to TargetGroupA because host header rule has higher priority. -> Option C

4. Quick Check:

   Lower priority number wins routing [OK]

Hint: Lower priority number rules apply first [OK]

Common Mistakes:

• Assuming path pattern overrides host header
• Thinking multiple matches cause rejection
• Ignoring rule priority order

4. You created a listener rule with priority 5 for path pattern /app/*, but traffic to /app/home is not routed correctly. What is a likely cause?

medium

A. Another rule with priority 1 matches the request first.

B. Path pattern syntax /app/* is invalid.

C. Listener rules do not support path patterns.

D. Target group is not attached to the load balancer.

Solution

1. Step 1: Check rule priority impact

   Rules with lower priority numbers are evaluated first and can override later rules.

2. Step 2: Consider other matching rules

   If a rule with priority 1 matches the request, the priority 5 rule won't be used.

3. Final Answer:

   Another rule with priority 1 matches the request first. -> Option A

4. Quick Check:

   Lower priority number rules block later ones [OK]

Hint: Check for higher priority rules blocking traffic [OK]

Common Mistakes:

• Thinking path pattern syntax is wrong
• Believing listener rules ignore path patterns
• Assuming target group attachment causes routing failure

5. You want to route traffic to different target groups based on both host header and path pattern. Which setup correctly achieves this in AWS listener rules?

hard

A. Create a rule with priority 1: HostHeader = 'shop.example.com' AND PathPattern = '/products/*' -> TargetGroupShop

B. Create two separate rules with same priority: one for HostHeader, one for PathPattern

C. Use only one rule with PathPattern to cover all hosts

D. Set listener to forward all traffic to a single target group and filter inside the app

Solution

1. Step 1: Understand combined conditions

   Listener rules can combine multiple conditions like host header AND path pattern in one rule.

2. Step 2: Evaluate options

   Create a rule with priority 1: HostHeader = 'shop.example.com' AND PathPattern = '/products/*' -> TargetGroupShop correctly uses combined conditions with a single priority rule; others either conflict or do not filter properly.

3. Final Answer:

   Create a rule with priority 1: HostHeader = 'shop.example.com' AND PathPattern = '/products/*' -> TargetGroupShop -> Option A

4. Quick Check:

   Combine conditions in one rule for precise routing [OK]

Hint: Combine host and path in one rule for exact routing [OK]

Common Mistakes:

• Using same priority for multiple rules causing conflicts
• Relying on app filtering instead of load balancer routing
• Using only path pattern ignoring host header