Google Professional Cloud DevOps Engineer Question 6
Single answerGoogle Cloud PlatformYour organization has a requirement to host multiple projects with their own Virtual Private Cloud (VPC) networks, but they also need to share resources like a centralized database and certain APIs between the projects securely. As a Google Cloud DevOps Engineer, how would you implement a solution that minimizes operational overhead while meeting the requirements?
- A
Use Shared VPC to create a host project and attach the service projects to enable resource sharing.
- B
Create individual VPCs for each project and set up VPC peering between them for resource sharing.
- C
Use Cloud VPN to connect the VPCs of individual projects and share resources securely.
- D
Implement Shared VPC by enabling Network Endpoint Groups (NEGs) across multiple projects.
Show answer and explanation
Correct answer: A
Explanation
Shared VPC is the recommended solution for organizations that need to share resources securely across multiple projects in Google Cloud. It allows you to centralize networking in a host project and attach service projects to the same network, reducing complexity and improving security. VPC peering or Cloud VPN may work in limited scenarios, but they are not designed for the centralized, efficient resource sharing that Shared VPC provides.
- A. Correct.
Correct. Shared VPC allows you to create a centralized host project that shares its network resources with service projects, enabling secure and efficient resource sharing while minimizing operational overhead.
- B. Incorrect.
Incorrect. While VPC peering allows projects to communicate, it can become complex to manage for multiple projects and does not offer centralized administration or security benefits like Shared VPC.
- C. Incorrect.
Incorrect. Cloud VPN is used for connecting on-premises networks to Google Cloud or for hybrid setups, but it isn't the recommended approach for connecting projects within Google Cloud itself.
- D. Incorrect.
Incorrect. Network Endpoint Groups (NEGs) are used for traffic steering to specific backends, not for inter-project resource sharing or implementing Shared VPC.