You are in the early stages of planning a migration to GCP.
You want to test the functionality of your hybrid cloud design before you start to implement it in production.
The design includes services running on a Compute Engine Virtual Machine instance that need to communicate to on-premises servers using private IP addresses.
The on-premises servers have connectivity to the internet, but you have not yet established any Cloud Interconnect connections.
You want to choose the lowest cost method of enabling connectivity between your instance and on-premises servers and complete the test in 24 hours.
Which connectivity method should you choose?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
To test the functionality of your hybrid cloud design before implementing it in production, you want to choose the lowest cost method of enabling connectivity between your instance and on-premises servers, and complete the test in 24 hours. The on-premises servers have connectivity to the internet, but you have not yet established any Cloud Interconnect connections.
Option A: Cloud VPN Cloud VPN is a virtual private network ( VPN) connection over the public internet. Cloud VPN can provide secure, low-cost connectivity between a Compute Engine instance in GCP and your on-premises network. However, it might not be the best option for high-throughput workloads or those with strict SLAs, as it relies on the public internet and may experience higher latency.
Option B: 50-Mbps Partner VLAN attachment A Partner VLAN attachment is a connection between your on-premises network and a VPC network in GCP. This option provides a private, dedicated connection with a bandwidth of up to 50 Mbps. This is a good option for low- to moderate-throughput workloads and those with moderate SLAs. However, it may not be sufficient for higher-throughput workloads or those with strict SLAs.
Option C: Dedicated Interconnect with a single VLAN attachment Dedicated Interconnect provides a dedicated, private connection between your on-premises network and a VPC network in GCP. You can choose to provision one or more VLAN attachments on the Dedicated Interconnect. A single VLAN attachment provides a private connection with a bandwidth of up to 10 Gbps. This is a good option for high-throughput workloads or those with strict SLAs. However, it can be more expensive than the other options.
Option D: Dedicated Interconnect, but don't provision any VLAN attachments This option provides a dedicated, private connection between your on-premises network and a VPC network in GCP, but without any VLAN attachments. This option may not be suitable for your use case as it does not provide connectivity between your Compute Engine instance and on-premises servers.
Considering the requirements of the scenario, the most suitable option would be Option A: Cloud VPN, as it provides a secure, low-cost connection over the public internet, which would be sufficient for testing the functionality of the hybrid cloud design. Additionally, Cloud VPN can be set up relatively quickly, making it a good choice for completing the test within 24 hours. However, if the workloads were higher-throughput or had strict SLAs, Option C: Dedicated Interconnect with a single VLAN attachment would be a better choice, but at a higher cost.