Professional Cloud ArchitectManage implementationMedium
A financial services company is migrating its critical customer-facing applications to Google Cloud. These applications require extremely low latency and high availability across multiple regions to serve a global customer base. The company also has strict data residency requirements, mandating that customer data processed in a specific region must remain within that region. You need to design a network architecture that meets these requirements while ensuring optimal performance and compliance. Which Google Cloud networking service should you primarily use to interconnect your regional deployments and provide a single global access point for users?
- ACloud VPN
- BVPC Network Peering
- CCloud Load Balancing (Global External HTTP(S) Load Balancer)
- DCloud Interconnect (Dedicated Interconnect)
Show answer & explanationAnswer & explanation
Correct answer: C. Cloud Load Balancing (Global External HTTP(S) Load Balancer)
To meet the requirements for extremely low latency, high availability across multiple regions, and a single global access point for users for customer-facing applications, a Global External HTTP(S) Load Balancer is the most suitable choice. It provides a single IP address, intelligent routing to the closest healthy backend, and handles regional failover automatically.
Why the other options are wrong
- A. Cloud VPN is primarily for secure site-to-site connectivity between on-premises networks and Google Cloud, not for globally distributing customer-facing applications.
- B. VPC Network Peering allows private connectivity between VPC networks within Google Cloud, but it doesn't provide a global access point for external users or global load balancing capabilities.
- D. Cloud Interconnect (Dedicated Interconnect) provides high-bandwidth, low-latency connectivity between on-premises networks and Google Cloud, similar to Cloud VPN but at a higher scale, and is not designed for external user access to global applications.
Global External HTTP(S) Load Balancer
A global, proxy-based load balancer for HTTP(S) traffic that distributes requests across multiple regions and backends, providing a single global IP address and automatic failover.
- Single global IP address for users.
- Routes traffic to the closest healthy backend.
- Provides high availability and fault tolerance across regions.
- Supports HTTP and HTTPS protocols.
Memory trick: Global users need a single, smart gateway.