A financial enterprise is updating its cloud governance posture across its Google Cloud resource hierarchy. The lead security architect needs to enforce two enterprise-wide governance requirements across all projects under the Production folder:
1. Prevent cloud engineers from generating long-lived service account JSON keys.
2. Prevent Compute Engine virtual machines from being assigned external public IP addresses.
Which TWO Organization Policy constraints must the architect enforce at the Production folder level to satisfy these compliance requirements? (Select TWO.)
- Enforce constraints/iam.disableServiceAccountKeyCreationCevap
- Enforce constraints/compute.vmExternalIpAccess set to Deny AllCevap
- CAssign primitive IAM Viewer roles to developers and revoke Service Account Admin permissions across the folder
- DConfigure a VPC Service Controls perimeter around the Production folder and block all egress traffic to external IP addresses
Cevap
The correct options are enforcing constraints/iam.disableServiceAccountKeyCreation and enforcing constraints/compute.vmExternalIpAccess set to Deny All at the folder level.
Enforcing `constraints/iam.disableServiceAccountKeyCreation` prevents users from creating new service account keys within the target hierarchy. Enforcing `constraints/compute.vmExternalIpAccess` with a deny policy blocks VM instances from being configured with external IP addresses. Together, these two Organization Policies directly fulfill both security governance mandates.
Adım Adım Çözüm
Anahtar Kavram
Organization Policies for IAM and Compute Security Controls