New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

F5 Networks 301b Exam - Topic 2 Question 93 Discussion

Actual exam question for F5 Networks's 301b exam
Question #: 93
Topic #: 2
[All 301b Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

0/2000 characters
Viva
3 months ago
B sounds interesting, but does 'match across virtual servers' really work?
upvoted 0 times
...
Marleen
3 months ago
I like A, but not sure about disabling port translation.
upvoted 0 times
...
Vincent
3 months ago
Wait, why do we need two separate pools for HTTP and HTTPS?
upvoted 0 times
...
Laquita
4 months ago
I disagree, I think D is more straightforward.
upvoted 0 times
...
Marvel
4 months ago
Option C seems like the best choice for session persistence.
upvoted 0 times
...
Amie
4 months ago
I'm leaning towards option A since it simplifies the configuration by using a single pool, but I'm not entirely confident about the port translation part.
upvoted 0 times
...
Naomi
4 months ago
I practiced a similar question where we had to set up pools for different protocols, but I can't recall if we needed to create separate pools for HTTP and HTTPS like in option D.
upvoted 0 times
...
Gilbert
4 months ago
I think option C sounds familiar because it mentions "match across services," which seems like it could help with directing clients correctly.
upvoted 0 times
...
Reena
5 months ago
I remember something about persistence profiles being crucial for maintaining session consistency, but I'm not sure which one to use here.
upvoted 0 times
...
Jani
5 months ago
I'm feeling pretty confident about this one. Option C looks like the best solution to me - it covers all the requirements and uses the appropriate persistence settings.
upvoted 0 times
...
Lavonne
5 months ago
Okay, I think I've got a good handle on this. The key is to create separate pools for the HTTP and HTTPS traffic, and then use a persistence profile to keep clients on the same node for the duration of their session.
upvoted 0 times
...
Kimberlie
5 months ago
Hmm, I'm a bit confused about the "match across virtual servers" part. Does that mean I need to apply the persistence profile to both virtual servers, or just one of them?
upvoted 0 times
...
Geoffrey
5 months ago
This looks like a pretty straightforward configuration task, but I want to make sure I understand the requirements correctly before I start.
upvoted 0 times
...
Gilberto
5 months ago
Hmm, I'm a bit unsure about this one. I'll need to review my notes on the VMware View architecture to figure out which component is the least available.
upvoted 0 times
...
Alpha
5 months ago
This is a tricky one. I'm leaning towards the bottom-up approach, since the business analyst will likely get the most detailed and accurate information from the people actually performing the process. But I could see an argument for a top-down view as well. Guess I'll have to weigh the pros and cons.
upvoted 0 times
...
Vivienne
10 months ago
Ah, the joys of load balancing. I bet the application admins are just sitting back, sipping their coffee, and enjoying the show.
upvoted 0 times
Tonja
9 months ago
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 Assign the persistence profile to vs_http
upvoted 0 times
...
Linsey
9 months ago
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
upvoted 0 times
...
Ressie
9 months ago
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
upvoted 0 times
...
...
Jani
10 months ago
Option D is looking good, but that SSL persistence profile just for the HTTP virtual server seems a bit odd. Why not apply it to both?
upvoted 0 times
Stephane
9 months ago
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
upvoted 0 times
...
Ethan
9 months ago
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.
upvoted 0 times
...
Marilynn
9 months ago
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
upvoted 0 times
...
...
Ryan
10 months ago
Ha! Option A is a classic case of 'set it and forget it'. Disable port translation for both HTTP and HTTPS? That's just asking for trouble down the line.
upvoted 0 times
Nichelle
9 months ago
User 3
upvoted 0 times
...
Clarinda
9 months ago
User 2
upvoted 0 times
...
Jerlene
9 months ago
User 2
upvoted 0 times
...
Quentin
9 months ago
User 1
upvoted 0 times
...
Devorah
10 months ago
User 1
upvoted 0 times
...
...
Keshia
10 months ago
Hmm, I'm not sure about option B. Disabling port translation for HTTPS seems risky, and I'm not convinced the SSL persistence profile will work the way they want across both virtual servers.
upvoted 0 times
...
Georgeanna
10 months ago
Option C looks like the way to go. Separate pools for HTTP and HTTPS, and a persistence profile that matches across services to keep the client on the same node. Simple and straightforward.
upvoted 0 times
...
Rickie
11 months ago
I'm not sure, but option D also looks like it could work.
upvoted 0 times
...
Roxanne
11 months ago
I agree with Isadora, option C seems to be the best choice.
upvoted 0 times
...
Isadora
11 months ago
I think option C is the correct one.
upvoted 0 times
...

Save Cancel