GCP Professional Cloud Architect Practice Question

Creating distinct development and production projects gives each environment its own quota pool, its own Cloud Audit Logs, and fully independent IAM policies, satisfying both the engineering and audit requirements. Because a Shared VPC network can be reused by multiple service projects, the new projects can attach to the existing host project without changing any subnet, firewall-rule, or peering configuration. Merely placing the existing project into different folders or relying on namespaces or VPC Service Controls keeps the same project, so quotas, logs, and many IAM bindings would still be shared. Spinning up separate organizations is unnecessary overhead and would break the current Shared VPC design, since Shared VPC cannot cross organization boundaries.