F5-CTS-LTM BIG-IP Local Traffic Manager Practice Question
Exhibit
ltm persistence source-addr my_source_persistence {
app-service none
match-across-pools disabled
match-across-services disabled
match-across-virtuals disabled
timeout 180
}Refer to the exhibit. A user connects to Virtual Server A, which uses the 'my_source_persistence' profile. The user is then redirected to Virtual Server B. Given the configuration, will the persistence record be honored?
⚠ Common exam trap
Candidates often assume persistence is global by default, failing to check the 'match-across-virtuals' setting, which is disabled by default and prevents persistence sharing between different virtual servers.
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
✓
No, because match-across-virtuals is disabled.
The persistence profile has 'match-across-virtuals' set to 'disabled'. Because this attribute is disabled, the BIG-IP will not share persistence information between Virtual Server A and Virtual Server B. When the user lands on Virtual Server B, the system will initiate a new load balancing decision instead of respecting the persistence session established on the first virtual server, which is crucial for managing multi-virtual server architectures.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Yes, because the timeout is set to 180 seconds.
Why it's wrong here
The timeout setting defines the lifespan of the persistence record, not the scope of its application. Even if the record is still active within the 180-second window, the 'match-across-virtuals' setting is the primary directive that governs whether that record is eligible to be applied to a different virtual server.
- ✓
No, because match-across-virtuals is disabled.
Why this is correct
With 'match-across-virtuals' explicitly disabled, the BIG-IP restricts the scope of the source address persistence record to only the specific virtual server that created it. Consequently, any requests arriving at a different virtual server will be treated as a new session, ignoring the persistence state established on the previous virtual server.
- ✗
Yes, because source-addr persistence is global.
Why it's wrong here
Source address persistence is not global by default. Its scope is strictly controlled by the settings within the persistence profile. Without enabling cross-virtual matching, the system maintains separate persistence tables for each virtual server, preventing the sharing of session state between different virtual server instances regardless of the client IP.
- ✗
No, because the timeout must be set to indefinite.
Why it's wrong here
The duration of the persistence record has no impact on whether it can be shared across virtual servers. Persistence duration is purely for determining when an entry should expire. The capability to share state between virtual servers is exclusively defined by the 'match-across-virtuals' configuration attribute within the persistence profile.
About these practice questions
Courseiva writes every F5-CTS-LTM question from scratch — 119 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.