F5CAB3 Exam Dumps - BIG-IP Administration Data Plane Configuration (F5CAB3) exam

Application-specific health checks must validate application responses, which requires HTTP monitors with custom send/receive strings.

When many users share one source IP, source-address persistence fails. Cookie persistence uniquely identifies clients at Layer 7.

When multiple hostnames resolve to the same IP address and encrypted communication is required, the BIG-IP must be able to present the correct SSL certificate based on the hostname requested by the client. This is accomplished using Server Name Indication (SNI).

According to BIG-IP Administration: Data Plane Configuration documentation:

SNI is a client-side TLS extension, where the client includes the requested hostname during the SSL handshake.

BIG-IP evaluates this hostname using the Client SSL profile, not the Server SSL profile.

The “Server Name” setting in the Client SSL profile enables BIG-IP to select the appropriate SSL certificate for the requested hostname.

Why option C is correct:

Client SSL profile handles inbound (client-side) encryption.

Server Name enables SNI-based certificate selection when multiple DNS names share the same virtual server IP.

Why the other options are incorrect:

A. Client SSL, Client NameThere is no Client SSL setting called Client Name for SNI certificate selection.

B. Server SSL, Server NameServer SSL is used for encryption between BIG-IP and backend servers, not for client-side hostname identification.

D. Server SSL, Client NameServer SSL does not process client-requested hostnames during TLS negotiation.

Correct Resolution:

Configure a Client SSL profile and enable the Server Name (SNI) setting to support multiple encrypted hostnames on the same virtual server IP.

Using “at least one” ensures each member is marked up based on its relevant service monitor.

SSH is a TCP-based service. A TCP monitor validates service availability without requiring application-layer inspection.

WAN TCP profiles are optimized for high latency and packet loss typical of Internet clients, while LAN profiles are ideal for backend servers.

The BIG-IP system uses a centralized management framework to ensure that all devices within a Sync-Failover group share a consistent configuration. When an administrator makes a change on any member of the group—whether it is the active or the standby device—the system detects a " ConfigSync " mismatch. The " Device Management > > Overview " screen tracks these changes by comparing the commit ID and timestamps of the configurations across all peers.

If a change is made on the standby member, that device now possesses a more recent configuration than the other members of the group. Consequently, the BIG-IP GUI will display a status of " Changes Pending " and suggest a Recommended Action to resolve the discrepancy. In this scenario, the correct action is to Synchronize the standby member configuration to the group. This push operation will copy the updated configuration from the standby device to the active device (and any other peers), bringing the entire cluster back into a " In Sync " status. It is important to note that BIG-IP allows bi-directional synchronization; you do not have to be on the active device to push a configuration. However, administrators must be cautious: choosing Option C (Synchronizing the active member to the group) would overwrite the changes just made on the standby device with the older configuration from the active device, effectively reverting the changes. The Recommended Action always points toward the direction that propagates the most recent change to the rest of the group.

With manual resume enabled, BIG-IP does not automatically return a pool member to service after recovery. The member remains offline until manually re-enabled.