A company has a security policy that service account keys should not be created. They want to prevent anyone from creating keys for any service account in the organization. Which organization policy constraint should they use?
Prevents creation of service account keys.
Why this answer
The `constraints/iam.disableServiceAccountKeyCreation` organization policy constraint explicitly prevents the creation of user-managed service account keys across the entire organization. This aligns with the security policy that service account keys should not be created, as it enforces the use of short-lived credentials or workload identity federation instead of long-lived keys.
Exam trap
The trap here is that candidates confuse the IAM permission `iam.serviceAccountKeys.create` with the organization policy constraint name. In the Google Professional Cloud Security Engineer exam, it's crucial to distinguish between IAM permissions (which allow actions) and organization policy constraints (which enforce restrictions). Option A uses an IAM permission, not an organization policy constraint, leading to an incorrect choice.
How to eliminate wrong answers
Option A is wrong because custom constraints are used for organization policies that are not covered by predefined constraints, but `iam.serviceAccountKeys.create` is a permission, not a constraint; the correct predefined constraint for this purpose is `constraints/iam.disableServiceAccountKeyCreation`. Option B is wrong because `constraints/iam.allowedPolicyMemberDomains` restricts which external domains can be added as members in IAM policies, not service account key creation. Option C is wrong because `constraints/compute.requireShieldedVm` enforces that Compute Engine VMs must use Shielded VM features, which is unrelated to IAM service account key management.