Exam ANS-C00 topic 1 question 74 discussion

Ans C The Proxy Protocol v2 is an option in NLB which appends the source IP in the TCP packet header. This is relevant since the servers are in on-premise and ALB will not do source IP preservation.

A With Network Load Balancer, the original source IP address and source ports for the incoming connections remain unmodified, so application software need not support X-Forwarded-For https://aws.amazon.com/blogs/aws/new-network-load-balancer-effortless-scaling-to-millions-of-requests-per-second/

NON-WEB APPLICATION. D is not an option. A >> NLB preserve source IP, unless targets are defined with IP and use TCP/TLS C >> NLB need to enable ProxyProtocol in case targets IP use TCP/TLS Ref. https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html#proxy-protocol No sufficient info in the scenario. But since we do not know, just enable Proxy Protocol.

https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html#proxy-protocol

Non-web application means you can't use Application Load Balancer. You can use NLB to meet the requirement, and enable Proxy Protocol as an optional setting to add the IP Address in the header of packet. https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html#proxy-protocol

None of the options. Should use NLB and enable Proxy Protocol v2 attribute. https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html#proxy-protocol

AWS Network Load Balancers operate at Layer 4 and support the Proxy Protocol. AWS Application Load Balancers operate on Layer 7 and support the X-Forwarded headers. AWS Classic Load Balancers operate at either Layer 7 or Layer 4, they support the both the X-Forwarded headers and the Proxy Protocol.

Network Load Balancer TCP & TLS: the source IP of the client isn’t preserved, enable Proxy Protocol UDP & TCP_UDP: the source IP of the client is preserved