Which persistence method is most appropriate for an HTTP application that needs to maintain session state across multiple requests from the same user, even if the user's IP address changes?

Destination address persistence

A company has a BIG-IP load balancing a database application. The pool has two members, both with the same priority. The administrator has enabled source address persistence with a timeout of 30 minutes. Users are reporting that after a failover of one member, some users are still being sent to the failed member and experiencing errors. What is the most likely cause?

The persistence timeout is still valid, and the BIG-IP is sending persisted clients to the failed member until the timeout expires

The load balancing method is set to Ratio, overriding persistence

The priority group activation is preventing traffic from going to the healthy member

The monitor is not detecting the failure quickly enough

A company runs a web application on a pair of BIG-IP load-balanced servers. Users report that after logging in, all subsequent requests during their session go to the same server, even when the other server is healthy and idle. The load balancing method is set to Round Robin. The administrator wants to confirm this behavior is intentional and not a misconfiguration. Which configuration should the administrator check first?

The monitor status of both pool members

The persistence profile assigned to the virtual server

The connection limit on the idle server

The priority group activation setting on the pool

A company uses a BIG-IP to load balance an HTTPS application. The virtual server uses SSL session ID persistence. Users are reporting that they are being sent to different servers after a browser restart, causing them to have to log in again. What is the most likely reason for this behavior?

The pool members are failing over frequently

SSL session ID persistence does not survive browser restarts because the SSL session is renegotiated

The SSL session ID persistence profile is set to 'Rewrite' mode, which does not preserve the session ID

The load balancing method is set to Least Connections, overriding the persistence profile

An administrator notices that traffic is being sent to lower-priority pool members even though all higher-priority members are healthy. What is the most likely cause?

The lower-priority members have a higher connection limit

The persistence profile is set to source address

The load balancing method is set to round-robin

The priority group activation threshold is set to a value greater than the number of available higher-priority members

F5Certified Administrator, BIG-IP

Domain 3Objective 1

Consider Persistence, Priority Group Activation, Rate/connection Limits F5CAB5 Practice Questions (Page 1)

Part of the Identify the reason load balancing is not working as expected domain, which makes up ~12% of our current practice bank. F5 does not publish an official question count, but from its 30-minute exam (~10–20 total, ~1–2 in this domain), expect 1–1 from this objective — we provide 16 practice questions to prepare you well beyond it. (estimate)

16questions here

4free pages

3concepts

Questions 1–5

1foundation · easy
Which persistence method is most appropriate for an HTTP application that needs to maintain session state across multiple requests from the same user, even if the user's IP address changes?
Select an answer first
2expert · hard
A company has a BIG-IP load balancing a database application. The pool has two members, both with the same priority. The administrator has enabled source address persistence with a timeout of 30 minutes. Users are reporting that after a failover of one member, some users are still being sent to the failed member and experiencing errors. What is the most likely cause?
Select an answer first
3application · medium
A company runs a web application on a pair of BIG-IP load-balanced servers. Users report that after logging in, all subsequent requests during their session go to the same server, even when the other server is healthy and idle. The load balancing method is set to Round Robin. The administrator wants to confirm this behavior is intentional and not a misconfiguration. Which configuration should the administrator check first?
Select an answer first
4application · medium
A company uses a BIG-IP to load balance an HTTPS application. The virtual server uses SSL session ID persistence. Users are reporting that they are being sent to different servers after a browser restart, causing them to have to log in again. What is the most likely reason for this behavior?
Select an answer first
5foundation · easy
An administrator notices that traffic is being sent to lower-priority pool members even though all higher-priority members are healthy. What is the most likely cause?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to F5CAB5

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by F5. “F5CAB5” is a trademark of its owner, used for identification only.

Consider Persistence, Priority Group Activation, Rate/connection Limits F5CAB5 Practice Questions (Page 1)

Questions 1–5

Which persistence method is most appropriate for an HTTP application that needs to maintain session state across multiple requests from the same user, even if the user's IP address changes?

A company uses a BIG-IP to load balance an HTTPS application. The virtual server uses SSL session ID persistence. Users are reporting that they are being sent to different servers after a browser restart, causing them to have to log in again. What is the most likely reason for this behavior?

An administrator notices that traffic is being sent to lower-priority pool members even though all higher-priority members are healthy. What is the most likely cause?

Keep studying — Identify the reason load balancing is not working as expected