Valid F5CAB3 Dumps shared by EduDump.com for Helping Passing F5CAB3 Exam! EduDump.com now offer the newest F5CAB3 exam dumps, the EduDump.com F5CAB3 exam questions have been updated and answers have been corrected get the newest EduDump.com F5CAB3 dumps with Test Engine here:
An LTM device has a virtual server mapped to www.f5.com with a pool assigned. The objects are defined as follows: Virtual server: Destination 192.168.245.100:443 netmask 255.255.255.0. Persistence: Source address persistence netmask 255.0.0.0. SNAT: Automap. Profiles: HTTP/TCP. How should the BIG-IP Administrator modify the persistence profile so that each unique IP address creates a persistence record?
Correct Answer: D
Source Address Affinity (Persistence) works by tracking the source IP address of incoming packets to ensure a client stays connected to the same backend server. The "netmask" setting within the persistence profile determines the "granularity" of this tracking. A netmask tells the BIG-IP how many bits of the source IP address to ignore when creating the persistence record. For example, the current setting of 255.0.0.0 (a /8 mask) means the BIG-IP only looks at the first octet of the IP; this results in all users from the same large Class A network (e.g., everyone from 10.0.0.0 to 10.255.255.255) being persisted to the exact same server, which can lead to severe load imbalance. To ensure that each unique IP address creates its own individual persistence record, the administrator must set the netmask to 255.255.255.255 (for IPv4). This is a "host mask" or /32, which instructs the BIG-IP to evaluate all 32 bits of the client's source IP address. With this setting, 10.1.1.1 and 10.1.1.2 will be treated as distinct entities and can be load balanced to different servers, each maintaining their own "stickiness". While Option A (255.255.255.0) would group users by their local subnet, only the full 255.255.255.255 mask satisfies the requirement for true unique-IP persistence. This configuration is standard for internet-facing applications where users arrive from diverse locations and the administrator wants to maintain the most granular and balanced distribution of traffic possible.