Free BIG-IP Administration Data Plane Concepts (F5CAB2) exam Practice Questions

An Application Delivery Controller (ADC) provides application traffic-management functions between clients and application servers. Two fundamental ADC capabilities represented here are SSL offloading and load balancing .

SSL offloading allows the BIG-IP system to terminate client-side SSL/TLS connections and perform the cryptographic processing that would otherwise consume application-server resources. F5 specifically describes SSL offload as the BIG-IP system performing the SSL handshake and encryption/decryption functions normally performed by the destination server. Client SSL profiles are commonly applied to virtual servers to implement this functionality.

Load balancing is another core ADC function. BIG-IP LTM uses pools and configured load-balancing algorithms to select an appropriate pool member for each connection or request. For example, with Round Robin, BIG-IP distributes incoming requests sequentially across available pool members. F5 identifies the load-balancing method as a fundamental property of a server pool.

Log collecting can occur as part of system administration and telemetry, but it is not one of the fundamental ADC functions being tested here. Screen sharing is an end-user collaboration capability and has no role in ADC traffic delivery.

Study Guide References/Topics: Application Delivery Controller Functions; SSL/TLS Offload; Virtual Servers and SSL Profiles; Pools; Load-Balancing Methods.

===============

12

In the BIG-IP system, pool selection must occur on the client-side of the connection, before the system attempts to connect to a pool 3 member. The events listed 4 are the primary entry points for making these decisions:

CLIENT_ACCEPTED (E): This is a Layer 4 event triggered when the BIG-IP accepts a TCP connection. It is the earliest point where a pool can be assigned based on the client ' s source IP address or the destination port.

CLIENT_DATA (A): This event is triggered when the system receives a " chunk " of data on the client-side. It is often used for non-HTTP protocols (like custom TCP protocols) to inspect the payload and select a pool based on its contents.

HTTP_REQUEST (C): This is a Layer 7 event. It occurs once the BIG-IP has fully parsed the HTTP headers. This is the most common event for pool selection, allowing the administrator to route traffic based on the URI, Host header, or cookies.

Events like SERVER_SELECTED or SERVER_CONNECTED occur after the load balancing decision has already been made, and HTTP_RESPONSE or SERVER_DATA occur after the server has already started communicating back, making them too late for initial pool selection.