The application team has requested that traffic destined for /downloads be sent to a different set of back-end servers than the rest of the traffic. Which feature should be used to accomplish this…

Question

Options

• ARedirect action in an HTTP Request policy
• BPool Group priority
• CRedirect to HTTPS action in an HTTP Security policy
• DContent switch action in an HTTP Request policy

• A
  5% (3)
• B
  14% (8)
• C
  4% (2)
• D
  77% (44)

Explanation

Content switching is the mechanism designed specifically to route requests to different backend server pools based on attributes of the HTTP request - in this case, the URL path /downloads. An HTTP Request policy with a content switch action lets the load balancer inspect the incoming URL and send matching traffic to an alternate pool, while all other traffic continues to the default pool.

Why the distractors are wrong:

• A (Redirect action): A redirect sends an HTTP 301/302 response back to the client, telling the browser to go to a new URL - it does not change which backend server handles the request.
• B (Pool Group priority): Pool Group priority controls failover order - if the primary pool fails, traffic moves to a lower-priority pool. It has nothing to do with path-based routing.
• C (Redirect to HTTPS): This is a security feature that forces HTTP traffic to upgrade to HTTPS; it does not influence which backend pool receives the request.

Memory tip: Associate "content switch" with switching destinations based on request content (URL, headers, etc.). If the question mentions routing specific paths or URLs to different server groups, the answer will always involve a content switch - not a redirect (which moves the client) and not priority (which handles failures).

No community discussion yet for this question.