A multinational financial services enterprise manages its Google Cloud environment using a folder hierarchy divided by business units. The security compliance team requires two central guardrails across the entire `Retail-Banking` folder structure: (1) block any Compute Engine virtual machine from being provisioned with an external IP address, and (2) test a restriction against creating service account keys across the organization without breaking existing automated continuous integration pipelines. Which TWO architectural actions should the lead Cloud Architect execute using Google Cloud Organization Policies?
- Apply an Organization Policy at the `Retail-Banking` folder level setting the `constraints/compute.vmExternalIpAccess` constraint to Deny All.Cevap
- Configure the `constraints/iam.disableServiceAccountKeyCreation` Organization Policy constraint at the Organization root level with Enforcement set to Dry-Run.Cevap
- CAssign primitive IAM Viewer roles to deployment service accounts at the folder level to prevent them from allocating external IP addresses and creating service account keys.
- DConstruct a VPC Service Controls perimeter encompassing the `Retail-Banking` folder to block public IP assignment and prevent service account key exfiltration.
Cevap
The Cloud Architect must apply the `constraints/compute.vmExternalIpAccess` policy set to Deny All at the target folder level, and set the `constraints/iam.disableServiceAccountKeyCreation` policy to Dry-Run at the Organization root level.
The correct responses specify using Google Cloud Organization Policies appropriately: enforcing `constraints/compute.vmExternalIpAccess` at the folder node directly prevents public IP attachment on Compute Engine instances, while configuring `constraints/iam.disableServiceAccountKeyCreation` in dry-run mode at the organization root tests policy compliance against live CI pipelines without causing immediate workflow failures.
Adım Adım Çözüm
Anahtar Kavram
Organization Policies and Constraints
Tahmini Süre:2m 0s