Challenge 1: Choosing lbmethod for Widely Varying Response Times — Solution Walkthrough The config: BalancerMember "http://10.0.0.11:5000" BalancerMember "http://10.0.0.12:5000" ProxySet lbmethod=bybusyness Why bybusyness fits this scenario: byrequests (the default) rotates requests round-robin regardless of how long each member is currently taking to respond -- it would happily keep sending new requests to a member that's already stuck handling one very slow request, purely because it's "its turn" in the rotation. bytraffic balances based on bytes transferred, which doesn't address slow-but-small responses at all -- a request can be slow without being large. bybusyness specifically tracks how many requests each member currently has in flight and routes new requests to whichever member has the fewest active requests right now. When response times vary widely between requests, this is exactly the signal that matters: a member stuck on one slow request naturally stops receiving new ones, while a member that's free keeps getting routed to, without needing to know anything about request size or a fixed rotation order. WHY THIS WORKS AS AN ANSWER ------------------------------ This exercise checks that the reader can match the actual bottleneck described (uneven response time, not uneven payload size) to the lbmethod specifically designed to react to that signal, rather than defaulting to byrequests or picking bytraffic by pattern-matching on "load balancing = probably about traffic."