F5 F5CAB5 Exam
BIG-IP Administration Support and
Troubleshooting
https://www.passquestion.com/f5cab5.html
35% OFF on All, Including F5CAB5 Questions and Answers
Pass F5CAB5 Exam with PassQuestion F5CAB5 questions and
answers in the first attempt.
https://www.passquestion.com/
1/9
, 1.A BIG-IP Administrator needs to determine why only one pool member is showing connections from the
virtual server, resulting in uneven load balancing.
What two reasons would cause uneven load balancing? (Choose two answers)
A. The virtual server is marked down.
B. Monitors have marked down multiple pool members.
C. The pool has a persistence profile configured.
D. All pool members are marked down.
Answer: B, C
Explanation:
Uneven load balancing on a BIG-IP system typically occurs when traffic is not distributed evenly across all
available pool members. One common reason is that monitors have marked down multiple pool members
(Option B). When health monitors fail for specific pool members, BIG-IP automatically removes those
members from load-balancing decisions. As a result, traffic is sent only to the remaining healthy member,
creating the appearance that load balancing is not functioning correctly.
This behavior is expected and aligns with BIG-IP’s design to ensure traffic is sent only to healthy
resources.
Another frequent cause is the presence of a persistence profile on the pool or virtual server (Option C).
Persistence (such as source address or cookie persistence) forces subsequent client connections to be
sent to the same pool member for session continuity. While persistence is critical for certain applications,
it can override the load-balancing algorithm and cause most or all traffic to be directed to a single pool
member, especially during low traffic volumes or testing scenarios.
The other options are incorrect because avirtual server marked down (Option A) would not pass traffic at
all, andall pool members marked down (Option D) would result in no connections rather than uneven
distribution. This analysis follows standard BIG-IP troubleshooting methodology using pool status, monitor
results, and persistence configuration review.
2.A BIG-IP Administrator plans to upgrade a BIG-IP device to the latest TMOS version.
Which two tools could the administrator leverage to verify known issues for the target versions? (Choose
two answers)
A. F5 End User Diagnostics (EUD)
B. F5 Bug Tracker
C. F5 University
D. F5 iHealth
E. F5 Downloads
Answer: B, D
Explanation:
Before upgrading a BIG-IP system to a newer TMOS version, it is critical to review known issues to
avoid introducing instability or regressions.F5 Bug Tracker (Option B) is a primary resource for this
purpose. It allows administrators to search for documented software defects by TMOS version, module,
symptom, or bug ID. Using Bug Tracker, an administrator can identify unresolved issues, fixed bugs, and
behavioral changes that may affect their specific deployment, such as traffic handling, high availability, or
module-specific functionality. This directly supports proactive troubleshooting and informed upgrade
planning.
F5 iHealth (Option D) is another essential tool used during upgrade preparation. iHealth analyzes
2/9
BIG-IP Administration Support and
Troubleshooting
https://www.passquestion.com/f5cab5.html
35% OFF on All, Including F5CAB5 Questions and Answers
Pass F5CAB5 Exam with PassQuestion F5CAB5 questions and
answers in the first attempt.
https://www.passquestion.com/
1/9
, 1.A BIG-IP Administrator needs to determine why only one pool member is showing connections from the
virtual server, resulting in uneven load balancing.
What two reasons would cause uneven load balancing? (Choose two answers)
A. The virtual server is marked down.
B. Monitors have marked down multiple pool members.
C. The pool has a persistence profile configured.
D. All pool members are marked down.
Answer: B, C
Explanation:
Uneven load balancing on a BIG-IP system typically occurs when traffic is not distributed evenly across all
available pool members. One common reason is that monitors have marked down multiple pool members
(Option B). When health monitors fail for specific pool members, BIG-IP automatically removes those
members from load-balancing decisions. As a result, traffic is sent only to the remaining healthy member,
creating the appearance that load balancing is not functioning correctly.
This behavior is expected and aligns with BIG-IP’s design to ensure traffic is sent only to healthy
resources.
Another frequent cause is the presence of a persistence profile on the pool or virtual server (Option C).
Persistence (such as source address or cookie persistence) forces subsequent client connections to be
sent to the same pool member for session continuity. While persistence is critical for certain applications,
it can override the load-balancing algorithm and cause most or all traffic to be directed to a single pool
member, especially during low traffic volumes or testing scenarios.
The other options are incorrect because avirtual server marked down (Option A) would not pass traffic at
all, andall pool members marked down (Option D) would result in no connections rather than uneven
distribution. This analysis follows standard BIG-IP troubleshooting methodology using pool status, monitor
results, and persistence configuration review.
2.A BIG-IP Administrator plans to upgrade a BIG-IP device to the latest TMOS version.
Which two tools could the administrator leverage to verify known issues for the target versions? (Choose
two answers)
A. F5 End User Diagnostics (EUD)
B. F5 Bug Tracker
C. F5 University
D. F5 iHealth
E. F5 Downloads
Answer: B, D
Explanation:
Before upgrading a BIG-IP system to a newer TMOS version, it is critical to review known issues to
avoid introducing instability or regressions.F5 Bug Tracker (Option B) is a primary resource for this
purpose. It allows administrators to search for documented software defects by TMOS version, module,
symptom, or bug ID. Using Bug Tracker, an administrator can identify unresolved issues, fixed bugs, and
behavioral changes that may affect their specific deployment, such as traffic handling, high availability, or
module-specific functionality. This directly supports proactive troubleshooting and informed upgrade
planning.
F5 iHealth (Option D) is another essential tool used during upgrade preparation. iHealth analyzes
2/9
