301B practice question 17 of 30

-- Exhibit – -- Exhibit -- Refer to the exhibit. An LTM Specialist has created a virtual server to load balance traffic to a pool of HTTPS servers…

Full set: 210 questions
-- Exhibit – -- Exhibit -- Refer to the exhibit. An LTM Specialist has created a virtual server to load balance traffic to a pool of HTTPS servers. The servers use client certificates for user authentication. The virtual server has clientssl, serverssl, and http profiles enabled. Clients are unable to connect to the application through the virtual server. Clients are able to connect to the application servers directly. What is the root cause of the problem?
Answer options
A: The application server does NOT support 2048-bit keys.
B: The clientssl profile is NOT set to require a client certificate.
C: The LTM device does NOT trust the issuing CA of the client certificate.
D: The application server does NOT see the client certificate due to SSL offload. Correct answer
Correct Answer:
D. The application server does NOT see the client certificate due to SSL offload.
Explanation

The configuration described is SSL Bridging (or SSL re-encryption), where the LTM terminates the client-side SSL connection and establishes a new, separate SSL connection to the backend server. In this model, the LTM acts as the SSL client for the server-side connection. The original client certificate presented by the user to the LTM is not automatically forwarded in the new SSL handshake with the server. Because the application server requires a client certificate for authentication and does not receive one from the LTM, it rejects the connection. The user can connect directly because their browser presents the certificate directly to the server.

Why Incorrect

A. The application server does NOT support 2048-bit keys. This is a possible but less specific cause. The problem statement highlights client certificate authentication as the key requirement that is failing.
B. The clientssl profile is NOT set to require a client certificate. This setting controls whether the LTM authenticates the client; it does not affect the server-side connection where the failure occurs.
C. The LTM device does NOT trust the issuing CA of the client certificate. This would cause the initial client-to-LTM handshake to fail, but the problem lies in the LTM-to-server connection.

References

- F5 BIG-IP System: SSL Administration, Chapter: About SSL Profiles, Section: Client and Server SSL profile overview. This section describes the two separate SSL connections (client-to-LTM and LTM-to-server) created during SSL bridging.

- F5 Knowledge Base, K14522: Configuring the BIG-IP LTM to perform client certificate authentication. This article details how the LTM terminates the client SSL session, which is the underlying mechanism causing the server to not see the certificate.

Scroll to Top