Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

F5 Networks F5CAB3 Exam - Topic 2 Question 4 Discussion

A BIG-IP Administrator creates a new Virtual Server to load balance SSH traffic. Users are unable to log on to the servers.What should the BIG-IP Administrator do to resolve the issue?
B) Set HTTP Profile to None
A) Set Protocol to UDP
C) Set Source Address to 10.1.1.2
D) Set Destination Address/Mask to 0.0.0.0/0

F5 Networks F5CAB3 Exam - Topic 2 Question 4 Discussion

Actual exam question for F5 Networks's F5CAB3 exam
Question #: 4
Topic #: 2
[All F5CAB3 Questions]

A BIG-IP Administrator creates a new Virtual Server to load balance SSH traffic. Users are unable to log on to the servers.

What should the BIG-IP Administrator do to resolve the issue?

Show Suggested Answer Hide Answer
Suggested Answer: B

SSH is a TCP Layer 4 protocol. Applying an HTTP profile causes BIG-IP to expect HTTP headers, breaking SSH sessions. Removing the HTTP profile allows raw TCP forwarding.


by Tatum at Jan 26, 2026, 06:21 AM

Limited Time Offer

25%

Off

Get Premium F5CAB3 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Moon
26 days ago
Setting HTTP Profile to None? That doesn't make sense for SSH.
upvoted 0 times
...
Rodolfo
1 month ago
Wait, are we sure about that? 0.0.0.0/0 seems risky.
upvoted 0 times
...
Gianna
1 month ago
I think D is the way to go for broad access.
upvoted 0 times
...
Kirk
1 month ago
Definitely need to set the right protocol!
upvoted 0 times
...
Naomi
2 months ago
SSH uses TCP, not UDP.
upvoted 0 times
...
Jill
2 months ago
I'd go with the classic "turn it off and on again" approach. Works every time!
upvoted 0 times
...
Zana
2 months ago
I bet the BIG-IP Admin is scratching their head right now, wondering how they managed to mess this up.
upvoted 0 times
...
Shay
2 months ago
0.0.0.0/0? That's a bit too broad, don't you think?
upvoted 0 times
...
Tamie
2 months ago
Setting the HTTP profile to None? Hmm, I don't think that's the right move here.
upvoted 0 times
...
Eden
2 months ago
Definitely not UDP, that's for sure!
upvoted 0 times
...
Felix
3 months ago
I recall that setting the destination address to 0.0.0.0/0 could allow traffic from anywhere, which might help with connectivity issues.
upvoted 0 times
...
Eric
3 months ago
I’m not sure about the source address option, but I think it might be more about the destination settings for SSH traffic.
upvoted 0 times
...
Dell
4 months ago
I feel like we had a similar question in practice about setting profiles. If it's SSH, I don't think an HTTP profile would even apply here.
upvoted 0 times
...
Shawna
4 months ago
I remember that SSH uses TCP, so I think setting the protocol to UDP is definitely not the right choice.
upvoted 0 times
...
Yesenia
4 months ago
Ah, I see what's going on here. The key is that the question is about SSH traffic, not HTTP. So the answer is definitely not B) Set HTTP Profile to None. I think the best option is A) Set Protocol to UDP, since that would ensure the BIG-IP is handling the SSH traffic correctly.
upvoted 0 times
...
Jeannetta
4 months ago
I'm pretty sure the answer is not C) Set Source Address to 10.1.1.2, since that wouldn't really address the issue of users not being able to log in. I'm going to go with B) Set HTTP Profile to None, since that seems the most relevant to the problem.
upvoted 0 times
...
Loise
4 months ago
Okay, let's see. The question says the users can't log in, so it's probably an issue with the protocol or the destination address. I'm leaning towards D) Set Destination Address/Mask to 0.0.0.0/0, but I'm not 100% sure.
upvoted 0 times
...
Candida
4 months ago
Hmm, I'm a bit confused. I thought the BIG-IP was used for load balancing, so maybe the answer has something to do with that? I'll need to think this through carefully.
upvoted 0 times
...
Anthony
5 months ago
I'm pretty sure the answer is B) Set HTTP Profile to None, since this is a question about SSH traffic and not HTTP.
upvoted 0 times
...

Save Cancel