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 1 Question 112 Discussion

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

An LTM Specialist is troubleshooting an issue with a new virtual server. When connecting through the virtual server, clients receive the message "Unable to connect" in the browser, although connections directly to the pool member show the application is functioning correctly. The LTM configuration is:

ltm virtual /Common/vs_https {

destination /Common/10.10.1.110:443

ip-protocol udp

mask 255.255.255.255

pool /Common/pool_https

profiles {

/Common/udp { }

}

translate-address enabled

translate-port enabled

vlans-disabled

}

ltm pool /Common/pool_https {

members {

/Common/172.16.20.1:443 {

address 172.16.20.1

}

}

}

How should the LTM Specialist resolve this issue?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

0/2000 characters
Lashawna
2 months ago
Adding an HTTP profile sounds like a solid move.
upvoted 0 times
...
Xochitl
2 months ago
Totally agree, switching to TCP would fix this!
upvoted 0 times
...
Domitila
3 months ago
Disagree, I think enabling the pool member on the right VLAN is key.
upvoted 0 times
...
Stefany
3 months ago
Wait, why is UDP even being used here? Seems off.
upvoted 0 times
...
Estrella
3 months ago
The virtual server is using UDP, but HTTP needs TCP.
upvoted 0 times
...
Marjory
3 months ago
I keep thinking about the UDP protocol in this configuration. It feels off for a web application, so option D might actually be the best way to resolve the issue.
upvoted 0 times
...
Carrol
4 months ago
I thought we learned that adding an HTTP profile could help with connection issues, but I can't recall if it applies here. Option B seems plausible, but I'm not confident.
upvoted 0 times
...
Theron
4 months ago
I'm not entirely sure, but I feel like we practiced a similar question where enabling the pool member on the correct VLAN was the key. So maybe option C could be worth considering.
upvoted 0 times
...
Ivory
4 months ago
I remember we discussed the importance of matching the protocol for virtual servers. I think option D might be the right choice since it mentions selecting the correct protocol.
upvoted 0 times
...
Veda
4 months ago
I'm a bit confused by the pool configuration. Maybe I should double-check that the pool member is enabled and accessible on the correct VLAN.
upvoted 0 times
...
Carry
4 months ago
I think the key here is to match the virtual server protocol to the client traffic. Changing the protocol to TCP or HTTP/HTTPS should resolve the "Unable to connect" error.
upvoted 0 times
...
Devorah
5 months ago
Okay, let's see here. The virtual server is set to UDP, but the clients are connecting through a browser, which typically uses HTTP/HTTPS. That could be the issue.
upvoted 0 times
...
Kimberlie
5 months ago
Hmm, this one seems tricky. I'll need to carefully review the configuration details to figure out what's going on.
upvoted 0 times
...
Denise
7 months ago
Okay, let's think this through. The clients can't connect, but the pool member is working fine. That points to a configuration issue, and the protocol mismatch is the most likely culprit. D) is the way to go, unless the LTM Specialist is feeling particularly mischievous and wants to try B) just to see what happens. *chuckles*
upvoted 0 times
Chaya
6 months ago
Let's go with D) and see if that resolves the problem.
upvoted 0 times
...
Carrol
6 months ago
Yeah, I agree. It seems like the protocol mismatch is causing the issue.
upvoted 0 times
...
Blair
7 months ago
I think D) Select the correct protocol for the virtual server is the best option here.
upvoted 0 times
...
...
Cyril
7 months ago
Ha! The LTM Specialist must have been daydreaming when they set this up. UDP for a web server? That's a bold move, Cotton. D) is the obvious choice, unless they want to make it even more interesting by trying C) and enabling the VLAN. *shakes head*
upvoted 0 times
...
Noah
7 months ago
Hmm, I'm not sure about this one. The configuration looks a bit strange, but I think the key is the protocol mismatch. D) is the way to go, unless the LTM Specialist is really feeling adventurous and wants to try B) just for fun.
upvoted 0 times
...
Jestine
7 months ago
The issue is clearly with the protocol. The virtual server is set to use UDP, but the pool member is probably expecting TCP/HTTP. D) Select the correct protocol for the virtual server seems like the right answer here.
upvoted 0 times
Rima
5 months ago
That makes sense. The protocol mismatch is likely causing the connection issue.
upvoted 0 times
...
Rima
6 months ago
D) Select the correct protocol for the virtual server.
upvoted 0 times
...
Alisha
7 months ago
Yes, D) Select the correct protocol for the virtual server should fix the issue.
upvoted 0 times
...
Ashton
7 months ago
Select the correct protocol for the virtual server.
upvoted 0 times
...
Rodolfo
7 months ago
I think the virtual server is using the wrong protocol.
upvoted 0 times
...
Fausto
7 months ago
The virtual server is using UDP, but the pool member is expecting TCP/HTTP.
upvoted 0 times
...
...
Veronica
8 months ago
Should we also consider adding an HTTP profile to the virtual server?
upvoted 0 times
...
Lavonna
8 months ago
I agree, selecting the correct protocol for the virtual server could help.
upvoted 0 times
...
James
9 months ago
I think the issue might be with the protocol.
upvoted 0 times
...

Save Cancel