A healthcare organization manages its Google Cloud environment using a folder hierarchy where all production database workloads reside under a dedicated folder named Database-Prod. To comply with data sovereignty regulations, the security team must mandate that all resources provisioned within this folder can only be located in us-central1 and us-west1. The guardrail must apply automatically to all existing and future projects created within the Database-Prod folder without relying on custom deployment scripts or per-user IAM permissions. Which configuration correctly satisfies this requirement?
- Apply an Organization Policy at the Database-Prod folder level for the Resource Locations constraint (constraints/gcp.resourceLocations), specifying an allowed list containing us-central1 and us-west1.Cevap
- BAssign the primitive Owner role (roles/owner) to the security governance team at the Database-Prod folder level, relying on manual resource reviews to block non-compliant deployments.
- CCreate a VPC Service Controls perimeter around the Database-Prod folder and rely exclusively on data exfiltration rules to restrict resource deployment regions.
- DGrant the Service Account User role (roles/iam.serviceAccountUser) to developers across the Database-Prod folder to restrict where resources can be provisioned.
Cevap
Apply an Organization Policy at the Database-Prod folder level for the Resource Locations constraint (constraints/gcp.resourceLocations), specifying an allowed list containing us-central1 and us-west1.
The Organization Policy service provides centralized governance controls over resource configurations. By binding an Organization Policy containing the constraints/gcp.resourceLocations list constraint to the Database-Prod folder, Google Cloud enforces an explicit allowlist for us-central1 and us-west1. Because Organization Policies inherit down the resource hierarchy, all current and future projects inside that folder inherit this policy automatically.
Adım Adım Çözüm
Anahtar Kavram
Organization Policy Resource Location Constraints