F5-CTS-LTM BIG-IP Local Traffic Manager Practice Question
Exhibit
ltm virtual /Common/vs_http {
destination /Common/10.10.10.10:80
pool /Common/pool_http
profiles {
/Common/http { }
/Common/tcp { }
}
}
ltm pool /Common/pool_http {
members {
/Common/node1:80 { }
}
}Refer to the exhibit. An administrator wants to modify this configuration to support persistence for this application. Which command should be added to the virtual server configuration?
⚠ Common exam trap
Many candidates assume persistence is enabled automatically when a pool is attached, forgetting that persistence profiles must be explicitly assigned to the virtual server configuration.
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
✓
persist /Common/cookie
To enable persistence on a Virtual Server, you must attach a persistence profile to the 'persist' attribute of the virtual server object. Simply having the pool members defined is insufficient for maintaining session affinity. This is a core concept in BIG-IP configuration; without a persistence profile, the LTM defaults to the load balancing algorithm, which may bounce users between different servers, breaking application sessions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
persist /Common/cookie
Why this is correct
Adding 'persist /Common/cookie' attaches the default cookie persistence profile to the virtual server. This ensures that the BIG-IP will insert a persistence cookie into the HTTP response, allowing subsequent requests from the same client to be consistently routed to the same backend pool member as required.
- ✗
profile /Common/cookie
Why it's wrong here
Profiles are assigned within the 'profiles' block of the virtual server configuration. Adding 'profile /Common/cookie' is syntactically incorrect for enabling persistence. Persistence profiles are defined specifically under the 'persist' setting, not within the general profiles list that includes protocol-specific settings like TCP or HTTP.
- ✗
persistence-mode cookie
Why it's wrong here
The 'persistence-mode' attribute is not a valid configuration parameter in the current BIG-IP tmsh syntax for virtual servers. Persistence must be implemented by associating a configured persistence profile object with the virtual server's 'persist' attribute, ensuring the correct profile parameters are applied during the traffic processing lifecycle.
- ✗
pool /Common/pool_http persist
Why it's wrong here
The 'persist' keyword is not a valid argument within the pool definition block. Persistence is configured at the virtual server level to define how traffic reaching that specific entry point is handled. Associating it at the pool level is not supported and would fail to produce the desired behavior.
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.