F5 Networks BIG-IP Administration Support and Troubleshooting F5CAB5 Exam Questions

Answer : D

Comprehensive and Detailed Explanation From BIG-IP Administration S73upport and Troubleshooting documents: Persistence is critical for ensuring that a client's session remains with the same pool member throughout its duration. If primary persistence (like Cookie Persistence) fails---for instance, because the client has disabled cookies---load balancing will not work as expected, and the session may be broken. A 'Fallback Persistence Profile' provides a backup method75. The most common and reliable fallback method is 'Source Address Affinity'76. This method tracks the client's IP address in the BIG-IP's persistence table and ensures that any subsequent requests from that IP are routed to the same pool member, even if the primary persistence token is missing. Troubleshooting session drops often involves checking if a fallback method is configured to handle scenarios where the primary method is unsupported by the client's browser or environment. Without a fallback, the BIG-IP would revert to standard load balancing, potentially sending the client to a different server that lacks their session data.

Answer : B

In BIG-IP TMOS administration, the 'Forwarding (IP)' virtual server type is unique because it is designed to act as a high-performance router rather than a typical load balancer. Unlike a 'Standard' virtual server, which terminates a connection and directs it to a specific pool of members, a Forwarding (IP) virtual server is intended to forward packets based on the system's routing table. Consequently, the configuration for this type of virtual server explicitly removes the option to associate a default pool. If an administrator is troubleshooting a scenario where they cannot assign a pool to a virtual server, they must verify if the type was accidentally set to Forwarding (IP). This type is most commonly used for outbound internet traffic (outbound SNAT) or to allow the BIG-IP to serve as a gateway between internal subnets. Identifying this constraint is vital for troubleshooting configuration errors where an administrator expects the system to load balance traffic but finds the pool association settings are grayed out or unavailable in the Configuration Utility.

Answer : C

When traffic 'stabilizes after a few minutes' following a failover, it points to a network-level performance issue involving ARP cache on upstream routers and switches. Each BIG-IP interface has a unique hardware MAC address. During failover, the Standby device takes over the floating IP address, but the upstream switch still associates that IP with the MAC of the now-offline device. Traffic is lost until the switch learns the new MAC or its ARP entry expires. 'MAC Masquerading' solves this by creating a shared, virtual MAC address for the floating traffic group. This virtual MAC is used by whichever device is currently active. Because the MAC address for the virtual server IP never changes from the perspective of the network, the upstream devices do not need to update their ARP tables. This troubleshooting solution eliminates the delay associated with failover, providing a seamless transition and ensuring that application traffic flow is not disrupted when the BIG-IP HA state changes.

Answer : C

This log entry indicates that multiple monitors are assigned to the pool member, and the member is failing one of them.

Understanding Monitor Logic: By default, if multiple monitors are assigned to a pool or pool member without a 'Minimum To Up' (Availability Requirement) setting, the system requires all monitors to pass for the member to be marked 'Up'.

Analyzing the Log: The log clearly states: [ /Common/http: up, /Common/http2: down; ... ]. This means the standard HTTP monitor is successful, indicating the member is serving HTTP traffic, but the http2 monitor has failed.

Conclusion: Since the http monitor is 'up' but the member as a whole is 'down,' we can conclude the member is successfully responding to standard HTTP requests but not HTTP2 requests. Therefore, the member is currently only serving standard HTTP traffic.

Answer : B

The Local Traffic Manager (LTM) log file is the primary repository for all events related to load balancing objects, including virtual servers, pools, and nodes.

Monitor Logging: When a health monitor marks a pool member as 'UP' or 'DOWN,' the system generates a log entry in /var/log/ltm.

Diagnosing Flaps: To troubleshoot 'flapping' (frequent state changes), an administrator would look for messages like 01010028:3: Pool /Common/http_pool member /Common/10.10.1.1:80 monitor status down followed quickly by an 'up' status. This log provides the timestamp and the specific monitor that triggered the state change.

Answer : A

To manually verify a health monitor's 'Send String' from the BIG-IP command line, the curl utility is the preferred tool because it allows for custom header insertion.

Matching the Monitor String: The monitor string requires an HTTP/1.1 request which must include a 'Host' header. Option A correctly uses the --header (or -H) flag to pass Host: www.example.com to the specific IP and port of the pool member.

Troubleshooting Logic: If curl --header 'Host: www.example.com' 'http://10.10.3.75:8080/' returns a '200 OK' but the BIG-IP monitor still shows 'Down,' the administrator should check if the Receive String in the monitor configuration matches the output provided by curl.

Invalid Syntax: Option D is incorrect because it tries to append the hostname to the URI path, which the web server will likely reject with a '404 Not Found'. tracepath (Options B and C) is a path discovery tool similar to traceroute and cannot validate HTTP response content.

Answer : B

Based on the configuration screens provided in the exhibit, the primary reason for the connectivity failure is the disabled ARP setting on the Virtual Address.

Virtual Address ARP Setting: In a standard BIG-IP deployment, the Address Resolution Protocol (ARP) must be enabled for the Virtual Address (192.168.238.111 in this case). When enabled, the BIG-IP system responds to ARP requests from the local network gateway or adjacent devices for that specific IP address.

Exhibit Analysis: Looking at the 'Virtual Address List >> 192.168.238.111' properties section, the ARP checkbox is unselected (unchecked). Because ARP is disabled, the upstream router or client cannot resolve the MAC address for 192.168.238.111, and the traffic never reaches the BIG-IP LTM.

Availability Indicators: Note the yellow circle (status indicator) on both the Virtual Server and the Pool Members. In F5 BIG-IP, a yellow status typically indicates that the object is 'Available' (Enabled) but its monitors are not currently identifying it as 'Up' (which would be a green circle), or it is in a 'Monitor Unknown' state. However, even if a pool is available, the traffic must first reach the Virtual Server, which is prevented here by the lack of ARP.

Incorrect Options Analysis:

Priority Group Activation (A): The exhibit shows this is 'Disabled'. While this affects how load balancing picks members between groups, it does not prevent all content from being received; the system would simply use all members in the pool.

Route Advertising (C): While 'Route Advertisement' is also unchecked, this is generally only required if the BIG-IP needs to dynamically propagate the Virtual Address route via protocols like BGP or OSPF. For local segment connectivity, ARP is the fundamental requirement.