F5-CTS-LTM BIG-IP Local Traffic Manager Practice Question
When troubleshooting a persistent connection issue, which LTM feature allows you to view active persistence entries?
⚠ Common exam trap
Many test-takers confuse configuration viewing commands in tmsh with runtime operational troubleshooting commands, mistakenly checking pool status instead of querying the actual persistence table records.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Traffic Management Shell (tmsh) persistence table
The persistence table contains a real-time mapping of client sessions to specific pool members. Viewing this table is the most effective way to determine if persistence is working correctly. It is a fundamental troubleshooting step for LTM specialists, as it confirms whether client traffic is being directed to the intended server or if a conflict in the persistence configuration is causing sessions to be misrouted.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Traffic Management Shell (tmsh) persistence table
Why this is correct
The command 'show ltm persistence persist-records' provides a detailed view of current entries in the persistence table. This allows administrators to verify which clients are currently pinned to which backend servers, which is essential for diagnosing issues where session stickiness is failing to perform as expected.
- ✗
Configuration Utility Dashboard
Why it's wrong here
While the GUI provides basic statistics, it does not offer a granular, real-time view of every individual persistence record in the same way the CLI does. For detailed troubleshooting of individual session mappings, direct command-line access via the persistence table is the standard and most reliable method.
- ✗
Virtual Server Statistics
Why it's wrong here
Virtual Server statistics show global traffic counts, such as hits, bytes in, and bytes out. They do not contain any information about the persistence mappings for individual clients. These stats are useful for identifying overall load, but they are not helpful for debugging specific persistence-related failures.
- ✗
Log files in /var/log/ltm
Why it's wrong here
The /var/log/ltm file records system-level events and errors, but it does not track individual persistence mappings. Persistence is a dynamic, memory-based operation handled by TMM, and its current state is stored in the persistence table, not in persistent log files on the filesystem.
About these practice questions
This F5-CTS-LTM question is part of Courseiva's 119-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official F5 exam blueprint
This F5-CTS-LTM practice question is part of Courseiva's free F5 certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the F5-CTS-LTM exam.