A financial analytics company manages its cloud resources using Google Cloud folders to isolate production workloads. The security team mandates that no virtual machine (VM) instances created inside any project under the 'Analytics-Production' folder may be assigned public IP addresses. This security constraint must apply automatically to all existing and future projects created within this folder. Which approach should the Cloud Architect take to enforce this constraint centrally with minimal operational overhead?
- Apply an Organization Policy at the 'Analytics-Production' folder level enforcing the `constraints/compute.vmExternalIpAccess` boolean constraint as Deny.Cevap
- BRevoke the primitive Editor and Owner IAM roles from project administrators at the organization level and grant only fine-grained Compute Viewer roles.
- CConstruct a VPC Service Controls perimeter encompassing the 'Analytics-Production' folder and restrict all outbound network traffic.
- DRemove the Service Account User role (`roles/iam.serviceAccountUser`) from all compute engineers working within the production folder.
Cevap
Apply an Organization Policy at the 'Analytics-Production' folder level enforcing the `constraints/compute.vmExternalIpAccess` constraint.
Applying an Organization Policy with the constraint `constraints/compute.vmExternalIpAccess` enforced as Deny at the parent folder level enforces programmatic guardrails across all contained projects. Any attempt to attach a public IP to a VM instance within this folder will be rejected automatically.
Adım Adım Çözüm
Anahtar Kavram
Organization Policies and Constraints