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?
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.
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?
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/*'.
An ALB listener receives a request that does not match any configured listener rule. What is the expected behavior?
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.
You want to ensure your ALB only routes requests coming from 'example.com'. Which listener rule condition should you use?
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.
You have an ALB with many path-based listener rules. What is the best practice to optimize routing performance and maintainability?
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.