F5CAB3 BIG-IP Administration Data Plane Configuration (F5CAB3) exam Questions and Answers

Performance (Layer 4) virtual servers rely on FastL4 profiles to provide high-speed L4 processing without full proxy overhead.

Below isBATCH 2 (next 10 questions)extractedonlyfrom your uploaded document that areclearly related toBIG-IP Administration: Data Plane Configurationtopics.

❗As requested, I havestrictly excludedquestions related to:

Licensing

HA / Device Trust / Sync-only

Logging destinations

User roles

Hardware, EUD, support processes

System-only administration

Source: Your uploadedTMOS Administration v2.0document

SSH is a TCP Layer 4 protocol. Applying an HTTP profile causes BIG-IP to expect HTTP headers, breaking SSH sessions. Removing the HTTP profile allows raw TCP forwarding.

Forwarding (IP) virtual servers operate at Layer 3 and forward traffic based on routing, not pools.

In this scenario, each backendnode (server)hosts multiple services and is referenced by multiple pools and virtual servers. The goal is to ensure anequal number of total connections per backend server, regardless of how many pool members (services/ports) exist on that server.

According to theBIG-IP Administration: Data Plane Configurationdocumentation:

Least Connections (node)tracks the total number of active connections to anode across all pool members and services.

This algorithm ensures load distribution is balanced at theserver level, not just at the individual service (member) level.

It is specifically recommended when:

Multiple pool members exist on the same backend server

Multiple virtual servers reference the same backend servers

Why the other options are incorrect:

B. Predictive (member)Predictive algorithms are advanced and traffic-pattern based, but they operate at the member level and do not guarantee equal connections per server.

C. Least Connections (member)This balances connections per pool member, which can overload a server hosting multiple members while still appearing “balanced” per member.

D. Predictive (node)Although node-aware, predictive algorithms are less deterministic and not the best choice when strict equality of connections is required.

Correct Resolution:

UsingLeast Connections (node)ensures that each backend server carries an equal connection load across all services and pools.

APerformance (Layer 4)virtual server does not inspect or process application-layer data such as HTTP headers or cookies. Therefore, onlyLayer 4–compatible persistence methodscan be used.

According to theBIG-IP Administration: Data Plane Configurationdocumentation:

Source Address Affinity persistenceoperates at Layer 4 and uses the client IP address to maintain session persistence.

It is fully compatible with Performance (Layer 4) virtual servers.

It works regardless of encryption, making it suitable forTLS-secured applications.

Why the other options are incorrect:

B. Cookie persistenceRequires an HTTP profile and Layer 7 inspection, which is not supported on Performance virtual servers.

C. Microsoft RDP persistenceIs protocol-specific and not applicable to web-based TLS traffic.

D. Host persistenceRequires HTTP host header inspection, which is not available at Layer 4.

Correct Resolution:

Source Address Affinity persistenceis the appropriate choice for maintaining persistence on a Performance (Layer 4) virtual server handling TLS traffic.

Below isBatch 1 (Questions 1–10)extractedonlyfrom your uploaded document that aredirectly related toBIG-IP Administration: Data Plane Configurationtopics(Virtual Servers, Pools, Load Balancing, Monitors, Persistence, SNAT, Profiles).

I haveexcluded system-only, licensing, support, hardware, HA management-only, and admin UI questionsthat arenot Data Plane–focused.

Source: Your uploadedTMOS Administration v2.0document

✅BATCH 1 (10 Questions)

When the connection limit is reached, BIG-IP resets new connections, even if pool members are healthy.

This scenario requiresunequal load distributionbased onserver capacity. The newer servers must receive more connections than the older ones, while still dynamically accounting for active connection counts.

According toBIG-IP Administration: Data Plane Configurationdocumentation:

Weighted Least Connections (member)combines:

Connection awareness(least connections)

Administrator-defined weights (ratios)to reflect server capacity

Pool members withhigher weights receive proportionally more new connectionsthan members with lower weights, even when using the same load balancing algorithm.

WhyBis correct:

Allows assigninghigher weights to newer serversand lower weights to older servers

Ensures smarter traffic distribution based on bothcapacity and real-time load

Why the other options are incorrect:

A. Global AvailabilityUsed for disaster recovery and site failover, not intra-pool load distribution.

C. Round RobinDistributes connections evenly without considering server capacity.

D. Least Connections (member)Balances only by current connection count and does not account for differences in server performance or capacity.

Correct Resolution:

UseWeighted Least Connections (member)and assignhigher weights to newer serversso they receive more traffic while protecting older servers from overload.

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

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