You work for a university that is migrating to GCP.
These are the cloud requirements: " On-premises connectivity with 10 Gbps " Lowest latency access to the cloud " Centralized Networking Administration Team New departments are asking for on-premises connectivity to their projects.
You want to deploy the most cost-efficient interconnect solution for connecting the campus to Google Cloud.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
In this scenario, the university wants to migrate to GCP and requires on-premises connectivity with 10 Gbps, lowest latency access to the cloud, and a centralized networking administration team. New departments also require on-premises connectivity to their projects. The goal is to deploy the most cost-efficient interconnect solution for connecting the campus to Google Cloud.
Option A: Use Shared VPC and deploy the VLAN attachments and Interconnect in the host project. Shared VPC allows for resources to be shared across multiple projects while maintaining separation and security between them. In this option, VLAN attachments are deployed in the host project and connected to the Interconnect. However, this option does not address the requirement for on-premises connectivity for new departments. Additionally, this option may not provide the lowest latency access to the cloud since it depends on the location of the host project.
Option B: Use Shared VPC and deploy the VLAN attachments in the service projects. Connect the VLAN attachment to the Shared VPC's host project. This option also uses Shared VPC, but instead of deploying VLAN attachments in the host project, they are deployed in the service projects. The VLAN attachments are then connected to the Shared VPC's host project, which has the Interconnect. This option allows for new departments to have on-premises connectivity through their service projects. It also provides centralized networking administration through the Shared VPC. This option could provide lower latency access to the cloud compared to option A since it allows for the service projects to be located closer to the on-premises network.
Option C: Use standalone projects and deploy the VLAN attachments in the individual projects. Connect the VLAN attachment to the standalone projects' Interconnects. This option uses standalone projects, which are not connected by Shared VPC. Instead, VLAN attachments are deployed in individual projects and connected to their standalone Interconnects. This option provides separation and security between projects. However, it does not provide centralized networking administration or the ability for new departments to have on-premises connectivity through a Shared VPC. Additionally, this option may not be the most cost-efficient since each project would require its own Interconnect.
Option D: Use standalone projects and deploy the VLAN attachments and Interconnects in each of the individual projects. This option is similar to option C but requires each individual project to have its own Interconnect. This option provides separation and security between projects but does not provide centralized networking administration or the ability for new departments to have on-premises connectivity through a Shared VPC. This option is likely the most expensive and may not be the most cost-efficient solution.
In summary, option B appears to be the best solution since it provides Shared VPC for centralized networking administration, allows for new departments to have on-premises connectivity through their service projects, and could provide lower latency access to the cloud.