An application owner has configured an HTTP Health Monitor for a Virtual Service with the close\ Which additional configuration is required for this Health Monitor to function correctly?

Question

Options

• AThe option "Rewrite Host Header to Server Name" must be enabled in the Pool.
• BThe option "Use Exact Request" must be enabled in the Health Monitor.
• CThe option "Is Federated" must be enabled in the Health Monitor.
• DThe option "Use HTTP/1.1" must be enabled in the Health Monitor.

• A
  3% (1)
• B
  88% (28)
• C
  9% (3)

Explanation

Option B is correct because when a custom HTTP request string is defined in an Avi/NSX ALB Health Monitor, the system may automatically append or modify the request by default. Enabling "Use Exact Request" forces the Health Monitor to send precisely the configured request string without any automatic modifications - this is essential for the monitor to behave as intended.

Why the distractors are wrong:

• A - "Rewrite Host Header to Server Name" is a Pool-level setting that affects how backend servers receive the Host header from client traffic, not how a Health Monitor sends its probe request.
• C - "Is Federated" controls whether the Health Monitor configuration is synchronized across a multi-site/federated deployment; it has no bearing on whether the monitor can send requests correctly.
• D - "Use HTTP/1.1" influences the protocol version used in the probe, but it is not the required setting in this specific scenario - the monitor can function on HTTP/1.0 by default.

Memory tip: Think of "Use Exact Request" as a "send it as written" switch - whenever you craft a custom HTTP health check request and the monitor isn't behaving as configured, ask yourself: "Is it sending my request exactly?" If not, that's your missing toggle.

No community discussion yet for this question.