A global healthcare enterprise is migrating its patient image processing application to Google Cloud. To satisfy strict data privacy regulations and governance guardrails across all projects contained within the Healthcare-Workloads folder, the cloud security team must enforce two specific governance controls:
1. Compute Engine virtual machine instances must not be allocated external/public IP addresses.
2. Google Cloud resources must be restricted to deployment exclusively within European locations (eu-west1 and eu-west3).
Which TWO Organization Policy constraints should the cloud architect apply to the Healthcare-Workloads folder? (Select TWO.)
- Enforce the `constraints/compute.vmExternalIpAccess` boolean constraint with an empty allowlist.Cevap
- Enforce the `constraints/gcp.resourceLocations` list constraint configured to allow `in:eu-west1-locations` and `in:eu-west3-locations`.Cevap
- CConfigure a VPC Service Controls security perimeter around the folder to block external network egress traffic to public IP ranges.
- DAssign the `roles/compute.networkAdmin` IAM role at the folder level to restrict users from attaching external IP addresses.
Cevap
The architect must enforce the `compute.vmExternalIpAccess` constraint to restrict public IP allocation and the `gcp.resourceLocations` constraint to limit resource creation to specified European regions.
Applying Organization Policy constraints at the folder level ensures inherited, immutable guardrails across all contained projects. The `compute.vmExternalIpAccess` constraint blocks public IP assignments on virtual machines, and the `gcp.resourceLocations` constraint restricts resource provisioning strictly to the specified European regions.
Adım Adım Çözüm
Anahtar Kavram
Centralized Governance using Organization Policy Constraints for VM Networking and Resource Placement