F5 Updated F5CAB2 Exam Questions and Answers by anabia

The F5 BIG-IP upgrade process for HA pairs requires a specific " staggered " approach to maintain uptime.

Version Mismatch: When one unit is upgraded to a newer version of TMOS (e.g., from 15.1 to 16.1), it enters a 26 " Version Mismatch " 27 state with its peer.

Configuration Sync: Because the configuration schemas between different versions are often incompatible, ConfigSync should not be performed . Attempting to sync a newer configuration to an older system (or vice-versa) can cause configuration corruption or system instability.

Failover Capability: Generally, a pair with a version mismatch can still fail over to ensure traffic continuity during the upgrade window, but administrative changes and syncs must be paused until both units are on the same version.

Understanding the default behavior of a Standard Virtual Server regarding address and port translation is fundamental to BIG-IP administration.

Source Address Translation (SNAT): By default, the BIG-IP system does not perform Source Address Translation (SNAT). This means that the packet ' s source IP address (the Client IP ) remains preserved as it passes through the BIG-IP to the pool member. This is critical for backend servers to identify the original client for logging and security purposes. Therefore, the client IP address is unchanged between the client-side and server-side connections.

Destination Address Translation (DAT): By default, a Standard Virtual Server always performs Destination Address Translation. The BIG-IP system changes the destination IP from the Virtual Server ' s IP address to the IP address of the specific Pool Member selected by the load balancing algorithm. Consequently, the server-side destination IP is different from the client-side destination IP.

Port Translation: By default, Port Translation is enabled. If a Virtual Server is listening on port 80 and the selected pool member is configured for port 8080, the BIG-IP will translate the destination port. Even if the ports happen to be the same, the setting allows for change, whereas the default SNAT setting (None) ensures the client IP remains static.

Redundant BIG-IP systems (HA pairs) must maintain constant communication to monitor the health of the peer and synchr 15 onize states. 16

Heartbeats: By default, even with a serial cable, th 17 e BIG-IP systems exchange " heartbeat " packets over the network to determine if the peer is still alive.

Network Failover: This involves the exchange of UDP packets (typically on port 1026) at regular intervals.

Device Service Clustering (DSC): Modern BIG-IP versions use the Central Management (cm) infrastructure to communicate configuration status and sync status constantly.

Clarification on others: Port lockdown does affect HA communication if misconfigured (A is false). Mirroring uses separate channels (B is false). Mirroring is never sent over the serial cable because it requires high bandwidth (D is false).

The BIG-IP processing flow follows a specific sequence of events as a packet moves through the system.

TCP Handshake: Before any application-layer data (like HTTP) can be processed, a TCP connection must be established.

The First Event: The very first event triggered when a client completes the 3-way handshake with the virtual server is CLIENT_ACCEPTED .

Profile Influence: Even if an HTTP profile is attached, the system must first " accept " the connection at the protocol level. HTTP_REQUEST only triggers after the client sends data that the BIG-IP recognizes as a valid HTTP request. If a client connects but never sends a request, CLIENT_ACCEPTED will have fired, but HTTP_REQUEST will not.