Creating a Private Connection for 20 Gbps between Google Compute Engine and On-Premises Data Center | Best Practices

Set Up Private Connection for 20 Gbps between Compute Engine and On-Premises Data Center

Question

You want to create a private connection between your instances on Compute Engine and your on-premises data center.

You require a connection of at least 20 Gbps.

You want to follow Google-recommended practices.

How should you set up the connection?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

A.

The recommended approach to create a private connection between Compute Engine instances and an on-premises data center, with a requirement of at least 20 Gbps, is to use Dedicated Interconnect. Therefore, option A is the correct answer. Here is a detailed explanation:

A. Create a VPC and connect it to your on-premises data center using Dedicated Interconnect: Dedicated Interconnect provides a direct physical connection between your on-premises network and Google Cloud's network. This connection is established using a dedicated fiber-optic cable and offers high-speed, low-latency connectivity. With Dedicated Interconnect, you can connect your on-premises data center to Google Cloud through a partner's colocation facility or a Google point of presence (POP).

Here are some benefits of using Dedicated Interconnect:

  • Higher throughput: With Dedicated Interconnect, you can achieve higher throughput (up to 10 Gbps per physical connection) and lower latency than with a VPN connection.
  • Private connectivity: Dedicated Interconnect provides a private, dedicated connection between your on-premises network and your VPC network in Google Cloud.
  • SLA: Dedicated Interconnect comes with an SLA that guarantees uptime and packet loss.
  • Global reach: You can use Dedicated Interconnect to connect to Google Cloud regions worldwide.

B. Create a VPC and connect it to your on-premises data center using a single Cloud VPN: While a Cloud VPN can provide a secure connection between your on-premises network and a VPC network in Google Cloud, it is not recommended for high-speed, high-throughput use cases. Cloud VPNs can provide up to 3 Gbps of throughput per tunnel, and a single VPN connection can support up to 1.5 Gbps. Therefore, using a single Cloud VPN to meet the requirement of at least 20 Gbps is not feasible.

C. Create a Cloud Content Delivery Network (Cloud CDN) and connect it to your on-premises data center using Dedicated Interconnect: Cloud CDN is a content delivery network that caches content at Google's edge locations worldwide, making it faster and more reliable for users to access your content. While Cloud CDN can improve the delivery of content, it is not designed to provide private connectivity between your on-premises network and your VPC network in Google Cloud. Therefore, using Cloud CDN to meet the requirement of a private connection is not recommended.

D. Create a Cloud Content Delivery Network (Cloud CDN) and connect it to your on-premises datacenter using a single Cloud VPN: Similar to option B, using a single Cloud VPN to connect to Cloud CDN would not provide the required throughput of at least 20 Gbps. Additionally, Cloud CDN is not designed to provide private connectivity between your on-premises network and your VPC network in Google Cloud. Therefore, using Cloud CDN with a single Cloud VPN to meet the requirement of a private connection is not recommended.