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 201 Exam - Topic 10 Question 89 Discussion

Actual exam question for F5 Networks's 201 exam
Question #: 89
Topic #: 10
[All 201 Questions]

A BIG-IP device is configured with both an internal external and two Corporate VLANs. The virtual server

has SNAT enabled and is set to listen on all VLANs Auto Last Hop is disabled. The Corporate users are on

10.0.0.0./24 and 172.16.0.0/12. The BIG-IP has a Self-IP on the 1.0.0.0.0./24 subnet.

Internet users are able to access the virtual server. Only some of the Corporate users are able to connect

to the virtual server A BIG-IP Administrator performs a tcpdump on the BIG-IP and verifies that traffic is

arriving from users in 10.0.0.0/24.

What should the BIG-IP Administrator do to correct this behaviour?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Paola at Jun 01, 2024, 11:02 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Dorcas
5 months ago
I’m surprised some users can connect at all with those settings!
upvoted 0 times
...
Victor
5 months ago
Definitely not A, that would just block access completely.
upvoted 0 times
...
Margarita
5 months ago
Wait, why would disabling the server help? That doesn't make sense.
upvoted 0 times
...
Elliott
5 months ago
I think option D could work too, just modify the default route.
upvoted 0 times
...
Raelene
6 months ago
Sounds like a routing issue, maybe option B?
upvoted 0 times
...
Iluminada
6 months ago
Changing the default route to point to the extra firewall sounds familiar, but I wonder if that would actually solve the connectivity problem for the Corporate users.
upvoted 0 times
...
Keena
6 months ago
Disabling the server on the internal VLAN seems too drastic. I feel like there must be a better solution.
upvoted 0 times
...
Krissy
6 months ago
I remember a practice question where we had to modify routes, but I can't recall if it was the default route or something else.
upvoted 0 times
...
Jenelle
6 months ago
I'm not entirely sure, but I think adding a static route could help with the 172.16.0.0/12 subnet issue.
upvoted 0 times
...
Bok
6 months ago
I agree with Jovita and Catina. The 172.16.0.0/12 subnet is the key here, so adding a static route for that network is probably the way to go.
upvoted 0 times
...
Sophia
6 months ago
Disabling the server on the internal VLAN doesn't seem right, since internet users can access it. And changing the default route or modifying the server's default route don't seem relevant to the specific issue described.
upvoted 0 times
...
Catina
6 months ago
I'm leaning towards adding a static route for the 172.16.0.0/12 subnet, since the question mentions that corporate users are on that network. That seems like the most logical solution to me.
upvoted 0 times
...
Jovita
6 months ago
Okay, let's see. The issue is that some corporate users can't access the virtual server, even though internet users can. And the tcpdump shows traffic from the 10.0.0.0/24 subnet. I think the key is figuring out why the 172.16.0.0/12 subnet users can't connect.
upvoted 0 times
...
Wynell
7 months ago
This question seems straightforward, but I want to make sure I understand the details before answering.
upvoted 0 times
...
Leatha
7 months ago
Class diagrams are usually used to model the structure of the system, so I don't think that would be the best choice for this question. I'm leaning more towards the use-case or sequence diagram.
upvoted 0 times
...
Jesse
7 months ago
This question seems straightforward, I think I can figure it out.
upvoted 0 times
...
Pearly
7 months ago
Dynamic Views might be the answer, as they can be customized to show real-time and historical data together.
upvoted 0 times
...
Rossana
11 months ago
This question is making my head spin like a BIG-IP device on a dance floor. But I think the answer is clear - add that static route and get those corporate users back on track. And remember, always keep your SNAT enabled, unless you want your virtual server to be a wallflower.
upvoted 0 times
Blair
9 months ago
Good point, changing the default route could also help in this situation.
upvoted 0 times
...
Leonor
9 months ago
D) Modify the default route of the servers to point to the BIG-IP device
upvoted 0 times
...
Junita
9 months ago
That makes sense, adding a static route should fix the issue.
upvoted 0 times
...
Allene
11 months ago
B) Add a static route for the 172.16.0.0/12 subnet
upvoted 0 times
...
...
Paulina
11 months ago
As a BIG-IP administrator, I'd be tempted to add a static route for the 172.16.0.0/12 subnet. It's the simplest and most direct solution to the problem. But hey, maybe the extra firewall is actually a giant hamster wheel. You never know!
upvoted 0 times
...
Von
11 months ago
Changing the default route to point to the extra firewall might not be the best approach, as that could introduce additional complexity and potential points of failure. The static route for the 172.16.0.0/12 subnet seems like the most straightforward solution.
upvoted 0 times
Eura
10 months ago
D) Modify the default route of the servers to point to the BIG-IP device
upvoted 0 times
...
Mari
10 months ago
That makes sense, it should help route the traffic correctly
upvoted 0 times
...
Lashaunda
11 months ago
B) Add a static route for the 172.16.0.0/12 subnet
upvoted 0 times
...
...
Lynelle
12 months ago
Disabling the server on the internal VLAN doesn't sound like the right solution. I think the administrator should modify the default route of the servers to point to the BIG-IP device, which should help resolve the issue.
upvoted 0 times
Millie
10 months ago
D) Modify the default route of the servers to point to the BIG-IP device
upvoted 0 times
...
Dahlia
10 months ago
B) Add a static route for the 172.16.0.0/12 subnet
upvoted 0 times
...
...
Dorthy
1 year ago
The issue seems to be with the routing configuration. The administrator should add a static route for the 172.16.0.0/12 subnet to ensure that all corporate users can access the virtual server.
upvoted 0 times
Rebeca
11 months ago
D) Modify the default route of the servers to point to the BIG-IP device
upvoted 0 times
...
Jettie
11 months ago
B) Add a static route for the 172.16.0.0/12 subnet
upvoted 0 times
...
...
Ryan
1 year ago
I'm not sure about that. Maybe disabling the server on the internal VLAN could also solve the problem.
upvoted 0 times
...
Chan
1 year ago
I agree with Curtis. Adding a static route for the 172.16.0.0/12 subnet should help fix the issue.
upvoted 0 times
...
Curtis
1 year ago
I think the BIG-IP Administrator should add a static route for the 172.16.0.0/12 subnet.
upvoted 0 times
...

Save Cancel