You will use Terraform to provision many short-lived internal projects (10–100 concurrently). Each internal project must map to its own Google Cloud project with a project owner, and infrastructure must be removable when done. To keep deployments simple, reusable, and centrally managed, what approach should you use?

The correct approach is to create a single Shared VPC host project and attach each internal Google Cloud project as a service project. This centralizes network management (routing, firewalls, IP addresses) in the host project while allowing each internal project to maintain its own administrative boundaries and billing. This meets the requirement for simple, reusable, and centrally managed deployments for many short-lived projects, as new projects can easily attach to the existing shared network infrastructure. Creating a single Google Cloud project and a single VPC per internal project would lead to decentralized, complex network management and potential IP overlap issues. Creating a single Google Cloud project and additional VPCs for each internal project is not scalable and would make network management cumbersome.