Internal load balancer (C) is also a non-proxied load balancer but it is supported only in premium-tier networks.
https://cloud.google.com/load-balancing/docs/load-balancing-overview
Answer is D: https://cloud.google.com/network-tiers/docs/overview#:~:text=Premium%20Tier%20enables%20global%20load,Standard%20Tier%20regional%20IP%20address.
Order of elimination : TCP and SSL proxy is with Premium Tier. Can't be Internal TCP/UDP as Standard Tier is across the Internet. So D is correct
TCP Proxy Load Balancing terminates TCP connections from the client and creates new connections to the backends. By default, the original client IP address and port information is not preserved.
Answer is D
Ans: D (though it should have been "External TCP/UDP Network load balancers")
Cant be (C), as they are not supported on standard tier:
https://cloud.google.com/load-balancing/docs/load-balancing-overview
Answer is (C).
Use Internal TCP/UDP Load Balancing in the following circumstances:
You need to forward the original packets unproxied. For example, if you need the client source IP address to be preserved.
https://cloud.google.com/load-balancing/docs/internal#use_cases
I disagree with you, both C and D can keep the Client IP, however only TCP/UDP Network is for standard network.
https://cloud.google.com/load-balancing/docs/network
https://cloud.google.com/load-balancing/docs/load-balancing-overview
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
mikesp
Highly Voted 2 years, 2 months agodesertlotus1211
Most Recent 11 months, 1 week agoAwesomeGCP
1 year, 10 months agozellck
1 year, 10 months agopiyush_1982
2 years agoszl0144
2 years, 2 months agoAzureDP900
1 year, 9 months agoExamQnA
2 years, 2 months agoTabayashi
2 years, 3 months agoArturo_Cloud
1 year, 11 months ago