Listener rules and routing in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does an ALB listener rule prioritize routing?

An Application Load Balancer (ALB) has multiple listener rules configured. How does the ALB decide which rule to apply when a request matches multiple rules?

A The ALB applies the rule with the highest priority number.

B The ALB applies the rule with the lowest priority number.

C The ALB applies the rule that was created most recently.

D The ALB applies all matching rules in parallel.

💡 Hint

Think about how priority numbers work in ordering rules.

Listener rules have priority numbers where lower numbers have higher priority. The ALB applies the rule with the lowest priority number that matches the request.

❓ Configuration

intermediate

Which listener rule configuration routes traffic to a target group for path '/images/*'?

You want to route all requests with paths starting with '/images/' to a specific target group. Which listener rule condition correctly matches this path pattern?

A Path pattern is '/images/*'

B Path is exactly '/images/*'

C Path is '/images/*' (wildcard supported)

D Host header is '/images/*'

💡 Hint

Listener rules use path patterns, not exact path or host header for this.

Listener rules use path pattern conditions to match URL paths with wildcards. The correct syntax is 'Path pattern is /images/*'.

❓ Architecture

advanced

What happens if no listener rule matches a request?

An ALB listener receives a request that does not match any configured listener rule. What is the expected behavior?

A The ALB retries the request on another listener.

B The ALB returns a 404 Not Found error to the client.

C The ALB drops the request without response.

D The ALB forwards the request to the default target group of the listener.

💡 Hint

Consider what the default target group is used for in a listener.

If no listener rule matches, the ALB forwards the request to the listener's default target group.

❓ security

advanced

Which listener rule condition can help restrict traffic to a specific domain?

You want to ensure your ALB only routes requests coming from 'example.com'. Which listener rule condition should you use?

A Host header condition with 'example.com'

B Source IP condition with 'example.com'

C Path pattern condition with '/example.com/*'

D HTTP method condition with 'example.com'

💡 Hint

Think about how domain names are represented in HTTP requests.

The host header condition matches the domain name in the HTTP request, so using 'Host header is example.com' restricts traffic to that domain.

✅ Best Practice

expert

How should you design listener rules for efficient routing with many path patterns?

You have an ALB with many path-based listener rules. What is the best practice to optimize routing performance and maintainability?

A Create one listener rule per path and assign the same priority to all.

B Use a single listener rule with a complex regex path pattern.

C Group related paths into fewer rules with clear, non-overlapping path patterns and use priority numbers carefully.

D Use many low-priority rules with overlapping path patterns.

💡 Hint

Think about how priority and rule clarity affect routing.

Grouping related paths into fewer, clear, non-overlapping rules with carefully assigned priorities improves routing efficiency and makes maintenance easier.

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