The BIG-IP Administrator needs to load balance a pool of web servers. Load balancing should consider the number of connections that are active on that pool member.Which load balancing method meets this requirement? (Choose one answer)
Answer(s): A
The requirement states that load balancing decisions must be based on the number of active connections on each pool member. This directly maps to the Least Connections (member) load balancing method.According to the BIG-IP Administration: Data Plane Configuration documentation:Least Connections (member) selects the pool member with the fewest active connections at the time of the request.This method dynamically adapts to real-time traffic patterns and ensures that more heavily loaded pool members receive fewer new connections.It is especially effective for web servers where connection duration may vary and equal distribution of active sessions is desired.Why the other options are incorrect:B . Round RobinDistributes connections sequentially without considering current load or active connections.C . Ratio (member)Distributes traffic based on static ratios, not real-time connection counts.D . Ratio (node)Uses predefined ratios at the node level and does not account for active connection counts.Correct Resolution:Using Least Connections (member) ensures that new connections are directed to the pool member currently handling the fewest active connections, meeting the stated requirement.
Refer to the exhibit.A BIG-IP Administrator needs to configure health monitors for a newly configured server pool named Pool_B.Which health monitor settings will ensure that all pool members will be accurately marked as available or unavailable? (Choose one answer)
Answer(s): C
From the exhibit, the pool contains different applications on different service ports (for example, HTTP/80, FTP/21, HTTPS/443, SSH/22). To mark pool members correctly, BIG-IP must be able to verify the actual service running on each member's port.In BIG-IP Administration: Data Plane Configuration, monitor behavior is described as follows:When multiple monitors are assigned to a pool, the Availability Requirement controls how monitor results are evaluated:At least one = the pool member is marked up if any one of the assigned monitors succeeds.All = the pool member is marked up only if every assigned monitor succeeds.For pools containing members with different services/ports, using All can incorrectly mark members down because monitors intended for other services will fail on the wrong port.Why C is correct:Assigning HTTPS, HTTP, FTP, and SSH covers the actual services shown in the pool.Setting the Availability Requirement to at least one ensures that each pool member is considered available when its appropriate service monitor succeeds, without being forced to pass unrelated service monitors.Why the other options are incorrect:A / D (Availability Requirement = all): would cause members to be marked down when unrelated monitors fail (e.g., SSH monitor against an HTTP member).B (includes ICMP): ICMP can indicate the host is reachable even if the application service is down, which does not "accurately" reflect service availability.Therefore, the best choice is HTTPS, HTTP, FTP, and SSH with Availability Requirement of at least one health monitor.
All pool members are online. All other virtual server settings are at default.What might alter the load balancing behavior? (Choose one answer)
Answer(s): D
By default, BIG-IP load balancing algorithms (such as Round Robin) distribute connections evenly across all available pool members. However, persistence profiles override normal load balancing decisions by forcing subsequent connections from a client to be sent to the same pool member.According to the BIG-IP Administration: Data Plane Configuration documentation:Persistence creates a client-to-server mapping that is honored before load balancing algorithms are applied.When persistence is enabled, BIG-IP may repeatedly select the same pool member even if others are available.This directly alters load balancing behavior.Why the other options are incorrect:A . Adding a OneConnect profileOneConnect optimizes server-side TCP connections but does not change which pool member is selected.B . Enabling SNAT automapSNAT affects source address translation, not pool member selection.C . Enabling a fallback host in the HTTP profileA fallback host is only used when no pool members are available.Correct Resolution:Adding a persistence profile alters load balancing behavior by maintaining client affinity to a specific pool member.
Which persistence profile would be the most appropriate to ensure an HTTP web request connects to the same pool member? (Choose one answer)
For HTTP-based applications, cookie persistence is the most appropriate and commonly recommended persistence method.According to the BIG-IP Administration: Data Plane Configuration documentation:Cookie persistence inserts or uses an HTTP cookie to maintain session affinity.It operates at Layer 7 (HTTP) and is application-aware.It allows persistence to be maintained even when multiple clients are behind a NAT device.Why the other options are incorrect:A . Destination addressDestination address persistence is generally used for inbound traffic patterns such as firewall or proxy scenarios.B . Hash persistenceHash persistence is less granular and not HTTP-specific.C . SSL persistenceSSL persistence is typically used when SSL session IDs are reused and is less reliable than cookies for HTTP applications.Correct Resolution:Using cookie persistence ensures that HTTP web requests are consistently directed to the same pool member.
A BIG-IP Administrator needs to apply persistence to a virtual server that is configured as a Performance (Layer 4) virtual server that allows access to a secure (TLS) e-commerce website.What type of persistence profile can be used? (Choose one answer)
A Performance (Layer 4) virtual server does not inspect or process application-layer data such as HTTP headers or cookies. Therefore, only Layer 4compatible persistence methods can be used.According to the BIG-IP Administration: Data Plane Configuration documentation:Source Address Affinity persistence operates 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 for TLS-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 persistence is the appropriate choice for maintaining persistence on a Performance (Layer 4) virtual server handling TLS traffic.Below is Batch 1 (Questions 110) extracted only from your uploaded document that are directly related to BIG-IP Administration: Data Plane Configuration topics (Virtual Servers, Pools, Load Balancing, Monitors, Persistence, SNAT, Profiles).I have excluded system-only, licensing, support, hardware, HA management-only, and admin UI questions that are not Data Planefocused.Source: Your uploaded TMOS Administration v2.0 documentBATCH 1 (10 Questions)
Post your Comments and Discuss F5 F5CAB3 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the F5CAB3 content, but please register or login to continue.