An operator has created a Virtual Service with pass-through SSL using the System-L4- Application profile to load balance a secure HTTP application. The web servers only accept connections via TLS on…

Question

Options

• AConfigure "Enable SSL" in the Pool configuration.
• BConfigure "Enable SSL" in the HTTP Health Monitor.
• CChange the Application Profile in the Virtual Service to System-Secure-HTTP.
• DConfigure a Health Monitor of Type: HTTPS instead of Type: HTTP.

• A
  4% (1)
• B
  4% (1)
• C
  8% (2)
• D
  83% (20)

Explanation

Option D is correct because the HTTP Health Monitor sends plaintext health check requests to port 443, but the web servers only accept TLS-encrypted connections - causing every check to fail and all members to be marked down. Switching to an HTTPS Health Monitor tells the load balancer to perform the TLS handshake before sending the health check, matching what the servers actually expect.

Why the distractors are wrong:

• A - "Enable SSL in the Pool" addresses backend SSL re-encryption for the data path, not the health monitor; the health check will still use plain HTTP and continue to fail.
• B - A standard HTTP Health Monitor has no "Enable SSL" checkbox; SSL capability is a property of the monitor type, not a toggle within an HTTP monitor.
• C - Changing to System-Secure-HTTP converts the Virtual Service to an L7 SSL-terminating setup, fundamentally altering the architecture rather than fixing the health check mismatch.

Memory tip: Think of it as a language barrier - your health monitor has to "speak TLS" to reach servers that refuse plaintext. If the monitor type starts with "HTTP," it's always plaintext; only "HTTPS" type monitors initiate a TLS handshake. Match the monitor type to the protocol the server speaks.

No community discussion yet for this question.