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 subject to strict regulatory compliance mandates governing data residency, cryptographic boundary isolation, and access governance. The security team needs to enforce the following controls across their Google Cloud environment:
Which combination of controls and Organization Policies should the enterprise implement?
roles/owner to the workload service accounts on the host project.This approach uses VPC Service Controls to prevent network perimeter data exfiltration and uses Cloud KMS Autokey for automated key provisioning, while granting the comprehensive roles/owner basic role to workload service accounts.
roles/owner assigns complete administrative control across all Google Cloud services in the project, violating core regulatory and access governance standards.constraints/gcp.restrictNonCmekServices).constraints/gcp.restrictCmekCryptoKeyProjects) to guarantee keys originate strictly from a pre-defined compliance project.Viewer, Editor, Owner) are not recommended for production environments due to broad, untracked permissions.The primary requirement was to prevent exfiltration of data across network boundaries using service perimeters while automating key generation.
DATA_READ for all services, disable default service account creation, and assign roles/cloudkms.cryptoKeyViewer to all workload identities on the KMS key ring.This configuration enables detailed audit logging for data read operations and assigns the roles/cloudkms.cryptoKeyViewer metadata viewing role across all workload identities.
roles/cloudkms.cryptoKeyViewer role only grants read-only permissions to view key metadata; it does not grant cloudkms.cryptoKeyVersions.useToEncrypt or cloudkms.cryptoKeyVersions.useToDecrypt, causing CMEK service agent encryption operations to fail.constraints/gcp.restrictCmekCryptoKeyProjects, failing to restrict CMEK key sourcing to the designated compliant project.roles/cloudkms.cryptoKeyViewer is an auditing/visibility role, not an operational cryptographic role.The requirement was specifically to audit which principals inspect key metadata and access Cloud Storage objects without modifying encryption configurations.
constraints/gcp.restrictNonCmekServices and constraints/gcp.restrictCmekCryptoKeyProjects organization policies, create regional symmetric Cloud KMS keys in the dedicated project, and grant roles/cloudkms.cryptoKeyEncrypterDecrypter to the respective service agents on the specific keys.This architecture combines native Google Cloud Organization Policy constraints with granular Identity and Access Management (IAM) permissions on regional Cloud KMS CryptoKeys to establish strict cryptographic boundary isolation, automated compliance enforcement, and least privilege access governance.
constraints/gcp.restrictNonCmekServices organization policy constraint blocks the creation of resources using Google default encryption across specified supported services, ensuring that data is encrypted using customer-managed keys.constraints/gcp.restrictCmekCryptoKeyProjects constraint restricts the resource hierarchy locations from which CMEK keys can be selected, ensuring keys only come from the approved, dedicated Cloud KMS project and valid regional locations.roles/cloudkms.cryptoKeyEncrypterDecrypter role directly on individual crypto keys to the specific Google-managed service agents (such as service-PROJECT_NUMBER@gcp-sa-...iam.gserviceaccount.com) ensures that only authorized workload identities can perform cryptographic operations without over-granting key administrative permissions.This solution uses native organization policies to automatically enforce compliance guardrails without requiring custom post-deployment remediation scripts. It perfectly balances preventative security controls with least-privilege identity access management.
constraints/gcp.resourceLocations organization policy constraint, configure Cloud KMS with asymmetrical signing keys in a multi-region location, and grant roles/cloudkms.admin to the default Compute Engine service account.This option relies solely on constraints/gcp.resourceLocations for geographic restriction while using asymmetric signing keys and assigning broad administrative privileges (roles/cloudkms.admin) to the default Compute Engine service account.
ENCRYPT_DECRYPT purpose); asymmetric signing keys cannot be used for CMEK envelope encryption.roles/cloudkms.admin role provides administrative capabilities (such as managing IAM policies, key creation, and lifecycle destruction) rather than cryptographic encryption/decryption operations (roles/cloudkms.cryptoKeyEncrypterDecrypter), representing an excessive privilege grant to a default service account.constraints/gcp.resourceLocations policy restricts the geographic deployment of resources, but it does not prevent users from provisioning resources with default Google-managed keys rather than CMEK.The goal was to configure PKI artifact signing within specific geographical boundaries while delegating full KMS administrative lifecycle ownership.
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