Loading video player...
A company is running a microservices
application with multiple back-end
services. They want to use a single
application load balancer to distribute
traffic to different target groups based
on the URL path in the request. For
example, requests to SL API star should
go to API service target group and
requests to the /webstar should go to
the web front-end target group. So,
which features should the solutions
architect configure to meet this
requirement? Let's identify the key
hints. Application load balancer. So
this is a layer 7 load balancer, right?
Route based on URL path. So we're going
to need to be able to inspect the HTTP
content and a single load balancer that
supports multiple services. So these are
our hints. So option one, configure the
listener rules with pathbased routing
conditions based on the application load
balancer. So we're going to use an
application load balancer. Option two,
deploy a network load balancer and
configure multiple listeners on
different ports for each service. Option
three, create separate application load
balancers for each microser and use
route 53 weighted routing to kind of do
the routing. Option four, implement
client side service discovery and
routing logic in the application code.
Leave your answer in the comments below.
Now, our hint says that URL path
routing, so that means inspecting HTTP
content, which means layer 7. Now, a
network load balancer, if we looked at
the options, is layer 4. It can't
actually see URL patterns. It's out.
Separate ALBs could work, but our hint
says a single load balancer and also
that will probably be more expensive.
Three client side routing pushes
complexity to the application which AWS
typically doesn't go for has an answer.
So the correct answer is ALB listener
rules with pathbased routing. Remember
ALB is layer 7. It can expect HTTP
content including URL paths. Plus
listener rules will route to slash API
for one target group and it will route
SLeb to another. One ALB multiple
services matches all of our hints. And
remember NLB equals layer 4 fast but
blind to HTTP. An ALB or application
load balancer that's a layer 7 router.
It's going to tell is it routing.
AWS Solutions Architect | Question 9 of 65 Routing microservices with one load balancer? Let’s do it the right way. ⚙️🌐 The scenario: A company needs /api/* requests to hit the API service target group and /web/* requests to hit the web frontend target group—using a single Application Load Balancer. The challenge: Which feature lets you route traffic to different target groups based on the URL path at Layer 7? The solution: ✅ Application Load Balancer listener rules ✅ Path-based routing to multiple target groups 🎯 👆 Watch the breakdown to see why Network Load Balancer, multiple ALBs with Route 53, and client-side routing don’t meet all the requirements. 👉 Save this for any microservices and load balancing questions! #AWS #CloudComputing #ApplicationLoadBalancer #LoadBalancing #CloudCertification #SolutionsArchitect #Microservices #CloudCareer #TechLearning #CertificationPrep