-- Exhibit
-- Exhibit --
Refer to the exhibit.
A layer 2 nPath routing configuration has been deployed. A packet capture contains a client connection packet with the following properties:
Source IP:
Destination IP:
At which two locations could the packet capture have been taken? (Choose two.)
In a layer 2 nPath routing configuration, packets are intercepted by the servers directly and not the load balancer, and the return path can skip intermediate routing devices. Therefore, a packet with a source IP as Virtual Server and destination IP as Client A could be captured at the internal interface of the Internet firewall (where packets are routed back to clients) and the network interface of the web server (where the VIP is configured to respond directly to the client). These locations align with the expected routing behavior for a packet with those properties in an nPath configuration.
AC - Probably - weird question as it depends on the routing tables of the Firewall and Internal Router which we dont see.
For L2 nPath routing, will need to configure the same IP address (VIP address) on an interface of web server (usually the loopback interface). Later when the client receives the packet returned directly by the server, it knows that it should talk with VIP again, which ensures the traffic goes to VS on BIGIP again.
Feels somehow wrong. I'd rather say B and D, because I don't see a chance to get a packet with those addresses on this path. Source IP = Virtual Server makes perfectly sense on the external VLAN of the BIGIP
Okay... nPath seems to be the turning point. Didn't heart that before. https://support.f5.com/csp/article/K11116 Suggested Answers A and C are correct, i guess.
if in the question I have not talked about npath, I would also answer B and D, it's an ugly trick