101 · Question #95
An LTM has the 3 virtual servers, a SNAT, four self IP addresses defined and the networks shown in the exhibit. Selected options for each object are shown below. Settings not shown are at their defaul
The correct answer is A. Destination IP: 10.10.2.10. When destination IP 10.10.2.10 matches only the IP Forwarding virtual server VirtualServer3 (10.10.2.0/24:80), BIG-IP passes the packet through unchanged, preserving the original destination IP.
Question
An LTM has the 3 virtual servers, a SNAT, four self IP addresses defined and the networks shown in the exhibit. Selected options for each object are shown below. Settings not shown are at their defaults. VirtualServerl Destination: 10.10.2.102:80 netmask 255.255.255.255 Pool: Pool with 3 members in the 172.16/16 network VirtualServer2 Destination: 10.10.2.102:* netmask 255.255.255.255 Pool: Pool with 3 members in the 192.168/16 network VirtualServer3 Destination: 10.10.2.0:80 netmask 255.255.255.0 Type: IP Forwarding SNAT1 Source IP: All Addresses SNATAddress: SNAT Pool with 2 members 172.16.20.50 and 192.168.10.50 Self IPs 192.168.1.1; 172.16.1.1; 10.10.2.1; 10.10.1.1 A connection attempt is made with a source IP and port of 10.20.100.50:2222 and a destination IP and port of 10.10.2.10:80. When the request is processed, what will be the destination IP address?
Options
- ADestination IP: 10.10.2.10
- BDestination IP: pool member in the 192.168/16 network.
- CDestination IP: pool member in the 172.16/16 network
- DThe request will be dropped.
How the community answered
(52 responses)- A62% (32)
- B4% (2)
- C12% (6)
- D23% (12)
Why each option
When destination IP 10.10.2.10 matches only the IP Forwarding virtual server VirtualServer3 (10.10.2.0/24:80), BIG-IP passes the packet through unchanged, preserving the original destination IP.
VirtualServer3 is configured as an IP Forwarding type with destination 10.10.2.0/24:80, which matches 10.10.2.10:80. An IP Forwarding virtual server does not perform load balancing or destination NAT - it simply routes the packet toward its original destination, so the destination IP remains 10.10.2.10.
VirtualServer2 (10.10.2.102:*) requires the exact IP 10.10.2.102 and does not match destination 10.10.2.10, so its 192.168/16 pool is never selected.
VirtualServer1 (10.10.2.102:80) also requires the exact IP 10.10.2.102 and does not match destination 10.10.2.10, so its 172.16/16 pool is never selected.
The packet is not dropped because VirtualServer3 (10.10.2.0/24:80) does match 10.10.2.10:80 and forwards it as an IP Forwarding virtual server without modification.
Concept tested: BIG-IP LTM IP Forwarding virtual server behavior
Source: https://techdocs.f5.com/en-us/bigip-16-1-0/big-ip-local-traffic-manager-implementations/creating-an-ip-forwarding-virtual-server.html
Topics
Community Discussion
No community discussion yet for this question.