Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
A financial enterprise is implementing an organizational security architecture in Google Cloud to meet strict compliance mandates for data at rest across regional workloads. The security team has established the following requirements:
Which combination of organization policies and Identity and Access Management (IAM) configurations should the security engineer implement?
constraints/gcp.restrictServiceUsage to allow only cloudkms.googleapis.com in central projects, enforce Customer-Supplied Encryption Keys (CSEK) on all compute disks, and grant roles/cloudkms.signerVerifier to workload service agents.This option relies on API enablement restrictions, Customer-Supplied Encryption Keys (CSEK), and asymmetric digital signature IAM roles instead of centralized CMEK governance.
constraints/gcp.restrictServiceUsage disables API activation within projects but does not evaluate whether storage or database resources are provisioned with customer-managed keys.roles/cloudkms.signerVerifier is utilized for asymmetric digital signing and verification, not symmetric envelope encryption for data at rest.The organization required client-side digital signatures for document signing rather than data-at-rest envelope encryption.
constraints/gcp.restrictNonCmekServices as an Allow rule for the required service APIs, configure constraints/gcp.restrictCmekCryptoKeyProjects as a Deny rule listing the workload projects, and grant roles/cloudkms.admin on the key rings to the workload service agents.This configuration misconfigures policy evaluation types on both CMEK organization policy constraints and grants overly permissive administrative privileges to automated workload identities.
constraints/gcp.restrictNonCmekServices must be configured with a Deny rule containing the service names to block non-CMEK resource creation. Configuring it as an Allow rule fails to restrict default encryption.constraints/gcp.restrictCmekCryptoKeyProjects is designed as an Allow list constraint that explicitly whitelists valid key project roots. Applying a Deny list does not safely establish an allowlist boundary for central key repositories.roles/cloudkms.admin provides full key lifecycle control (creating, disabling, and setting IAM policies on keys) rather than only the operational cryptographic permissions needed to encrypt and decrypt data.cloudkms.cryptoKeyEncrypterDecrypter), not control-plane administrative roles.The goal was to delegate full key administrative management to service agents while denying specific legacy projects from provisioning keys.
constraints/gcp.restrictNonCmekServices as a Deny rule for the required service APIs, configure constraints/gcp.restrictCmekCryptoKeyProjects as an Allow rule specifying the central KMS projects, and grant roles/cloudkms.cryptoKeyEncrypterDecrypter on the KMS keys to the respective service agents.This architectural solution combines Google Cloud CMEK organization policy constraints with least-privilege Cloud KMS Identity and Access Management (IAM) role bindings to enforce centralized cryptographic governance across an enterprise hierarchy.
constraints/gcp.restrictNonCmekServices list constraint blocks the creation of resources in designated services if CMEK is omitted. Setting this policy to Deny for specific services (e.g., bigquery.googleapis.com, storage.googleapis.com, alloydb.googleapis.com) prevents users from falling back to Google default encryption.constraints/gcp.restrictCmekCryptoKeyProjects list constraint restricts which projects can supply Cloud KMS keys for CMEK. Setting it to Allow with values such as under:projects/KMS_PROJECT_ID ensures workload projects can only consume keys provisioned in central, governed security projects.roles/cloudkms.cryptoKeyEncrypterDecrypter role to each service's respective service agent (e.g., service-[PROJECT_NUMBER]@gcp-sa-...iam.gserviceaccount.com) provides exactly the encrypt and decrypt capabilities required to wrap and unwrap Data Encryption Keys (DEKs) during I/O operations without granting administrative privileges.FAILED_PRECONDITION error responses.This approach directly leverages predefined organization policy constraints designed for CMEK governance and avoids custom scripting or complex detective-only remediation pipelines.
constraints/gcp.restrictCmekCryptoKeyProjects as an Allow rule targeting the central KMS projects, set default project-level bucket encryption to CMEK, and assign roles/cloudkms.cryptoKeyDecrypter to the workload compute instances' default service accounts.This configuration applies key source restrictions and attempts default bucket-level encryption, but it fails to enforce CMEK across all required storage and database services while providing incomplete IAM permissions to the wrong identity type.
constraints/gcp.restrictNonCmekServices.service-PROJECT_NUMBER@gcp-sa-...), not the Compute Engine default service account.roles/cloudkms.cryptoKeyDecrypter prevents the service from encrypting new objects or wrapping new Data Encryption Keys (DEKs).Workloads were strictly performing read-only decryption of existing datasets using custom user-managed Compute Engine service accounts.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated