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

F5 Networks Exam 201 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

Contribute your Thoughts:

Rossana
15 days 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
...
Paulina
18 days 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
20 days 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
Lashaunda
3 days ago
B) Add a static route for the 172.16.0.0/12 subnet
upvoted 0 times
...
...
Lynelle
26 days 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
...
Dorthy
2 months 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
22 days ago
D) Modify the default route of the servers to point to the BIG-IP device
upvoted 0 times
...
Jettie
25 days ago
B) Add a static route for the 172.16.0.0/12 subnet
upvoted 0 times
...
...
Ryan
2 months ago
I'm not sure about that. Maybe disabling the server on the internal VLAN could also solve the problem.
upvoted 0 times
...
Chan
2 months 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
2 months 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