A https://cloud.google.com/interconnect/docs/how-to/dedicated/using-interconnects-other-projects

Exam on 2024-05-02

Choose A. It seems that option A focuses on centralizing the on-premises connectivity infrastructure in the host project, which can lead to streamlined management and potentially better cost efficiency. If the university prefers a more centralized approach to network administration and connectivity, option A might be a suitable choice.

https://cloud.google.com/network-connectivity/docs/interconnect/how-to/enabling-multiple-networks-access-same-attachment

A: Dedicated Interconnect connections enable you to connect your on-premises network to multiple Virtual Private Cloud (VPC) networks by adding multiple VLAN attachments ***** to that connection. You can create a VLAN attachment from an Interconnect connection in one project to a VPC network in another project, as long as they are both in the same organization. A VLAN attachment that is used with either type of connection can use Shared VPC or VPC Network Peering to share the connectivity between multiple VPC networks.

A is correct answer

Answer is A

Answer is A: https://cloud.google.com/network-connectivity/docs/interconnect/concepts/best-practices Configure VLAN attachments in the Shared VPC host project 'In a Shared VPC network, configure all VLAN attachments, not physical Interconnect connections (ports), in the host project. For more information about connecting attachments to Shared VPC networks'... https://cloud.google.com/network-connectivity/docs/interconnect/how-to/enabling-multiple-networks-access-same-attachment 'You must create VLAN attachments and Cloud Routers for an Interconnect connection only in the Shared VPC host project'

Ans - A

Correct Answer is (A) Using Cloud Interconnect with Shared VPC You can use Shared VPC to share your VLAN attachment in a project with other VPC networks. Choosing Shared VPC is preferable if you need to create many projects and would like to prevent individual project owners from managing their connectivity back to your on-premises network. In this scenario, the host project contains a common Shared VPC network usable by VMs in service projects. Because VMs in the service projects use this network, Service Project Admins don't need to create other VLAN attachments or Cloud Routers in the service projects. In this scenario, you must create VLAN attachments and Cloud Routers for a Cloud Interconnect connection only in the Shared VPC host project. The combination of a VLAN attachment and its associated Cloud Router are unique to a given Shared VPC network. https://cloud.google.com/network-connectivity/docs/interconnect/how-to/enabling-multiple-networks-access-same-attachment#using_with

B is correct Ans In A, you create VLAN attachment in hostproject which has shared VPN and On-prem Interconnect. Than how departments will connect to Interconnect from their projects? B is correct approach. VLAN attachments are created in service projects of individual departments. It uses "In another project" option to define where is Interconnect.

A is correct answer and also recommended Google solution.

The correct answer is A Shared VPC overview https://cloud.google.com/vpc/docs/shared-vpc

A is correct

I think A is the right answer. When using a Shared VPC Network with Dedicated Interconnect, consider the following: VLAN attachments and Cloud Routers for Dedicated Interconnect must exist in the Shared VPC host project, not in any service projects attached to the host project. When you create the Cloud Router to manage a VLAN attachment, you specify a particular VPC network. Effectively, the combination of a VLAN attachment and its associated Cloud Router are unique to a given Shared VPC network. Service Project Admins can create VMs that use subnets in a Shared VPC network of a host project based on the permissions they have to the host project. VMs that use the Shared VPC network can use the custom dynamic routes for VLAN attachments available to that network.