F5 BIG-IP LTM Specialist: Maintain and Troubleshoot — Question 83
An LTM Specialist has been asked to configure a virtual server to distribute connections between a pool of two application servers with addresses 172.16.20.1 and 172.16.20.2. The application servers are listening on TCP ports 80 and 443. The application administrators have asked that clients be directed to the same node for both HTTP and HTTPS requests within the same session.
Virtual servers vs_http and vs_https have been created, listening on 1.2.3.100:80 and 1.2.3.100:443, respectively.
Which configuration option will result in the desired behavior?
Answer options
- A. Create pool app_pool with members 172.16.20.1:any and 172.16.20.2:any Assign app_pool as the default pool for both vs_http and vs_https Disable port translation for vs_http and vs_https
- B. Create pool http_pool with members 172.16.20.1:80 and 172.16.20.2:80 Assign pool http_pool as the default pool for both vs_https and vs_https Disable port translation for vs_https Create an SSL persistence profile with "match across virtual servers" enabled Assign the persistence profile to vs_http.
- C. Create pool http_pool with members 172.16.20.1:80 and 172.16.20.2:80 Create pool https_pool with members 172.16.20.1:443 and 172.16.20.2:443 Assign http_pool as the default pool for vs_http Assign https_pool as the default pool for vs_https Create a source address persistence profile with "match across services" enabled Assign the persistence profile to vs_http and vs_https
- D. Create pool http_pool with members 172.16.20.1:80 and 172.16.20.2:80 Create pool https_pool with members 172.16.20.1:443 and 172.16.20.2:443 Assign http_pool as the default pool for vs_http Assign https_pool as the default pool for vs_https Create an SSL persistence profile with "match across virtual servers" enabled
Correct answer: C
Explanation
Option C is the correct choice as it creates separate pools for HTTP and HTTPS, ensuring that the correct port is used for each request type. It also utilizes a source address persistence profile with 'match across services' enabled, which maintains client sessions on the same application server for both protocols. The other options do not effectively address session persistence across both HTTP and HTTPS or use incorrect configurations.