A pool member responds to a request with an HTTP 500 error code. A different server in the pool needs to be selected to retry the request before sending the HTTP response back to the client. Which…

Question

Options

• AThis option is not supported.
• BConfigure HTTP Server Reselect in the Pool configuration.
• CModify the health monitor to be more aggressive with the check interval.
• DCreate a VS Policy that intercepts 500 response codes and re-plays the request to a different Pool

• A
  6% (2)
• B
  10% (3)
• C
  3% (1)
• D
  81% (25)

Explanation

Option D is correct because a Virtual Server (VS) Policy - or an iRule - operates at the HTTP application layer and can inspect response codes mid-transaction. By triggering on an HTTP 500 response, the policy can discard that response and re-forward the original request to a different pool member before the client ever sees the error, which is exactly what the question requires.

Option B is a tempting distractor because "HTTP Server Reselect" sounds relevant, but that pool feature handles connection-level failures (e.g., a TCP reset or server going down), not application-level HTTP response codes - it cannot inspect a 500 and act on it. Option C is wrong because the health monitor interval controls how often F5 checks whether a server is up; tightening it may remove a bad server from the pool faster, but it does nothing to retry an in-flight request that already got a 500. Option A is simply incorrect since a valid mechanism exists.

Memory tip: Think of it this way - health monitors and pool settings manage availability, while VS Policies and iRules manage behavior. Any time a question asks you to react to an HTTP response code and take action on a live request, the answer lives in the VS Policy/iRule layer.

No community discussion yet for this question.