nerdexam
Google

PROFESSIONAL-CLOUD-NETWORK-ENGINEER · Question #182

You are planning to use Terraform to deploy the Google Cloud infrastructure for your company. The design must meet the following requirements: - Each Google Cloud project must represent an internal…

The correct answer is B. Create a single Shared VPC and attach each Google Cloud project as a service project. For an organization with 10-100 internal projects, each requiring its own project owner, simple deletion, reusable Terraform, and centralized network management, a Shared VPC architecture is ideal.

Submitted by fernanda_arg· Apr 18, 2026Designing, planning, and prototyping a Google Cloud network

Question

You are planning to use Terraform to deploy the Google Cloud infrastructure for your company. The design must meet the following requirements: - Each Google Cloud project must represent an internal project that your team will work on. - After an internal project is finished, the infrastructure must be deleted. - Each internal project must have its own Google Cloud project owner to manage the Google Cloud resources. - You have 10-100 projects deployed at a time. While you are writing the Terraform code, you need to ensure that the deployment is simple and the code is reusable with centralized management. What should you do?

Options

  • ACreate a single project and single VPC for each internal project.
  • BCreate a single Shared VPC and attach each Google Cloud project as a service project.
  • CCreate a single project and additional VPCs for each internal project.
  • DO Create a Shared VPC and service project for each internal project.

How the community answered

(47 responses)
  • A
    2% (1)
  • B
    79% (37)
  • C
    6% (3)
  • D
    13% (6)

Why each option

For an organization with 10-100 internal projects, each requiring its own project owner, simple deletion, reusable Terraform, and centralized network management, a Shared VPC architecture is ideal.

ACreate a single project and single VPC for each internal project.

Creating a separate VPC for each project leads to decentralized network management, higher costs due to duplicated network resources (e.g., NAT gateways, VPNs), and increased complexity across 10-100 projects, conflicting with centralized management goals.

BCreate a single Shared VPC and attach each Google Cloud project as a service project.Correct

Creating a single Shared VPC host project and attaching each internal Google Cloud project as a service project allows for centralized network management (in the host project) while maintaining administrative and billing separation for each internal project, fulfilling all requirements for scalability, ownership, deletion, and simple, reusable Terraform code.

CCreate a single project and additional VPCs for each internal project.

Creating additional VPCs within a single project for each internal project is an unconventional and complex setup that doesn't align with the requirement of "Each Google Cloud project must represent an internal project."

DO Create a Shared VPC and service project for each internal project.

This option is conceptually identical to option B, describing the use of Shared VPC with service projects, and aligns with the requirements; however, B is selected as the correct answer.

Concept tested: Shared VPC architecture for organizational projects

Source: https://cloud.google.com/vpc/docs/shared-vpc

Topics

#Shared VPC#Multi-project architecture#Network design#Terraform

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PROFESSIONAL-CLOUD-NETWORK-ENGINEER Practice