MENU
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?
Suggested Answer: B
Get Premium 303 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
24 comments · newest first
KA
Katie
5 days ago
I agree with B. The static route should allow proper traffic flow for those users.
MA
Malcom
10 days ago
Option A seems risky. Disabling the server might cut off access completely.
AR
Arthur
15 days ago
I’m leaning towards D. Modifying the default route could solve the issue for all users.
LI
Lisha
20 days ago
I think option B makes sense. A static route could help the 172.16.0.0/12 users connect.
GL
Glen
25 days ago
Overall, I think B is the safest bet. It directly addresses the routing issue.
SA
Salome
1 month ago
I feel like option C could complicate things. Changing the default route might not be necessary.
SA
Sabrina
1 month ago
But what if the internal VLAN is misconfigured? Option A might be worth considering.
RU
Rupert
1 month ago
I'm leaning towards option D. Modifying the default route could solve the issue too.
SH
Shad
2 months ago
Agreed! Without that route, traffic won't flow properly.
LA
Lawrence
2 months ago
I think option B makes sense. A static route could help reach the 172.16.0.0/12 subnet.
RE
Rex
2 months ago
Definitely check the default route settings too!
JU
Judy
2 months ago
Wait, why would some users connect and not others? That's weird.
CO
Coral
2 months ago
Disabling the server on the internal VLAN seems unnecessary.
VE
Veta
2 months ago
I agree, adding a static route could fix it!
JU
Jutta
3 months ago
Sounds like a routing issue with the 172.16.0.0/12 subnet.
SH
Shalon
3 months ago
Definitely check the VLAN settings too, could be a misconfiguration.
JA
Jaime
3 months ago
Wait, why is only some of the Corporate users having issues? That’s weird!
FL
Fletcher
3 months ago
Disagree, changing the default route (C) might cause more problems.
EL
Elin
3 months ago
I think adding a static route (B) is the way to go!
PA
Pauline
3 months ago
Sounds like a routing issue to me.
ME
Melita
4 months ago
I think disabling the server on the internal VLAN could cause more issues. It seems like the static route option might be the best choice, but I’m not entirely sure.
BR
Brandon
4 months ago
I’m a bit confused about the default routes. Shouldn’t they be pointing to the BIG-IP device for proper traffic flow?
SH
Shaunna
4 months ago
This question feels similar to one we practiced where we had to troubleshoot VLAN access. I think adding a static route might help, but I can't recall the specifics.
RU
Ruth
5 months ago
I remember something about SNAT and how it can affect routing, but I'm not sure if that's the main issue here.