A company has redundant mail servers in different Google Cloud Platform regions and wants to route customers to the nearest mail server based on location. How should the company accomplish this?
A.
Configure TCP Proxy Load Balancing as a global load balancing service listening on port 995.
B.
Create a Network Load Balancer to listen on TCP port 995 with a forwarding rule to forward traffic based on location.
C.
Use Cross-Region Load Balancing with an HTTP(S) load balancer to route traffic to the nearest region.
D.
Use Cloud CDN to route the mail traffic to the closest origin mail server based on client IP address.
Corrrect Answer is (A):
TCP Proxy Load Balancing is implemented on GFEs that are distributed globally. If you choose the Premium Tier of Network Service Tiers, a TCP proxy load balancer is global. In Premium Tier, you can deploy backends in multiple regions, and the load balancer automatically directs user traffic to the closest region that has capacity. If you choose the Standard Tier, a TCP proxy load balancer can only direct traffic among backends in a single region.
https://cloud.google.com/load-balancing/docs/load-balancing-overview#tcp-proxy-load-balancing
It's A. TCP is the only one that is global (multiple regions). A Network Load Balancer is regional. The HTTP(S) LB is only for http/https traffic and would not be suitable. Cloud CDN doesn't even make sense as an option.
TCP Proxy Load Balancing is a global load balancing service that works at Layer 4 (TCP/SSL) and is ideal for services like mail servers that use non-HTTP protocols, such as IMAP (port 993) or POP3 (port 995).
• TCP Proxy Load Balancing supports global load balancing, meaning it can route traffic to the nearest backend based on the geographic location of the user. This ensures that customers are routed to the nearest mail server, optimizing performance and latency.
TCP Proxy Load Balancing is the appropriate choice for globally routing TCP traffic, such as mail services, to the nearest server based on client location. It provides the necessary global load balancing capabilities to achieve this requirement.
why the other options are not the best fit:
A. TCP Proxy Load Balancing: This is a global load balancing solution, but it might not be the most efficient for routing mail traffic based on proximity.
C. Cross-Region Load Balancing with HTTP(S): This is designed for HTTP/HTTPS traffic, not mail protocols like POP3, SMTP, or IMAP.
D. Cloud CDN: While Cloud CDN can cache content for faster delivery, it's not designed to handle real-time mail traffic routing.
This is probably an old question
2-3 years ago, GCP introduces a "proxy network load balancer"
So, in 2024, we have:
- application load balancer, global, external-only, multi-region backends, only for HTTP and HTTPS, do not preserve clients' IP
- "legacy" network load balancer (aka "passthrough"), external or internal, single-region, tcp or udp, preserve clients' IP
- "new" network load balancer (aka "proxy"), global, external or internal, multi-region backends, tcp or udp, do not preserve clients' IP
Here, we want:
- global
- external
- multi-region
- non-http
=> proxy network load balancer is the solution
This maps to A (generic answer) or B (but only in proxy mode: passthrough won't work)
The company can achieve location-based routing of customers to the nearest mail server in Google Cloud Platform (GCP) using a Network Load Balancer (NLB)
The company can achieve location-based routing of customers to the nearest mail server in Google Cloud Platform (GCP) using a Network Load Balancer (NLB)
There is no direct SMTP support in TCP proxy load balancer, hens it cannot be A. Google Cloud best practices recommend Network Load Balancing (NLB) for Layer 4 protocols like SMTP.
B) Create a Network Load Balancer to listen on TCP port 995 with a forwarding rule to forward traffic based on location.
Explanation:
Port 995 implies this is SSL/TLS encrypted mail traffic (IMAP).
Network Load Balancing allows creating forwarding rules to route traffic based on IP location.
This can send users to the closest backend mail server.
TCP Proxy LB does not allow location-based routing.
HTTP(S) LB is for HTTP only, not generic TCP traffic.
Cloud CDN works at the HTTP level so cannot route TCP mail traffic.
So a Network Load Balancer with IP based forwarding rules provides the capability to direct mail users to the closest regional mail server based on their location, meeting the requirement.
"A" is the most suitable answer.
Mail servers use SMTP which run on TCP. This excludes C, D which are HTTPs based. Option B is not global which excludes it as well.
The following page elaborates on global external proxy load balancing under the premium tier which meets the needs for this question and aligns with option A
https://cloud.google.com/load-balancing/docs/tcp#identify_the_mode
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.
ESP_SAP
Highly Voted 4 years, 6 months agoWarren2020
Highly Voted 4 years, 11 months agololanczos
Most Recent 3 months, 2 weeks agoSQLbox
9 months agoMr_MIXER007
9 months, 3 weeks agousercism007
10 months, 1 week ago3d9563b
10 months, 4 weeks agopico
1 year agoshanwford
1 year, 1 month agoeeghai7thioyaiR4
1 year, 1 month agoeeghai7thioyaiR4
1 year, 1 month agoRoro_Brother
1 year, 1 month agoJOKERO
8 months, 4 weeks agodija123
1 year, 3 months agookhascorpio
1 year, 4 months agoErenYeager
1 year, 4 months ago[Removed]
1 year, 11 months agogcpengineer
2 years agogcpengineer
2 years agogcpengineer
2 years ago