An enterprise security architect wants to prevent developers from creating service account keys and ensure that Compute Engine resources can only be deployed in specific approved Google Cloud regions across all projects contained within the `Production` folder. Which TWO Organization Policy constraints should be configured to satisfy these governance requirements? (Select TWO.)
- Enforce `constraints/iam.disableServiceAccountKeyCreation` at the `Production` folder level.Cevap
- Enforce `constraints/gcp.resourceLocations` with an allowed locations list at the `Production` folder level.Cevap
- CGrant the primitive Viewer role (`roles/viewer`) to developer identities at the `Production` folder level.
- DConfigure a VPC Service Controls perimeter encompassing the `Production` folder to restrict resource creation and API access.
Cevap
The correct policy constraints to enforce at the `Production` folder level are `constraints/iam.disableServiceAccountKeyCreation` to block key creation and `constraints/gcp.resourceLocations` to restrict regional deployments.
Enforcing `constraints/iam.disableServiceAccountKeyCreation` directly disables service account key creation, and enforcing `constraints/gcp.resourceLocations` limits infrastructure deployment to specified regions. Configured at the folder level, these constraints automatically govern all child projects.
Adım Adım Çözüm
Anahtar Kavram
Organization Policy Constraints for IAM Security and Location Restrictions