Google Professional Cloud Network Engineer Question 67
Single answerGoogle Cloud PlatformYour organization is planning to deploy a multi-tier application across multiple Google Cloud projects. The application requires centralized control over network policies and shared access to common resources such as a database and a logging system. Which VPC design should you choose to meet these requirements effectively?
- A
Standalone VPCs in each project with peering to share resources
- B
A Shared VPC with host and service projects
- C
Multiple standalone VPCs connected via Cloud VPN
- D
A single global VPC for all projects with no segmentation
Show answer and explanation
Correct answer: B
Explanation
A Shared VPC is the optimal solution for organizations running applications across multiple projects in Google Cloud. It allows centralized administration of network policies and shared access to resources while maintaining logical isolation between projects. This design is scalable, secure, and simplifies inter-project communication, making it ideal for multi-project environments with shared infrastructure needs.
- A. Incorrect.
Using standalone VPCs with peering can enable resource sharing, but it does not provide centralized network policy control. Additionally, VPC peering does not support transitive connections, which can complicate the architecture.
- B. Correct.
A Shared VPC allows centralized control over network policies and enables projects to share common resources efficiently. It is the recommended solution for multi-project setups requiring shared infrastructure and unified control.
- C. Incorrect.
Cloud VPN can connect standalone VPCs, but this approach is complex to manage and does not scale well for multi-project environments. It also lacks centralized policy control.
- D. Incorrect.
A single global VPC without segmentation may simplify the network but does not adhere to best practices for security, isolation, or scalability in a multi-project environment.